Reference · Credentials

Flow API credentials

Used by 2 BusyBot nodes.

Type flowApi 2 fields

The Flow credential needs two values: your organization ID and a personal access token. Flow scopes requests by organization, which is why the ID is required alongside the token.

Fields

Field	Type	Required	Notes
Organization ID `organizationId`	string	Yes	Your Flow organization ID.
Access Token `accessToken`	password	Yes	Your Flow API personal access token.

Getting your credentials

Sign in to Flow.
Open the settings area covering API access or integrations.
Create a personal access token and copy it.
Note your organization ID, which identifies the Flow organization the automation should act within.
Enter both values into the credential in BusyBot.

Troubleshooting

401 Unauthorized — the token is wrong or revoked.
404 or empty results — the organization ID is wrong, or the token’s account does not belong to that organization.

Frequently asked questions

Why is an organization ID needed?

Flow scopes requests by organization, so the token alone does not say which one to act within.

Whose permissions apply?

Those of the account that created the personal access token.

Does one credential cover the node and its trigger?

Yes, both declare the same type.

Nodes that use Flow API

One credential works across every node below — create it once and reuse it.

Last updated 2026-08-16. Spotted something wrong? Tell us.