Steps are the building blocks of Torq workflows. Each step automates a specific action, executed in a logical sequence to achieve your workflow's goal. Torq continuously expands its step library by adding new steps and enhancing existing ones.
Builderbox
The Builderbox gives you access to a wide range of pre-configured steps and the flexibility to create custom steps.
The Builderbox organizes steps into the following categories:
Operators: Logic-driven steps that define the flow and progression of a workflow.
Integrations: Ready-to-use steps for connecting with external services, pre-configured to perform key tasks. HTTP-based steps can be switched to HTTP mode to modify the underlying API request. Use the Send an HTTP request step to create custom requests to external services, which can be saved as custom steps for reuse.
Cases: Steps for automating Torq's HyperSOC.
Utilities: Out-of-the-box steps for manipulating or transforming data, including categories for arrays, strings, dates, and more.
Custom steps: Steps you create through modified integration steps, HTTP requests, cURL commands, and more. All custom steps created for the workspace appear under this tab.
Build your workflow
Find steps: Browse the Builderbox or use the search bar to find a step. Integration step search results are ranked by relevance, using a mix of exact keyword, typo-tolerant, and meaning-based matching. In the Integrations section, toggle to Configured to show only steps for integrations that are already set up in the workspace.
Drag and drop: Drag the step to the desired drop point in the Workflow Designer.
Configure step parameters: Set the step parameters so your step runs as intended. A warning icon in the top right of a step or next to it indicates that a required input parameter may be missing, or that an update is available. Click the warning icon for details and to make fixes.
QuickBuild
Operators and steps are also accessible directly in the Designer using QuickBuild:
Click the drop point: Select the drop point where you want to add your next step.
Find your step: Click the Operator icon or search for the step you need.
(Optional) Use Co-Builder: Let Co-Builder guide your next move in the workflow.
Configure workflow steps
Once a step is added to a workflow, click on it to configure its properties.
Parameters
The Step Properties tab displays all required input parameters. Optional parameters are hidden by default, click the cogwheel next to Parameters to access additional settings such as timeout, SSL verification, and more. Not every step includes optional parameters.
Execution options
The Execution Options section in the Properties tab includes the following settings:
Runner: Executes steps using the specified arguments via Kubernetes or Docker. If no runner is set, steps run on Torq's secure, hosted step runner service in the cloud. Steps using cloud-to-cloud communication can use the default runner. Steps requiring access to private VPCs or data centers require a self-hosted step runner deployed in those environments.
Ignore failure: By default, a failed step stops the entire workflow and marks it as failed. Set to Yes to allow the workflow to continue even if the step fails.
Retry after: Configure the workflow to retry a failed step after a specified delay for a set number of attempts. Without this setting, failed steps will not retry.
Discard data: Set to Yes to discard all step data once the workflow completes, making it inaccessible in the step execution log. Any files generated by the step are also discarded. Useful when handling sensitive data.
Return the response as file: Set to Yes to receive step results as a file. Useful for binary content or large data sets that exceed the step output size limit. You will receive a file link and details in JSON format.
Shareable link: Set to Yes to generate a link that can be shared with third parties for a limited time. By default, file links are private and can only be used within Torq steps. This option is only visible when Return response as file is set to Yes.
Reference step output examples
Once a step is executed, its output is available in the workflow context for subsequent steps. If you prefer to continue building without executing the step first, check whether it has an example output, this lets you reference its data using autocomplete or tree mode in later steps.
View output example: Select the step to open the Properties panel, then choose Output Example from the three-dot (...) menu.
Torq also supports mock outputs, allowing you to simulate step executions with preconfigured responses for testing purposes without making actual API calls.
View the Execution Log
The Step Execution Log tab records all step executions, whether run standalone or as part of a workflow. Use it to verify that the step response received is as expected, helping you build more reliable and efficient workflows.
Both successful and failed executions are logged. In the case of failure, the step status code provides insight into the cause. Execution history is retained for the past 30 days.
Each log entry includes:
Execution ID
The entity that triggered the execution (workflow or user)
Execution time and duration
Step input and output JSON objects
Execution debug details
Single step executions
You can execute individual steps to test how a step will run without running the entire workflow.
Execute a step: Click the step you want to test, then click the Execute icon. The Execution Log opens automatically and displays the results.
Step status codes
When a step runs, Torq returns a status code in the Execution Log indicating the success or failure of the operation. If there's an error, you'll see the reason and a suggested solution. The HTTP status code is also shown if the step made an HTTP request.
Step status code | Status | Description | HTTP status code |
1 | OK | The step was executed successfully. | 2xx |
2 | InvalidArgument | One or more input parameters contain an invalid value. | — |
3 | DeadlineExceeded | The step's operation timed out. | 408 |
4 | NotFound | The requested resource or entity was not found. | 404 |
5 | AlreadyExists | The resource or entity you tried to create already exists. | — |
6 | PermissionDenied | Insufficient permissions to perform this operation. | 403 |
7 | Aborted | The step execution was aborted (not failed). | — |
8 | OutOfRange | The operation is being performed on data outside the available range (for example, accessing an index item that doesn't exist). | — |
9 | Internal | An internal system error caused the step to fail. | 500 |
10 | Unavailable | The step's service is currently unavailable. Try executing the step again. | — |
11 | Unauthenticated | Invalid authentication credentials. | 401 |
12 | On hold | The step is waiting for user input (for example, Ask a question). | — |
Disable steps
Disabling a step keeps it in the workflow but excludes it from execution. If subsequent steps depend on the disabled step, you may need to adjust some settings for the workflow to run correctly.
Disable a step: Select the step in the Designer and click the Disable icon in the menu above it.
