Reference · Credentials
Facebook Lead Ads OAuth2 credentials
Used by 1 BusyBot node.
Type
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 and are never shown again after saving.
- 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.
Nodes that use Facebook Lead Ads OAuth2
One credential works across every node below — create it once and reuse it.