Reference · Credentials
Affinity API credentials
Used by 2 BusyBot nodes.
affinityApi 1 field The Affinity credential holds an API key issued by your Affinity account, used by the Affinity node and its trigger. Affinity gates API access by plan, so confirm it is available to your account before building a workflow that depends on it.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API KeyapiKey | password | Yes | Your Affinity API key. |
Getting your credentials
- Sign in to Affinity.
- Open your account settings and find the API section.
- Generate an API key and copy it.
- Paste it into the credential’s API Key field in BusyBot.
Permissions and scopes
The key acts with the permissions of the account that created it, so lists and fields invisible to that user are invisible to the automation. If a workflow should see everything, generate the key from an account with the appropriate access.
Troubleshooting
- 401 Unauthorized — the key is wrong or has been revoked; generate a new one.
- Empty results where data exists — the account behind the key does not have access to that list or field.
- API not available — Affinity gates API access by plan. Confirm your plan includes it.
Frequently asked questions
Is API access included in every Affinity plan?
No — Affinity gates API access by plan, so confirm yours includes it before building a workflow that depends on it.
Why is a list I can see returning nothing?
The key carries the permissions of the account that generated it. If that account cannot see the list, neither can the automation.
Does one key cover both the Affinity node and its trigger?
Yes — both declare the same credential type, so a single credential serves them.
Nodes that use Affinity API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.