Create an integration step
- 30 Jul 2023
- 1 Minute to read
- DarkLight
Create an integration step
- Updated on 30 Jul 2023
- 1 Minute to read
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
Use the Create an integration step to programmatically create integrations as part of workflow logic.
This step can be used to create integrations in different workspaces according to the credentials provided by the Torq integration or access token.
How to use
- Add the Create an integration step to your workflow.
- Specify a meaningful name for the integration you want to create.
- In the Integration type field, start typing the vendor name and select the vendor steps or trigger integration from the dropdown. The unique integration type is populated automatically according to your selection.
- Once the integration type is selected, the step parameters list will be updated to include the relevant fields (required or optional) for creating the specified kind of integration.
You can use$.integrations.<integration name>.<parameter>
to access the credentials used for the selected type of integration in the current workspace. The credentials can also be saved as workspace secrets, retrieved from an external vault, and more.ImportantThe Discard data execution option is set to Yes by default for this step, ensuring that any integration credentials, which may include sensitive data, aren't retained after the step execution. As a result, potentially sensitive information will not be accessible through the step execution log or any other system logs. - Specify a Torq integration or an access token to determine the workspace in which the integration will be created.
To use an access token:- Use the Generate Access Token step, which requires a client ID and secret.
- In the Create an integration step, click the three-dot menu next to the Torq integration field and select Set values separately.
- Provide the context path to the access token:
{{ $.generate_access_token.api_object.access_token }}
- For trigger integrations, the step output will include the integration webhook URL, which has to be provided to the third-party service to get trigger events.
Was this article helpful?