BusyBot

Reference · Credentials

Twilio API credentials

Used by 2 BusyBot nodes.

Type twilioApi 5 fields

The Twilio credential always needs your Account SID, then one of two secrets: the account auth token, or an API key SID and secret pair. The API key route is the better default — it can be revoked on its own without changing the account-wide token every other integration depends on.

Fields

FieldTypeRequiredNotes
Auth Type
authType		 string No "authToken" or "apiKey"
Account SID
accountSid		 string Yes Your Twilio Account SID
Auth Token
authToken		 password No Your Twilio Auth Token
API Key SID
apiKeySid		 password No Your Twilio API Key SID
API Key Secret
apiKeySecret		 password No Your Twilio API Key Secret

Getting your credentials

  1. Sign in to the Twilio Console.
  2. Copy your Account SID from the console dashboard. It begins with AC.
  3. Decide which secret to use and set Auth Type accordingly:
    • apiKey (recommended) — create an API key in the console, then copy its SID into API Key SID and its Secret into API Key Secret. The secret is shown once.
    • authToken — copy the account Auth Token from the dashboard into Auth Token.
  4. Paste the values into the credential in BusyBot.

Permissions and scopes

An API key can be revoked independently, so a leak or a decommissioned integration costs you one key rather than a rotation across everything you own. The account auth token is account-wide and rotating it breaks every integration at once.

If you use Twilio subaccounts, create the key under the subaccount whose numbers and usage the workflow should touch.

Troubleshooting

  • 401 Unauthorized — the Auth Type does not match the fields filled in, for example apiKey selected with only an auth token supplied.
  • Authenticate error mentioning the SID — Account SID and API Key SID both begin with letters but are different values. The Account SID starts AC; an API key SID starts SK.
  • The ‘from’ number is not valid — the number is not owned by the account the credentials belong to, or is not enabled for that channel.
  • Trial account restrictions — unverified destination numbers are blocked on trial accounts. That is an account state, not a credential problem.

Frequently asked questions

Auth token or API key?

An API key, wherever practical. It can be revoked on its own, whereas rotating the account auth token breaks every integration using it at the same time.

Which SID goes where?

The Account SID starts with `AC` and always goes in Account SID. An API key SID starts with `SK` and goes in API Key SID — swapping them causes an authentication failure that looks like a wrong password.

Why is my 'from' number rejected?

It has to be a number owned by that Twilio account and enabled for the channel you are using. On trial accounts, destination numbers must also be verified.

Does one credential cover the Twilio node and its trigger?

Yes, both declare the same credential type.

Nodes that use Twilio API

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

Last updated . Spotted something wrong? Tell us.