Romulus Trigger icon

Romulus Trigger

Starts the workflow when a Romulus event occurs

Romulus Trigger

AI-generated

Overview

The Romulus Trigger node starts an n8n workflow when specific Romulus events occur, such as when a robocall is answered, an agent call is completed, or an agent action is completed. It is useful for automating processes based on telephony or agent activity events, for example, triggering follow-up actions after a call or monitoring specific agent activities.

Use Case Examples

  1. Trigger a workflow when any robocall starts to log call details or notify a team.
  2. Start a workflow when a specific agent completes a call to update CRM records.
  3. Monitor all agents' completed actions to generate performance reports automatically.

Properties

Name Meaning
Event The specific Romulus event to monitor, such as robocall started, agent call completed, or agent action completed.
Scope Determines whether to monitor all agents or a specific agent for agent-related events.
Agent Name or ID Selects the specific agent to monitor for events, applicable when scope is specific and event is agent-related.
Scope (Robocall) Determines whether to monitor all robocall configurations or a specific one for robocall events.
Robocall Configuration Name or ID Selects the specific robocall configuration to monitor, applicable when robocall scope is specific.

Output

JSON

  • json - The JSON payload received from the Romulus webhook event, containing event-specific data.

Dependencies

  • Requires Romulus API credentials for authentication and API requests.

Troubleshooting

  • Webhook creation or deletion may fail if the Romulus API credentials are invalid or lack necessary permissions.
  • Loading agents or robocall configurations may fail due to API errors or network issues; ensure the API is reachable and credentials are correct.
  • If the webhook does not trigger, verify the webhook URL is correctly registered in Romulus and the event and scope settings match the expected events.

Links

Discussion