BusyBot
Search all guides

Reference · Credentials

Connect X (Twitter) to BusyBot

Used by 1 BusyBot node.

Type twitterOAuth2 4 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes —
Refresh Token
refreshToken		 password No —
Client ID
clientId		 string No —
Client Secret
clientSecret		 password No —

Setting up X (Twitter) OAuth2

  1. In X (Twitter) OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own X (Twitter) OAuth2 account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose X (Twitter) OAuth2.
  3. Paste each value into the matching field and save.
  4. Add the X (Twitter) 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 X (Twitter) credentials?

One node: X (Twitter). Create the credential once and select it in that node.

What does a X (Twitter) credential need?

4 fields: Access Token, Refresh Token, Client ID, Client Secret. Required: Access Token. The values come from your own X (Twitter) account.

How are X (Twitter) 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.

Does X (Twitter) use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret): you approve access in X (Twitter), and the resulting tokens are stored encrypted like every other credential.

Nodes that use X (Twitter) OAuth2

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