Integrations
Set up WhatsApp credentials in Duaer
Store WhatsApp connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
Get a WhatsApp access token and account ID
The Duaer WhatsApp API credential needs an Access Token and a Business Account ID:
- In Meta for Developers, create a Business app and add the WhatsApp product.
- On WhatsApp > API Setup, copy the WhatsApp Business Account ID.
- The temporary access token on that page expires after 24 hours, so use it only to try things out. For long-term use, create a system user in Meta Business Settings, assign it the app and the WhatsApp account, and generate a token with the whatsapp_business_messaging and whatsapp_business_management permissions.
- Put the token and the account ID into the Duaer credential.
For the WhatsApp OAuth API type, Client ID is the Meta app ID and Client Secret is the app secret. Both are under App settings > Basic.
WhatsApp API
In Duaer, choose WhatsApp API when you create a credential, then fill in these fields:
- Access Token (required, secret)
- Business Account ID (required)
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: WhatsApp Business Cloud.
WhatsApp Bot API
In Duaer, choose WhatsApp Bot API when you create a credential, then fill in these fields:
- Access Token (required, secret): System User access token from the WhatsApp > API Setup page of the Meta app. The token shown there by default is temporary and expires in 24 hours. Use a permanent System User access token instead.
- Phone Number ID (required): The bot phone number ID, from the WhatsApp > API Setup page of the Meta app.
- WhatsApp Business Account ID (required): The WABA ID that owns the phone number, from the same API Setup page.
- App Secret (required, secret): From App Settings > Basic in the Meta app. Used to verify inbound webhook signatures.
When you save, Duaer tests the connection with these values.
WhatsApp OAuth API
In Duaer, choose WhatsApp OAuth API when you create a credential, then fill in these fields:
- Client ID (required)
- Client Secret (required, secret)
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: WhatsApp Trigger.
Save the connection in Duaer
Open Credentials and create WhatsApp. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.
Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.
Who can use this credential
Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
Questions
Do WhatsApp secret values appear in Duaer node parameters?
No. In Duaer, WhatsApp secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a WhatsApp credential from saving in Duaer?
Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields WhatsApp expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.