Torq offers hundreds of integrations and Steps out of the box, providing extensive functionality. Occasionally, you might need to expand Step capabilities or address specific needs. In these cases, create custom Steps quickly and easily, ensuring you have the precise functionality required for your Workflows.
There are several ways to create a custom Step, and you can use the Step Builder to save these for future use in your workspace:
When importing or exporting Workflows between workspaces, any custom Steps (or integrations) within the Workflow will also be imported/exported.
Create an HTTP request Step
An accessible way to create your own Step is to send a custom HTTP request. You can use the AI generator to generate the HTTP request or the Step Builder to create a custom Step that you can use again in the future.
Open Your Workflow: Navigate to the Workflows page and open or create a new Workflow.
Add an HTTP Request Step: In the Builderbox, search for Send an HTTP Request and add the Step to the Workflow.
Configure the Step:
Enter an AI Prompt: In the Generate HTTP Request with AI input field, enter a natural language description of the desired action and click the AI complete icon.
Alternatively, click the wand icon to open the Step Builder.
Save the work you do in the Step Builder. If you close it without saving, all work on the custom Step will be lost.
Use the Step: This Step is now available for the workspace under the Custom tab in the Builderbox.
Optional parameters
Access the optional parameters by clicking on the Settings icon in the Parameters section of the Step. Some of the notable available options include:
Timeout: This will set the Step to end automatically after a specified period of inactivity. This prevents the Step from executing indefinitely.
Skip SSL verification: SSL verification is the process of confirming a website's certificate, which ensures secure and encrypted communication between the client and server.
Ignore redirects: If the call requires over three redirects, they will be ignored.
HTTP proxy: Provide an intermediary server to send the requests to the servers. This enhances security and privacy.
Convert a public Step to HTTP mode
HTTP-based integration Steps can be switched to HTTP mode to modify the underlying API request. HTTP mode exposes additional HTTP request options. Since integration Steps are usually a subset of the vendor's API calls' input parameters, HTTP mode can configure the Step as a raw HTTP request and use the full functionality of the underlying API request.
The changes to the API request will only apply to this Step in the Workflow you are building.
Switch to HTTP Mode: Click the two arrows icon in the Step Parameters section to convert the Step to HTTP mode. Click Convert to confirm the switch. Note that after you switch to HTTP mode, you cannot switch back to Basic mode.
Configure the HTTP Request: Modify the request options as needed.
Example: HTTP Mode for Dropbox Step
Example: HTTP Mode for Dropbox Step
The only parameter the Get member list Dropbox step has is the integration.
Click the two arrows icon to convert the Step to HTTP mode. Now, you'll be able to edit the API call to suit your needs.
For example, you can provide a different access token than the one used by the integration. The out-of-the-box step can only use the access token provided by its input parameter, the Dropbox integration.
Create a custom Step from a public Step
Sometimes, you may want to create a custom Step from a public Step instead of converting it to HTTP mode. The custom Step will then be available for future use in the workspace under the Custom tab in the Builderbox.
Find the public Step: Find the Step you want to customize and add it to your Workflow.
Create custom Step: Click the wand icon in the Step configuration window. Follow the Step Builder instructions and save your work. If you close the wizard without saving, all work on the custom Step will be lost.
Create a Step from a cURL command
Create an HTTP request Step by pasting (similar to copy-pasting) an API call in the form of a cURL command (for example, from vendor documentation) into the Designer.
Prepare the cURL Command: Copy the cURL command that executes the API call you want to run in Torq.
curl -X GET "https://api.shodan.io/shodan/host/8.8.8.8?key={YOUR_API_KEY}"Generate Your HTTP Request Step: Directly paste it onto the desired anchor in the Designer (the same way you would paste a step), creating a Send an HTTP request Step based on the cURL command. This is customizable using the wand icon and Step Builder.
Create a Step from a nested Workflow
Save nested Workflows as custom Steps to allow other users to easily access, reuse, and benefit from their logic. For more information on nested Workflows, see here.
Select Your Nested Workflow: Drag the Workflow operator onto the Canvas within an existing Workflow. Select the Workflow you would like to save as a custom Step. Note that this must be a Workflow you can access within your workspace.
Customize Your Step: Click the wand icon to create a custom Step based on the selected Workflow and follow the Step Builder instructions.
Choose the main vendor (integration) for this nested Workflow. This will ensure the custom Step appears when you search for that vendor. You can also specify the name of a new vendor.
Create custom Steps with the Step Builder
This walkthrough of the Step Builder will guide you in creating your custom Step. Access the Step Builder by clicking the wand icon in the Step you want to customize or save as a custom Step.
Save your work in the Step Builder. If you close the wizard without saving, your work will be lost.
Enter the Step details
Name: Enter a meaningful name for the Step that reflects what it does.
Description: A brief explanation of the Step that expands on the name.
Documentation URL: A link to the vendor's API documentation (if available).
Vendor: The vendor for this Step. If the vendor doesn't exist, type the new name and click Create <vendor name>.
Integration: The integration instance to use by default for this Step.
Build the HTTP request
In this section, you create the underlying API for the Step. Scroll through the HTTP Request options to access the optional parameters.
URL: The base URL for the API call.
Method: The API method (GET, POST, PATCH, DELETE, etc.).
Authorization: The authorization method for the API call (for example, None, Basic (u/p), and Bearer).
Headers: One or more key-value pairs.
HTTP optional parameters: An expandable list of optional parameters to add to the Step. Click Add alongside the parameter you need and define the field.
You can set any value from the HTTP request as a parameter. When configuring this Step, users will see required parameters as fields in the main configuration window, and optional parameters will be accessible by clicking the cogwheel icon.
Create new parameters
You can create a new parameter from the marked segments in the URL. Highlight the relevant parameter segment and click Set as parameter.
The parameter will be added to the left-hand menu for you to define. The Step preview will show the input field for this parameter.
Assign a value to existing parameters
To define a parameter you have added to your Step, select it from the list on the left-hand side menu.
Types of parameters
Define your parameter by selecting one of the two primary parameter types: data parameters and integration value parameters.
Data parameter: Toggle to Create a parameter.
This parameter will receive input from the end-user using the Step. Edit the name for the Step's input field, select the correct type, description, placeholder, and if this is a required field.
Integration value parameter: Toggle to Use an integration value.
Select the value from the dropdown menu. If the Step was configured with an Integration (under the Step details section), the user can select a parametrized value that will receive its content from the integration. This will usually be for the URL's account domain identifier or authorization-related values. You can also create custom integrations.
Parameter conditions
This is a regular data parameter for instances where the end-user should fill it out only under certain conditions, such as if another parameter has a specific value or is filled in. Unselect the 'Required' checkbox to apply conditions to parameters and add a condition according to the appropriate requirements.
Remove values from parameters
To remove a value from being a parameter option (but not delete the parameter), go to the HTTP section, click on the parameterized value, and click Remove parameter.
If the parameter doesn't have any value, a notification will appear, reminding you to assign a value or delete it.
Delete parameters
To delete a parameter, go to the parameter configuration and click Delete in the top right corner. When deleting a parameter, each associated value will become unparameterized, and the input field presented in the Step preview will be removed.