Reference · Credentials
Connect Facebook Lead Ads to BusyBot
Used by 1 BusyBot node.
facebookLeadAdsOAuth2 5 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Access TokenaccessToken | password | Yes | Facebook User OAuth2 access token |
App IDclientId | string | Yes | Your Facebook App ID. |
App SecretclientSecret | password | Yes | Your Facebook App Secret. |
Refresh TokenrefreshToken | password | No | OAuth2 refresh token. Required for automatic token renewal. Leave blank only if the token never expires. |
Token Expiry (Unix timestamp)expiresAt | string | No | Unix timestamp (seconds) when the access token expires. Managed automatically after refresh. |
Setting up Facebook Lead Ads OAuth2
- In Facebook Lead Ads OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own Facebook Lead Ads OAuth2 account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Facebook Lead Ads OAuth2.
- Paste each value into the matching field and save.
- Add the Facebook Lead Ads 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 Lead Ads credentials?
One node: Facebook Lead Ads Trigger. Create the credential once and select it in that node.
What does a Facebook Lead Ads credential need?
5 fields: Access Token, App ID, App Secret, Refresh Token, Token Expiry (Unix timestamp). Required: Access Token, App ID, App Secret. The values come from your own Facebook Lead Ads account.
How are Facebook Lead Ads 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 Facebook Lead Ads use OAuth?
Yes. This credential connects through OAuth (fields: Access Token, App ID, App Secret, Refresh Token, Token Expiry (Unix timestamp)): you approve access in Facebook Lead Ads, and the resulting tokens are stored encrypted like every other credential.
Nodes that use Facebook Lead Ads OAuth2
One credential works across every node below — create it once and reuse it.