Reference · Credentials
ConvertKit API credentials
Used by 2 BusyBot nodes.
convertKitApi 1 field The ConvertKit credential holds your account's **API Secret** — not the public API key. ConvertKit issues both, and write operations require the secret, which is why that is the field here. Pasting the key instead is the most common setup mistake.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API SecretapiSecret | password | Yes | Your ConvertKit API Secret. |
Getting your credentials
- Sign in to your ConvertKit account.
- Open your account settings and find the developer or API area.
- Copy the API Secret. ConvertKit shows an API Key alongside it; the secret is the one this credential needs.
- Paste it into the credential’s API Secret field in BusyBot.
Permissions and scopes
The secret grants full access to the account’s subscribers, forms, sequences and tags. Treat it as you would a password, and rotate it if it may have been exposed.
Troubleshooting
- 401 Unauthorized — you may have pasted the API Key rather than the API Secret. They are different values.
- Custom field values ignored — the field must already exist in ConvertKit; unknown keys are silently dropped.
- Tag operations failing — tags are addressed by numeric ID rather than by name in several operations.
Frequently asked questions
API Key or API Secret?
The secret. ConvertKit issues both, and this credential needs the secret because write operations require it — pasting the key is the most common setup mistake.
Is the secret safe to reuse across workflows?
It is a single account-wide secret, so yes technically — but it grants full access, so rotate it if it may have been exposed.
Why are my custom fields not saving?
The field has to exist in ConvertKit already. Keys that match nothing are ignored rather than erroring.
Nodes that use ConvertKit API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.