- 16 Feb 2023
- 1 Minute to read
- Updated on 16 Feb 2023
- 1 Minute to read
Steps are the building blocks of Torq's workflows. They are single-purpose, automated actions arranged on the designer and executed in a logical order. A step will always begin with a verb that describes the action being taken.
Torq provides public integration-based steps which are updated and added on a rolling basis. The steps library is a searchable repository of all available steps. It is divided into public and custom steps, sorted alphabetically by vendor name.
Integration steps are prebuilt API calls to external services for which Torq has built-in support. In general, these steps are configured to include the most relevant input parameters and return the API call's full response. If a system step does not contain input parameters that you want to use, you can open the step in HTTP mode, which enables you to configure the step.
Utilities are steps that help manipulate or transform data in a workflow. In the library, they are divided by topic:
- Array Utils
- Cryptographic Utils
- Date and Time Utils
- Encoding Utils
- Extraction Utils
- Object Utils
- Output Utils
- String Utils
- Utils (miscellaneous)
HTTP mode exposes additional request options for steps. Since steps are usually based on the integration's API input parameters, Torq allows you to open a step in HTTP mode and configure the step as a raw HTTP request using the vendor's API. This enables you to use the full functionality of the underlying API request.
To save you from having to go through the vendor's API documentation, execute the step pre-HTTP mode and take a look at the execution log. In most cases, the output JSON will display the rest of the supported input parameters for the API call, saving you searching time.
HTTP Request steps are a blank slate for creating custom requests and calls to external services, which you can save as custom steps for easy reuse. This step type differs from the HTTP mode because HTTP mode inherits several request parameters, such as URL, endpoint, and action from the pre-built integration step.
Create, save, and modify your own steps and share them throughout your enterprise. These could include modified integration steps, HTTP steps, utilities, cURL commands, creative uses of APIs, or steps related to vendors that Torq does not support in a pre-built manner.