BusyBot

Reference · Credentials

ActiveCampaign API credentials

Used by 2 BusyBot nodes.

Type activeCampaignApi 2 fields

The ActiveCampaign credential needs two values — your account's API URL and an API key — both issued by your own ActiveCampaign account. The URL is account-specific, which is why it is a field here rather than a fixed endpoint.

Fields

FieldTypeRequiredNotes
API URL
apiUrl		 string Yes The base URL of your ActiveCampaign account
API Key
apiKey		 password Yes Your ActiveCampaign API key

Getting your credentials

  1. Sign in to your ActiveCampaign account.
  2. Open the Developer section of your account settings, where both values are shown together.
  3. Copy the API URL. It is unique to your account and looks like https://youraccount.api-us1.com — the region suffix differs between accounts.
  4. Copy the API Key shown alongside it.
  5. Paste both into the credential in BusyBot.

Permissions and scopes

The key acts with the permissions of the ActiveCampaign user it belongs to, so lists and contacts that user cannot see are invisible to the automation.

Troubleshooting

  • 404 or connection errors — the API URL is wrong or truncated. It must be your account’s full URL, not the generic ActiveCampaign domain.
  • 403 Forbidden — the API key is wrong or was regenerated. Copy the current value from the developer settings.
  • Reads work but writes fail — check the permissions of the user account whose key you used.

Frequently asked questions

Why does it need a URL as well as a key?

Because ActiveCampaign gives each account its own API host. The key alone does not tell BusyBot where to send the request, which is why both fields are required.

Where do I find both values?

In the developer area of your ActiveCampaign account settings, where the API URL and API key are shown together.

Does regenerating the key break existing workflows?

Yes — any workflow using the old key stops authenticating until you update the credential in BusyBot with the new value.

Nodes that use ActiveCampaign API

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

Last updated . Spotted something wrong? Tell us.