Integrations
Start a Duaer workflow with WhatsApp Trigger
In Duaer, WhatsApp Trigger starts a workflow when WhatsApp sends an event. It can listen for 10 events, such as Account Review Update, Account Update, Business Capability Update, and 7 more.
Start a Duaer workflow with WhatsApp Trigger
- On the Duaer canvas, open the node panel, search for WhatsApp Trigger, and add it as the first node.
- In Credential to connect with, pick or create a WhatsApp OAuth API credential. Refer to WhatsApp Trigger credentials.
- Pick the events that should start a run, for example Account Review Update or Account Update.
- If needed, select Add Option for the optional settings listed below.
- Select Execute step, then cause a real event in WhatsApp to capture a sample. Publish the workflow so Duaer registers the webhook and starts a run for every event.
Events that start a Duaer workflow with WhatsApp Trigger
Account Review Update, Account Update, Business Capability Update, Message Template Quality Update, Message Template Status Update, Messages, Phone Number Name Update, Phone Number Quality Update, Security, Template Category Update.
WhatsApp Trigger options in Duaer
Under Add Option, WhatsApp Trigger offers Receive Message Status Updates.
Questions
Which WhatsApp Trigger events can start a Duaer workflow?
Duaer's WhatsApp Trigger can listen for 10 events, including Account Review Update, Account Update, Business Capability Update, Message Template Quality Update, Message Template Status Update, and 5 more. Pick one or more on the node.
Does WhatsApp Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the WhatsApp Trigger webhook for production runs after you publish.
Which credential does WhatsApp Trigger use in Duaer?
Duaer's WhatsApp Trigger uses a WhatsApp OAuth API credential. The secret stays in the credential, not in node parameters.
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.