In addition to Torq's 200+ public Integrations, Torq offers a powerful custom integration builder that gives you complete flexibility. Torq empowers you to seamlessly connect with every application and service that matters most to your organization while tailoring the integrations to meet your specific needs.

Torq supports the custom creation of both step and trigger integrations. Once created, your custom integrations will be accessible to anyone building within the workspace - and can be easily shared throughout your organization.

You must have the role of Workspace Creator or above to create a custom integration.

Create a Custom Steps Integration in Torq with Custom Parameters

Navigate to Integration Builder: Go to Build > Integrations and click Create New > Integration.
Fill in Integration Details:
1. Under Type, select Steps.
2. Under Name, enter the name of the application or vendor (for example, Microsoft Outlook)
3. Under Description, type a brief description of the integration, such as Perform API calls from your Microsoft Outlook account with this step integration.
4. Under Logo URL, enter the URL of the logo in PNG/SVG format.
5. Under Documentation Link, enter the link to the vendor's API documentation.
Next: Click Next to finalize the details. You can click Back if you want to change anything later.
Authentication Method: Pick the Custom authentication method.
Set Parameters: Set the parameters needed to configure the integration. These parameters are completely customizable and will be available when you create all future instances of the custom integration and steps for the integration. You must add at least one parameter to continue.
1. The Instance name parameter is added by default. This will be the name of the integration instance.
2. To add a new parameter, click Add Parameter.
3. Select a parameter type. Parameters types can be one of two types:
  1. Short Text for non-sensitive data (URLs, usernames, etc.)
  2. Secret for sensitive data (client secrets, tokens, API keys, etc.).
4. Optionally, add a description. This will appear as a tooltip above the parameter name.
5. Optionally, add a placeholder. This will appear in the parameter box as an example for the user.
6. If the parameter is required to configure the integration, check the Required box. Otherwise, the parameter will be viewed as optional, and the user may not fill it out when completing the integration instance setup.
Next: Click next to finalize the parameters. You can click Back if you want to change anything later.
Test Setup: Optionally, under Test Setup, configure a test to verify the integration instance’s connection.
1. URL: The vendor's endpoint to which the test request will be sent.
  1. Choose an endpoint that won't count against your API quota, as it will be called each time someone tests their instance. For example, https://login.microsoftonline.com/{{ .TENANT_ID }}/oauth2/v2.0/token.
    In some cases the endpoint needs to include dynamic information specific to the instance being tested, such as {{.TENANT_ID}} in the example above.
    To configure this, write the endpoint with the dynamic information like this: https://login.microsoftonline.com/(tenantID}/oauth2/v2.0/token
    Manually highlight the {tenantID}.
    Click Assign to Existing Parameter and select the Tenant ID parameter you setup in the Integration earlier.
2. Method: Select the appropriate HTTP method required by the endpoint. In the example above, the call is a POST request.
3. Authorization: Pick the authorization needed for the API call. The options are None, Basic, or Bearer.
  1. If needed, add the relevant headers for the authorization.
4. Content-Type: Optionally, specify the content type as specified in the vendor's API documentation.
5. Body: Optionally, include a Body if required for the API call.
6. HTTP Optional Parameters: The Timeout and Skip SSL Verification parameters are optional.
  1. Use Timeout if the request may take longer than expected or if you anticipate potential errors without a timeout.
  2. Use Skip SSL Verification if the vendor's API documentation recommends skipping SSL verification.
Finalize: Click Save and Publish.
Optionally Create Instance: You can click Create Instance on the confirmation page to instantly navigate to your new Integration's page and create a new instance of that trigger integration, or click Edit to edit the integration you just created.

After finalizing your custom step integration, be sure to create custom steps for it by going to Build > Integrations > Create New > Step.

Create a Custom Trigger Integration in Torq

Navigate to Integration Builder: Go to Build > Integrations and click Create New > Integration.
Fill in Integration Details:
1. Under Type, select Trigger.
2. Under Name, enter the name of the application or vendor (for example, Microsoft Outlook)
3. Under Description, type a brief description of the integration, such as Receive alerts from your Microsoft Outlook account with this trigger integration.
4. Under Logo URL, enter a URL of the application or vendor logo.
5. Under Documentation Link, enter the link to the vendor's API documentation.
Finalize: Click Save and Publish.
Optionally Create Instance: You can click Create Instance on the confirmation page to instantly navigate to your new Integration's page and create a new instance of that trigger integration, or click Edit to edit the integration you just created.

Setting Up Integrations in Torq: Connecting to Third-Party Services

Create a Custom Integration: Build Integrations to Specifications

Create a Custom Steps Integration in Torq with Custom Parameters

Create a Custom Trigger Integration in Torq