Reference · Credentials
Connect HubSpot Developer to BusyBot
Used by 1 BusyBot node.
Type
hubspotDeveloperApi 3 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Developer API KeyapiKey | password | Yes | HubSpot Developer API key |
App IDappId | string | Yes | HubSpot application ID |
Client SecretclientSecret | password | No | HubSpot app client secret for webhook signature verification |
Setting up HubSpot Developer API
- In HubSpot Developer API, create the credential this connection needs — the values listed in the table above. These are issued from your own HubSpot Developer API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose HubSpot Developer API.
- Paste each value into the matching field and save.
- Add the HubSpot Trigger 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 HubSpot Developer credentials?
One node: HubSpot Trigger. Create the credential once and select it in that node.
What does a HubSpot Developer credential need?
3 fields: Developer API Key, App ID, Client Secret. Required: Developer API Key, App ID. The values come from your own HubSpot Developer account.
How are HubSpot Developer 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 HubSpot Developer API
One credential works across every node below — create it once and reuse it.