BusyBot

Reference · Credentials

Trello API credentials

Used by 2 BusyBot nodes.

Type trelloApi 3 fields

The Trello credential needs a key and a token from Trello's developer page, and they play different roles: the key identifies the application, the token authorises it to act as your account. The trigger additionally needs the OAuth secret to verify incoming webhooks.

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes Trello API key from https://trello.com/app-key
API Token
apiToken		 password Yes Trello API token generated for the API key
OAuth Secret
oauthSecret		 password No Trello OAuth/API secret used to verify HMAC signatures on incoming webhook requests. Required when using the Trello trigger; find at https://trello.com/app-key under the API key entry.

Getting your credentials

  1. Sign in to Trello and open trello.com/app-key.
  2. Copy the API Key shown there.
  3. On the same page, follow the link to generate a Token. Trello asks you to authorise the key against your account and shows the token once — copy it.
  4. Paste both into the credential’s API Key and API Token fields.
  5. If you use the Trello trigger, copy the secret shown alongside the API key into OAuth Secret. It verifies the HMAC signature on incoming webhook requests.

Permissions and scopes

The token authorises access as your Trello account, so boards you cannot see are invisible to the automation. When generating the token you can choose its expiry — a never-expiring token is convenient and correspondingly more valuable if leaked.

Troubleshooting

  • 401 unauthorized permission requested — the token was generated for a different API key, or lacks write access. Key and token must belong together.
  • Board or card not found — the account behind the token is not a member of that board.
  • Trigger rejects webhooks — the OAuth Secret is missing or does not match the API key it was issued with.
  • Token stopped working — it expired, or was revoked from your Trello account settings.

Frequently asked questions

Why are there both a key and a token?

The key identifies the application and the token authorises it to act as your account. They are generated together and only work as a pair.

When do I need the OAuth Secret?

For the Trello trigger, which uses it to verify the HMAC signature on incoming webhook requests. Action-only workflows do not need it.

Does the token expire?

That depends on what you chose when generating it. A never-expiring token avoids surprises but is more valuable to an attacker, so rotate it if it may have been exposed.

Nodes that use Trello API

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

Last updated . Spotted something wrong? Tell us.