BusyBot
Search all guides

Reference · Credentials

Connect Facebook Graph API (App) to BusyBot

Used by 1 BusyBot node.

Type facebookGraphAppApi 2 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes Facebook Graph API access token
App Secret
appSecret		 password Yes Facebook App Secret for webhook HMAC-SHA256 signature validation. Required to verify incoming webhook authenticity.

Setting up Facebook Graph API (App)

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

One node: Facebook Trigger. Create the credential once and select it in that node.

What does a Facebook Graph API (App) credential need?

2 fields: Access Token, App Secret. Required: Access Token, App Secret. The values come from your own Facebook Graph API (App) account.

How are Facebook Graph API (App) 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.

Nodes that use Facebook Graph API (App)

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