BillRun Trigger
AI-generatedOverview
This node acts as a trigger for workflows based on events occurring in the BillRun system. It listens for specific actions on various BillRun modules such as Accounts, Bills, Balances, Collection, and others. When an event matching the selected module and action occurs, the node triggers the workflow, passing the event data to subsequent nodes. This is useful for automating processes like reacting to account updates, bill creations, payment events, or collection status changes in a billing system.
Use Case Examples
- Trigger a workflow when a new account is created to send a welcome email.
- Start a process when a bill is updated to notify the finance team.
- Automate collection steps by triggering workflows when accounts enter or exit collection.
Properties
| Name | Meaning |
|---|---|
| Module | The BillRun module on which to trigger the action, e.g., Accounts, Bills, Balances, Collection, etc. |
| Action | The specific action on the selected module to trigger the workflow, such as create, update, close, delete, reopen, permanent change, and other module-specific actions. |
| Collection Step | The name of the collection step to trigger on when using the 'Custom Collection Step' action in the Collection module. |
Output
JSON
body- The JSON payload received from the BillRun webhook representing the event data that triggered the workflow.
Dependencies
- An API key credential for BillRun API access
Troubleshooting
- Ensure the webhook URL is correctly configured in BillRun to send events to this node.
- Verify that the selected module and action match the events configured in BillRun to avoid missing triggers.
- Check API credentials and permissions if webhook creation or verification fails.
- Common error: 'Webhook not found' - occurs if the webhook was deleted or not created properly; re-create the webhook in the node settings.
Links
- BillRun API Webhooks Documentation - Official documentation for BillRun webhook setup and event types.
