Reference · Credentials
Connect Agile CRM to BusyBot
Used by 1 BusyBot node.
Type
agileCrmApi 3 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Emailemail | string | Yes | Account email for Basic Auth. |
API KeyapiKey | password | Yes | REST API key. |
Subdomainsubdomain | string | Yes | Your Agile CRM subdomain (e.g., mycompany). |
Setting up Agile CRM API
- In Agile CRM API, create the credential this connection needs — the values listed in the table above. These are issued from your own Agile CRM API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Agile CRM API.
- Paste each value into the matching field and save.
- Add the Agile CRM node to a workflow, select this credential, and run a simple operation to confirm it authenticates.
Security
- Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
- Grant the minimum scopes or permissions the operations you actually use require.
- Rotate the credential periodically, and immediately if it may have been exposed.
- Credentials are scoped to your account — a workflow cannot use another account's.
Frequently asked questions
Which BusyBot nodes use Agile CRM credentials?
One node: Agile CRM. Create the credential once and select it in that node.
What does a Agile CRM credential need?
3 fields: Email, API Key, Subdomain. Required: Email, API Key, Subdomain. The values come from your own Agile CRM account.
How are Agile CRM secrets stored?
Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.
Nodes that use Agile CRM API
One credential works across every node below — create it once and reuse it.