Reference · Credentials
Connect WhatsApp Business (Trigger) to BusyBot
Used by 1 BusyBot node.
Type
whatsAppTriggerApi 2 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Client IDclientId | string | Yes | Your Facebook App ID |
Client SecretclientSecret | password | Yes | Your Facebook App Secret |
Setting up WhatsApp Business (Trigger)
- In WhatsApp Business (Trigger), create the credential this connection needs — the values listed in the table above. These are issued from your own WhatsApp Business (Trigger) account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose WhatsApp Business (Trigger).
- Paste each value into the matching field and save.
- Add the WhatsApp 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 WhatsApp Business (Trigger) credentials?
One node: WhatsApp Trigger. Create the credential once and select it in that node.
What does a WhatsApp Business (Trigger) credential need?
2 fields: Client ID, Client Secret. Required: Client ID, Client Secret. The values come from your own WhatsApp Business (Trigger) account.
How are WhatsApp Business (Trigger) 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 WhatsApp Business (Trigger)
One credential works across every node below — create it once and reuse it.