Torq

Trigger Torq workflows from any event within your security stack. Torq securely communicates with any application via dedicated webhooks, allowing you to automate alert cataloging, ticket management, incident management, identity verification, and much more.

After you create a trigger integration in Torq you will receive a webhook you can provide to the third-party service from which you want to get events. Every service has a different process for receiving webhooks, so we recommend you check out the Torq integration documentation for relevant information. Torq does not normalize or manipulate the trigger event JSON.

Create a trigger integration with the third-party service from which you want to get events (you can also use the webhook integration).

Select the Integrations trigger when creating a new workflow.

1. You can also click on the replace icon above an existing trigger to change it to an integration trigger.

Select the integration instance from which you want to get events.

Integration events can be viewed in the trigger Event Log.

Use the trigger event data in workflow steps: $.event.&lt;event_structure&gt;. Test Run the workflow with an integration event to make sure your workflow is running as expected.

Publish the workflow so it can be executed automatically when a new integration event occurs. You can also apply <a href="#h_323a1c460a">trigger conditions</a>.​

1. Create a trigger integration with the third-party service from which you want to get events (you can also use the webhook integration).
2. Select the Integrations trigger when creating a new workflow.
 1. You can also click on the replace icon above an existing trigger to change it to an integration trigger.
3. Select the integration instance from which you want to get events.
4. Integration events can be viewed in the trigger Event Log.
5. Use the trigger event data in workflow steps: $.event.&lt;event_structure&gt;. Test Run the workflow with an integration event to make sure your workflow is running as expected.
6. Publish the workflow so it can be executed automatically when a new integration event occurs. You can also apply <a href="#h_323a1c460a">trigger conditions</a>.​

After an event JSON is received, you can modify and resend it. This enables you to test different trigger event parameters and scenarios to see how they impact the workflow.

There are 2 ways to resend an integration event:

- Click Run Workflow if the workflow is published or Test Run in draft mode. Search for a specific event or select the last one.
- Go to the trigger Event Log, select an event, and click Resend. ​NoteTrigger events are available for 90 days up to 30 events.

Change the trigger event fields or their values as necessary and click Test Run.​

1. There are 2 ways to resend an integration event:
 - Click Run Workflow if the workflow is published or Test Run in draft mode. Search for a specific event or select the last one.
 - Go to the trigger Event Log, select an event, and click Resend. ​NoteTrigger events are available for 90 days up to 30 events.
2. Change the trigger event fields or their values as necessary and click Test Run.​

You can apply conditions to specify which integration events will trigger the workflow. For example, specify an event type. Events from the same integration with a different event type will not trigger the workflow, but you can see them in the trigger Event Log.

Additional information on conditions is available <a href="https://kb.torq.io/en/articles/9110256-understanding-conditions-in-torq-workflows">here</a>.

How to Use

Resend a Trigger Event

Trigger Conditions