Integrations

Integrations are connections to third-party services, a.k.a., vendors. Torq has two types of integrations:

• Trigger
• Steps

Trigger integrations

Trigger integrations send alerts, events, and other data from third-party services as JSON payloadsto Torq. 

When you create a trigger integration, a unique Torq endpoint (URL) is generated. You'll use this URL in a third-party service to tell it where to send events.

Where and how you enter the URL and define the alerts to send to the URL will depend on the service.

Step integrations

Step integrations are authenticated connections to third-party services, that enable you to interact with the service's steps in Torq workflows. Each vendor step is a security opinionated implementation of vendor APIs. You can always expose the underlying API call to extend the functionality of the API. These integrations are generally bi-directional, passing data from Torq -> Vendor and  Vendor -> Torq .

The form of authentication depends on the service you're using. Here are some of the most common parameters used for authentication.

• API key
• API secret
• Client key
• Client secret
• User name
• Password
• App ID
• Tenant URL

Example: Box integration in Torq