The new Builderbox is now available.
You can still switch to the previous version if needed.
Steps are the building blocks used to create workflows. Each step automates a specific action, executed in a logical sequence to achieve your workflow’s goal. Torq is constantly improving by adding new steps and enhancing existing ones.
The Builderbox gives access to a wide range of pre-configured Steps and the flexibility to create custom steps easily.
Builderbox Overview
Use the Builderbox to access the different types of steps to build your workflows:
Operators: Logic-driven steps that define the flow and progression of a workflow.
Integrations: Ready-to-use steps for connecting with external services. Pre-set to perform key tasks using basic settings.
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. These requests can be saved as custom steps for easy reuse.
Cases: Steps for automating Torq's HyperSOC.
Utilities: Out-of-the-box steps for manipulating or transforming data based on common and reusable logic. Categories include steps for arrays, strings, dates, and more.
Custom steps: You can create your own steps through modified integration steps, HTTP requests, cURL commands, and more. Any custom steps created for the workspace are shown under this tab.
Build Your Workflow
Use the Builderbox to access the different types of Torq Steps.
Find Steps: Browse the Builderbox, or use the search bar to find the step you are interested in.
Integration Steps 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 set up in the workspace.
Drag and Drop: Drag the step to the 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 or next to a Step is an indicator that:
A step might be missing a required input parameter, and/or
A step could have an update waiting.
Click the warning icon to find out more and make fixes.
QuickBuild
Operators and Steps are also accessible directly in the Designer using the QuickBuild. Click on the drop point where you want to add your next step. Click on the Operator icon or search for the Step you need, or use the Co-Builder to guide your next move in the workflow.
Configure Workflow Steps
Once a step is added to a workflow, click on the step to configure its properties.
Parameters
The Step Properties tab displays required input parameters. If necessary, click the cogwheel icon to add optional parameters.
Execution Options
Additional settings are available in the Execution Options section, in the Properties tab:
Runner: The Step Runner executes steps using the specified arguments.
It uses Kubernetes or Docker to schedule the execution and retrieve the output.
If no runner is set, steps are executed on Torq's secure, hosted step runner service in the cloud.
Steps that use cloud-to-cloud communication and leverage public cloud APIs can be executed on the default runner. Steps that require access to components hosted in private VPCs or data centers will require deploying a self-hosted step runner in these environments.
Ignore failure: By default, if a step fails, the whole workflow stops and is marked as failed.
If set to Yes, the workflow will continue even if the step fails.
Retry after: Set your workflow to retry a failed step after a specified delay for a set number of attempts. Without this setting, failed steps won’t retry.
Discard data: If set to Yes, any data from the step is discarded once the workflow is done and isn't accessible in the step execution log.
Any files generated by the step are also discarded.
Useful, for example, when dealing with sensitive data in a step.
Return the response as file: Choose Yes to receive step results as a file.
Useful for binary content, such as pictures or big data sets that exceed the step output size limit.
You'll get a file link and details in JSON format.
If set to Yes, you will see the Shareable link option explained below.
Shareable link: Select Yes to get a link that can be shared with third parties for a limited time.
By default, file links are private and can only be used in Torq steps.
The Shareable link toggle is only visible when the Return Response As File toggle 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 keep building without executing the step, check if it has an example output—this allows you to reference its data using autocomplete or tree mode in later steps.
To view a step's output example, select the step to open the Properties panel and choose Output Example from the three-dot menu.
Torq also supports mock outputs, enabling 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 standalone or part of the workflow. Boost workflow reliability and efficiency by checking that the step response received is as you expected, aiding in more robust workflow builds.
Both successful and failed step executions are logged, and in the case of failure, the step status code offers insights into the cause. The step execution history is retained for the past 30 days
Each log entry includes:
the execution ID
the entity that executed the step (workflow or user)
the execution time and duration
the step input and output JSON objects, and
execution debug details.
Single Step Executions
Users can execute individual steps to test how a step will run without executing the whole workflow. Click on the step you want to run and then click the Execute icon. The Execution Log is automatically opened and displays the results.
Step Status Codes
When you run a step, Torq returns a status code in the Execution Log to indicate the success or failure of the operation. If there's an error, you'll get the reason the error occurred and a suggested solution. You can also see the HTTP status code if the step made an HTTP request.
Table of status codes
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 step's operation. | 403 |
7 | Aborted | The step execution was aborted (not failed). | - |
8 | OutOfRange | The step's operation is trying to be 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. You can try to execute the step again. | - |
11 | Unauthenticated | Invalid authentication credentials | 401 |
12 | On hold | Generally seen for steps waiting for user input, for example, Ask a question. | - |
Disable Steps
Disabling a step keeps it in the workflow but excludes it from being executed as part of the workflow execution. To disable a step, select it in the Designer and click the Disable icon in the menu above it. If subsequent steps depend on the disabled step, you might need to change some settings for the workflow to run correctly.
