Boomerangme Trigger icon

Boomerangme Trigger

Starts the workflow when Boomerangme events occur.

Overview

This node acts as a trigger for workflows based on events from the Boomerangme platform. It listens for specific Boomerangme events via a webhook and starts the workflow whenever one of these events occurs. This is useful for automating processes that depend on real-time updates or changes in Boomerangme, such as reacting to card status changes, company or customer lifecycle events, payment completions, or template activations.

Practical examples:

  • Automatically send a notification when a new company is created.
  • Update internal records when a card balance is updated.
  • Trigger follow-up actions after a payment is completed successfully or fails.
  • React to user template changes by updating related systems.

Properties

Name Meaning
Event The specific Boomerangme event to listen for. Options include various card, company, customer, payment, and template-related events such as CardBalanceUpdatedEvent, CompanyCreatedEvent, PaymentCompletedSuccessfulEvent, etc.

Output

The node outputs JSON data representing the payload received from the Boomerangme webhook for the triggered event. This JSON contains all relevant details about the event instance, allowing subsequent nodes in the workflow to process or act upon this data.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Boomerangme API.
  • Needs to be configured with a valid webhook URL accessible by Boomerangme to receive event notifications.
  • Relies on the Boomerangme API endpoint /api/automation/webhooks to register and delete webhooks dynamically.

Troubleshooting

  • Webhook registration failure: If the node cannot create the webhook on Boomerangme, ensure the API key credential is valid and has sufficient permissions.
  • Webhook not triggering: Verify that the webhook URL is publicly accessible and correctly set in Boomerangme. Also, confirm that the selected event matches the events sent by Boomerangme.
  • Deletion errors: When deleting the webhook, network issues or invalid webhook IDs may cause failures. These are handled gracefully but check logs if triggers persist unexpectedly.
  • Unexpected payloads: Since the node passes through the raw event data, downstream nodes must handle variations in event structure.

Links and References

Discussion