Integrations
Start a Duaer workflow with Chargebee Trigger
In Duaer, Chargebee Trigger starts a workflow when a request reaches its URL. It can listen for 34 events, such as Card Added, Card Deleted, Card Expired, and 31 more.
Start a Duaer workflow with Chargebee Trigger
- On the Duaer canvas, open the node panel, search for Chargebee Trigger, and add it as the first node.
- Pick the events that should start a run, for example Card Added or Card Deleted.
- Select Execute step and send a test request to the node's Test URL. Publish the workflow so its Production URL starts a run for every request.
Events that start a Duaer workflow with Chargebee Trigger
Card Added, Card Deleted, Card Expired, Card Expiring, Card Updated, Customer Changed, Customer Created, Customer Deleted, Invoice Created, Invoice Deleted, Invoice Generated, Invoice Updated, Payment Failed, Payment Initiated, Payment Refunded, Payment Succeeded, Refund Initiated, Subscription Activated, Subscription Cancellation Scheduled, Subscription Cancelled, Subscription Cancelling, Subscription Changed, Subscription Created, Subscription Deleted, Subscription Reactivated, Subscription Renewal Reminder, Subscription Renewed, Subscription Scheduled Cancellation Removed, Subscription Shipping Address Updated, Subscription Started, Subscription Trial Ending, Transaction Created, Transaction Deleted, Transaction Updated.
Questions
Which Chargebee Trigger events can start a Duaer workflow?
Duaer's Chargebee Trigger can listen for 34 events, including Card Added, Card Deleted, Card Expired, Card Expiring, Card Updated, and 29 more. Pick one or more on the node.
Does Chargebee Trigger run before the Duaer workflow is published?
Only the Test URL works while you test with Execute step. The Production URL starts runs after you publish the Duaer workflow.
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.