Use Torq Interact to send and create secure and interactive web pages and web forms that collect data, log answers, provide information, upload or download files, and propel workflows forward according to the responses received.
Torq Interact allows multiple SOC analysts to make parallel decisions quickly, improving response times, enriching attack reports with the end-user's experience, and more. Interact is used within cases as a task.
Interaction - an operator or a trigger in a workflow representing a single web page/web form/task configuration, and the linear time (compared to other steps) will be available during the workflow execution.
Interaction Flow - a series of Interactions accessible from the same web page or case task. Each Interaction flow represents an end-user journey of communication with Torq.
You can preview the Interaction in the configuration panel.
By design, a workflow will not move on to the next steps while an Interaction is still waiting for responses and has not yet timed out. If you have steps that you would like executed while the workflow waits for responses, create a parallel execution to run them at the same time as the Interaction flow.
Interact Only role
The Interact Only role provides limited access for users who only need to engage with Torq Interact without accessing other parts of the Torq platform.
Access scope
Users with the Interact Only role have limited access, allowing them to engage exclusively with Interact workflows within the workspaces where they are designated as Interact Only users. They can access any Interact URL associated with those workspaces, whether the workflows are delivered through the Torq app sidebar or via a permanent webpage URL, as long as the Interaction Flow’s access configuration grants them permission. All Interactions they’re permitted to use are centralized in one place, making it easy to find and act on the relevant Interaction Flows without navigating the broader platform. For a full description of the Interact-only role, its permissions, and visible UI pages, see the Torq Roles and Scopes: Managing Access and Permissions article.
The page below illustrates a typical landing view for users with the Interact Only role. It presents a centralized Interactions list containing only the flows relevant to them, those that are available to run, and those currently awaiting their input (pending).
Interaction basics
Add elements to the Interaction: Drag and drop elements into the Interaction canvas to build your content. Rearrange them by dragging into a new order. An Interaction can include as many elements as needed.
Manage elements:
Use the icons on the right side of each element to copy or delete it.
Hold Shift to select multiple elements.
Use Cmd+C to copy, Cmd+V to paste, and Cmd+D to delete.
The Title element cannot be deleted or duplicated.
Elements can be copied and pasted across workflows and workspaces.
Use context references: Each element has a unique Context reference used later in the workflow.
The default reference is based on the element text and updates automatically if the text changes.
You can edit the reference name, but it cannot be empty.
(Optional) Add a description: Provide helper text to clarify the input for users. This field may remain empty.
Set a default value: Some of the input elements require a Default value.
This is the initial value shown to the user.
If the user makes no changes, this value is returned to Torq.
(Optional) Change the element type: Use the Type dropdown to switch the element type. The text, description, and context reference remain the same, but any unique configuration values will reset.
Element types
Torq Interact supports three main categories of elements, as detailed below.
Control elements
Condition: Create dynamic logic inside the Interaction to display elements based on user responses.
Display elements
Markdown: Display formatted text, images, or links.
Button: Add a button to move the user to the next Interaction Flow.
You can customize the button text.
The button can only be removed on the final flow, which ends the Interaction.
Add a secondary button to allow users to proceed even if required fields are incomplete.
Link: Add links to published workflows or external URLs.
Paste an external URL into the Link to field if needed.
Can be used to create an interactive portal experience.
File Download: Upload a file (manually or via workflow context) for the user to download.
Table: Display a workspace variable table or JSON table. See the dedicated Table documentation for full details.
User input elements
User input elements collect structured data from users. Inputs can be marked as required or optional.
Short Text: Collect a brief response.
Long Text: Collect a detailed response.
Secret: Securely collect sensitive values (API keys, credentials, tokens).
Input is masked and never exposed in logs.
If the value must persist beyond the current execution, explicitly save it as a Torq Secret or Integration API key.
Supports secure one-time use, configuration, and rotation.
Secret configuration fields:
Text: Label displayed to the user.
Type: Automatically set to Secret.
Context reference name: Variable used later in the workflow.
(Optional) Description: Helper guidance for the user.
JSON: Request JSON input.
File: Upload one or multiple files (maximum size: 50MB per file).
Number: Request a numeric value.
Boolean: Toggle true or false.
Single Select: Choose one option from a list.
Multi-Select: Choose multiple options from a list.
Date and Time: Select a date and time (or date only) from a calendar picker.
Row Selection: Allow users to select one or more rows from a displayed table. For detailed configuration, see Row Selection and Editable Table in Torq Interact.
Selected rows are returned to the workflow context.
Ideal for approvals, triage, and targeted actions on specific records.
Editable Table: Allow users to modify editable fields in a table before submitting the Interaction. For detailed configuration, see Torq Interact: Row Selection and Editable Table.
Metadata fields (such as ID or timestamps) cannot be edited.
Changes are applied only after the Interaction is submitted.
The submitted payload includes the updated table and the number of modified rows.
Interaction Flow settings
To configure Interaction Flow settings:
Open Flow Settings: Click the Flow Settings button in the top-right corner of the Interaction Flow operator or from the top bar.
Rename the flow: Update the Interaction Flow name.
Reassign the flow: Move the Interaction to a different Interaction Flow.
Set timeout: Define how long the page remains accessible.
Default timeout: 24 hours.
Maximum timeout: 30 days.
Configure user access: Define who can access this Interaction Flow, specific users, roles, external SSO users, or everyone (workspace users and external SSO users). For detailed access configuration options and behavior, see Torq Interact: Access Control.
Configure branding: Customize the logo displayed on the Interaction page by navigating to Settings > General in your workspace and updating the workspace logo.
Display-only Interaction
A Display-only Interaction presents information without requiring user input or submission. For a complete example, see the guide on building a display-only portal using Torq Interact.
Use display elements only: Add elements such as Markdown, Link, or File Download.
Do not add input elements: Avoid adding user input elements (e.g., text fields, dropdowns).
Do not add buttons: Do not include navigation or submission buttons.
Place as the final Interaction: Only the final Interaction in an Interaction Flow can be display-only.
Understand timeout behavior: Display-only Interactions automatically have a 30-day timeout, overriding the default Interaction Flow timeout.
Link to the Interaction Flow
Open the workflow context: In the relevant step, type
$to access the workflow context.Select the Interaction Flow URL: Choose
interaction_flows_urland then select the relevant Interaction Flow.Use the generated reference: The reference will appear in the following format:
{{ $.interaction_flows_url.'My Interaction Flow' }}
Interaction Flows in Loops
Regular loops
For each Interaction Flow execution, if there are no additional Interact steps following it on the canvas, the flow treats that Interaction as its final step. Therefore, when using a regular loop that contains an Interaction Flow, the flow must continue after the loop, ending with either a submission Interaction (an Interaction that includes a button) or a display Interaction showing a confirmation or “Thank you” message.
Parallel loops
Two Interactions from the same Interaction Flow cannot be run in parallel.
A parallel loop generates a dedicated Interaction Flow URL for each loop iteration. Since an Interaction Flow executed in a parallel loop creates multiple URLs for the same interactions, each sent to different users or cases, all interactions related to the Interaction Flow must be contained within the same single loop.
Continuing Interaction Flows in nested workflows
Continue your Interaction Flows within a nested workflow to keep parent workflows organized and simple.
Add an On-Demand trigger: In the nested workflow, add an On-Demand trigger.
Add an Interaction Flow parameter: Click the trigger, select + Add parameter.
Select parameter type: Choose Interaction flow as the parameter type, give it a name (e.g., Interaction Flow Continued), and click Save.
Pass the Interaction Flow from the parent workflow: In the parent workflow, pass the existing Interaction Flow as a parameter to the nested workflow.
Assign Interactions to the passed flow: Inside the nested workflow, assign each Interaction to the Interaction Flow defined in the trigger parameter to maintain continuity.
Continue the flow in the parent workflow: After the nested workflow completes, continue the Interaction Flow in the parent workflow with at least one additional Interaction before ending the flow.
Interaction Flows cannot end inside nested workflows.