Skip to main content
All CollectionsIntegrate Everything
Setting Up Integrations in Torq: Connecting to Third-Party Services
Setting Up Integrations in Torq: Connecting to Third-Party Services

This guide introduces Torq integrations, explaining how to connect seamlessly with third-party services using trigger and step integrations.

Updated over a week ago

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:

  1. 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.

  2. 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.

Did this answer your question?