Skip to main content

Workflow Triggers in Torq: Initiating Workflow Executions

Learn about Torq's workflow triggers and how to use them efficiently.

Updated today

Every workflow begins with a trigger, defining the event that initiates the workflow execution. A trigger event consists of structured data in JSON format, which can be accessed in the workflow steps.

Trigger options include workflows started by users, events from other services, case management scenarios, and more.

Trigger types

Choose a trigger type to define how a workflow starts and what event context it receives.

  • On-demand trigger: Start a user-initiated workflow execution from Torq or other platforms, allowing customization of the trigger event.

  • Integration trigger: Ingest events from third-party services to Torq via webhooks.

  • Schedule trigger: Schedule workflows to run at specific times, such as weekly or daily intervals.

  • System events: Trigger workflows automatically based on platform-generated events, such as workflow or step failures, review requests, resource-sharing actions, and more.

  • Torq Cases: Trigger workflows with case management-related events.

  • Torq Interact: Trigger workflows using Torq's customizable web pages and forms.

Replace a trigger

You can replace an existing trigger with a different trigger type if your automation requirements change, without rebuilding the entire workflow.

  1. Open the workflow and select the trigger: Click the trigger you want to replace on the workflow canvas.

  2. Replace the trigger: Click the Replace icon above the trigger.

  3. Choose a new trigger: Select the new trigger and, if applicable, specify the integration type and integration instance.

Set trigger conditions

Add trigger conditions to determine which events will start workflow executions. More information about conditions is available here.

  1. Open the workflow and select the trigger: Click the trigger on the workflow canvas.

  2. Add trigger conditions: Click Add Condition to define trigger conditions. You can reference the event JSON using {{ $.event.<trigger event structure> }}.

  3. (Optional) Add multiple conditions: Combine conditions using AND / OR logic as needed.

  4. (Optional) Validate conditions: Open the Event Log tab to see which past events meet the current trigger conditions. Events marked with a green checkmark can trigger the workflow.

It is good practice to review trigger conditions to ensure they are well-defined and supported, and check for any conflicting conditions or missing parameters.

View event history

You can view past trigger events to monitor activity, troubleshoot issues, or verify that events were received and processed correctly.

  1. Open the workflow and select the trigger: Click the trigger on the workflow canvas.

  2. View past events: Navigate to the Event Log tab to see previous trigger events.

  3. Identify matching events: Events that meet the current trigger conditions are marked with a green checkmark.

Trigger events are retained for 90 days, with a maximum of 30 events available at a time.

Resend events

You can resend any past event, either to test the current workflow functionality or to rerun a production event.

  1. Open the workflow and select the trigger: Click the trigger on the workflow canvas.

  2. Review eligible events: Select the Event Log tab. Events marked with a green checkmark meet the current trigger conditions and can trigger the workflow.

  3. Resend an event: Select the event and click the Resend icon, or click Test Run and choose the event from the list.

  4. (Optional) Modify the event: Update the event JSON before resending, if needed.

Did this answer your question?