Overview
The Romulus Trigger node starts an n8n workflow when a specific event occurs in the Romulus system. It listens for webhook events related to calls and agent actions, enabling automation based on real-time telephony or agent activity.
Common scenarios where this node is beneficial include:
- Automating follow-up processes after a call with an agent completes.
- Triggering notifications or logging when a robocall is answered.
- Executing workflows when particular agent actions finish, such as updating CRM records or sending summary emails.
For example, you could use this node to start a workflow that updates a customer support ticket once an agent call is completed, or to log robocall answers for analytics purposes.
Properties
| Name | Meaning |
|---|---|
| Due to limitations, you can use just one Voxloud trigger for each workflow | Informational notice about usage limitation (no input expected). |
| Authentication | Method of authentication; currently supports only "API Key". |
| Event | The type of event to listen for: - Robocall Started (triggered when a robocall is answered) - Agent Call Completed (triggered when a call with an agent is completed) - Agent Action Completed (triggered when a particular agent action is completed) |
| Entity ID | Optional string to specify the ID of the entity to which the webhook should be attached. Required for "Agent Call Completed" and "Agent Action Completed" events; optional for "Robocall Started". |
Output
The node outputs the webhook payload received from Romulus as JSON data under the json field. This data represents the event details sent by Romulus when the specified event occurs.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Romulus API.
- The node interacts with Romulus REST endpoints to manage webhook subscriptions.
- No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Webhook creation errors: If the node fails to create a webhook, it throws an error indicating the failure reason. Ensure the API key is valid and has permissions to manage webhooks.
- Webhook existence check failures: The node attempts to verify if a webhook already exists before creating one. Network issues or incorrect API credentials may cause this check to fail.
- Multiple triggers limitation: Only one Voxloud (Romulus) trigger can be used per workflow due to platform limitations. Attempting to add more may cause unexpected behavior.
- Entity ID requirement: For some events, the Entity ID must be provided. Omitting it will likely cause webhook registration to fail or the webhook to not function as intended.
Links and References
- Romulus API documentation (for webhook subscription management) — consult your Romulus provider's official API docs.
- n8n Webhook Trigger documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/