Reference · Credentials
Connect Intercom to BusyBot
Used by 1 BusyBot node.
Type
intercomApi 2 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API Key / Access TokenapiKey | password | Yes | Intercom API access token. Found in Settings > Developers > Access Token. |
Regionregion | options | No | Intercom data region. EU/AU customers MUST select the matching region or auth fails with 401. |
Setting up Intercom API
- In Intercom API, create the credential this connection needs — the values listed in the table above. These are issued from your own Intercom API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Intercom API.
- Paste each value into the matching field and save.
- Add the Intercom 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 Intercom credentials?
One node: Intercom. Create the credential once and select it in that node.
What does a Intercom credential need?
2 fields: API Key / Access Token, Region. Required: API Key / Access Token. The values come from your own Intercom account.
How are Intercom 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 Intercom API
One credential works across every node below — create it once and reuse it.