Creating integrations in Torq allows for seamless connections with third-party services. This guide provides an overview of trigger and step integrations, enabling you to create efficient and responsive workflows. By integrating Torq with your security stack, you can receive real-time data via trigger integrations and perform actions in external systems through step integrations.
Understanding Torq integrations
There are two primary types of integrations in Torq:
Trigger integrations
These allow Torq to receive alerts, events, and other data from external services. Setting up a trigger integration involves:
Generating an endpoint: Create the integration in Torq to receive a unique endpoint URL.
Configuring the external service: Input the Torq endpoint URL into the third-party service to direct its data outputs to Torq.
Step integrations
These are authenticated connections that enable interactions with third-party services directly within Torq workflows. These integrations are generally bidirectional, enabling data exchange between Torq and the external service. Common authentication parameters include:
API Key
API Secret
Client Key
Client Secret
Username
Password
App ID
Tenant URL
For further assistance or advanced configurations, refer to the specific integration guides available in the Torq Knowledge Base.
Set a default integration instance
You can set a default integration instance for step integrations to streamline workflow building and AI tool configuration. When a default is defined, Torq automatically selects it whenever that integration is used, eliminating the need to manually choose an instance each time.
This reduces friction, speeds up configuration, and helps prevent errors caused by selecting the wrong integration, especially when the same integration is used repeatedly across workflows. You can still override the default on a per-step basis whenever needed.
How default integrations work
Default integrations take effect from the moment they’re set onward; existing workflows and configurations aren’t updated automatically. For each integration step, at most one instance can be set as the default.
By default, the first integration created for a vendor, including the first shared integration, is automatically set as the default. If a default integration is shared into another account and it’s not the first integration for that vendor in the destination account, it won’t be set as default there.
When integrations are shared, users in the destination account can choose to set the shared integration as their default. If a default integration is deleted, it’s simply removed and no replacement default is assigned automatically. Likewise, if a shared integration that’s set as default is later unshared or deleted from the source account, the default designation is cleared in the destination account with no automatic reassignment.
Configure a default integration instance
Navigate to Integrations: In Torq, go to Build > Integrations > Steps.
Select an integration: Click the integration you want to configure.
Set as default: Click the three-dot (...) menu on the right side of the integration instance row and select Set as default.
Use the default integration in a step
Add the integration step: Add the relevant integration step to your workflow.
Verify the default selection: Select the step and open Properties. The default integration instance is automatically selected and clearly labeled as Default. You can change it if needed.
