Use Torq Interact to send and create secure and interactive web pages and web forms that collect data, log answers, provide information, and propel workflows forward according to the responses received. Allow multiple SOC analysts to make parallel decisions quickly, improving response times, enriching attack reports with the end-user's experience, and more. Interact can also be used within cases as tasks.
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 cases task. Each Interaction flow represents an end-user journey of communication with Torq.
Preview the Interaction in the configuration panel.
Interaction Basics
Drag and drop elements into the Interaction configuration area to build your ideal Interaction content. Rearrange elements by dragging them into alternative orders. Each Interaction can contain as many elements as needed.
Each element can be copied or deleted by using the icons on the right-hand side of the element. To select multiple elements at once, hold down the Shift button. From there, Cmd+C will copy, Cmd+V will paste, and Cmd+D will delete. The exception is the Headline element, which cannot be deleted or replicated. Elements can be copied and pasted across workflows and workspaces.
Each element has a unique Context reference, allowing easy access from other steps within the workflow. The default context reference is based upon the Text and will auto-change whenever the related text does. The context reference is editable as desired and cannot be empty.
Each element allows for a Description, where you can write clarifying information for the user. The description can remain empty if you wish.
Each element requires a Default value, the initial value that an input will contain, provided before the user makes any changes. If the user makes no changes, this value will be returned to Torq.
You can change the element type from the Type dropdown menu. When the type is changed, the description, text, and context reference remain the same, but any created unique values will not be saved.
Two types of elements are available within a Torq Interact form:
Display Elements -
Markdown allows for the presentation of text or any other markdown-generated content (images, links, etc.) to the user.
Button presents a button that will navigate the user to the next Interaction Flow in the series. Customize the text on the button as you wish. Removing the button is only possible on the final Interaction Flow of the series and will end the flow.
Add a secondary button to allow the user to move forward within the Interaction Flow even if they have not filled in all the required fields.
File Download allows you to upload a file (directly or via workflow context) for the end user to download.
User input elements allow the user to input data via a form. Input elements can be marked as required or unrequired.
Short text requests the user write a short answer.
Long text requests the user to write a long answer.
JSON requests that the user insert a JSON.
File requests the user upload a file or multiple files.
The size limit for a user-uploaded file in an Interaction Flow/Cases Task is 50MB.
Number requests the user return a number.
Boolean requests the user toggle a true or false button.
Single select requests the user select one option from a curated menu.
Multi-select requests the user to select multiple options from a curated menu.
Date and Time requests the user select a date and time from a calendar picker. When building the Interaction Flow, you can request the user select either a date and time or just a date.
To change the Interaction Flow settings, click on the top right corner Interaction Flow settings button on any Interaction Flow operator or from the topbar over each step. From there, you can:
Control the user access for the specific Interaction Flow to only Torq users or users who can log in with your organization's SSO. To use SSO, ensure SSO IdP is enabled from within workspace settings. Add users to the Torq group within your SSO app (ex: JumpCloud, Okta, etc.) and not within the Torq app
Rename the Interaction Flow.
Reassign the Interaction to a different Interaction Flow.
You can change the logo on the web page by going to Settings > General in your workspace.
Condition Elements in Interact
Under Control Elements, you can find the Condition element. The condition element allows you to create complex logic directly in your Interaction by dynamically presenting display and user input elements based on live responses.
The condition element utilizes And/Or logic with Equals/Not Equals and Filled conditions to flexibly build your interactions dynamically present questions and information based on answers to previously existing elements.
And/Or Logic: Utilize And to require all conditions to be met before presenting the follow-up questions or Or for allowing any of the conditions to be met in order to present the follow-up.
Drag the condition element into an Interaction with at least one user input element.
Place the condition element below the existing user input element.
Set your condition based on an existing user input element. Within one condition section, you can set multiple And/Or conditions.
Condition elements cannot reference user inputs or elements created beneath themselves.
However, a secondary condition can be created beneath (not within) the first condition element and reference user-input elements from within the first condition.
After setting your condition, drag and drop either display or user input elements within it. If the condition is met, the elements contained within the condition will be shown to the end-user.
Condition Element: Example
Condition Element: Example
In the following example, a form asking which location was affected by an outage is sent to a user.
After creating an Interaction-triggered workflow, drag and drop a Single-Select element with the question and three options: US, EU, CA. This question will be presented to every user who receives the Interaction.
Drag and drop a Condition element beneath the first single-select.
Give the condition a unique and meaningful name.
Select an element from the drop-down menu.
As there is only one other element in our interaction currently, only the single-select will be available.
Select the Equals option for the condition, and in the Value field, enter US.
Now drag a Boolean element underneath the Related elements line. This will ensure the Boolean is only shown to those who selected the US.
It is important to note that any elements added outside of a condition element will be shown to all end users, regardless of meeting any created conditions.
After setting multiple elements under the Related elements line, this is what the form will look like for the end user:
When to use Conditions and when to use If?
The Condition Element should be used when the elements shown on condition directly relate to the user-input elements in that same Interaction, or when the Interaction Flow does not require multiple Interactions or Operators.
Interaction Flows built using multiple Interactions and If/Switch/ other Operators should be used when:
The content is affected by other Interaction Flows or other steps from within the workflow.
You wish to keep each Interaction as short as possible.
Starting a Workflow with the Interact Trigger
Create a new workflow and select the Torq Interact Trigger.
Once the workflow is created, open the Interact trigger and drag and drop your desired elements.
Add another Interaction to the Interaction Flow from the operators’ menu and select to assign it to the existing interaction flow. The new Interaction will follow the previous trigger on the webpage or task created. You can also add a new Interaction to the specific Interaction Flow with the button that appears upon clicking the step or the trigger.
When starting an Interaction with a trigger, you can view the email of the user who submitted the Interact form by accessing {{ $.metadata.user_email }} within the workflow.
Display Only Interaction
To send an Interaction that will not request user submission, use the Markdown element alone, without any input or button elements. Inside an Interaction Flow, only the final Interaction can be display only.
Starting an Interaction Flow Inside a Workflow
A new Interaction Flow can start at any point within a workflow. When an Interaction Flow does not originate from a trigger, you can select whether the Flow will display as a webpage or a Cases Task.
Drag the Interaction operator from the operator’s panel to the proper location on the canvas.
Give the Interaction Flow a relevant name.
In Interaction Flow settings, select if this Interaction Flow is a case task or a web page and change the access as needed.
Click Save to retain changes.
Every Interaction Flow that begins in the middle of a workflow and is not meant for a case has a URL that can be sent to the end user by a chatbot or email.
Changing the Interaction’s Assignment to a Different Interaction Flow
Switch which Interaction Flow an Interaction belongs to by clicking on the operator in the workflow and then Interaction Flow > Change. From there, you can select either New Interaction Flow to create a new flow that begins with that Interaction or Existing Interaction Flow to add that Interaction to an already existing Interaction Flow within the workflow. This can also be done from within the Interaction Flow's settings.
Link to the Interaction Flow
To access an Interaction Flow's URL within another step, type $ to access autocomplete > interaction_flows_url and select the relevant Interaction Flow. ex: {{ $.interaction_flows_url.'My Interaction Flow' }}
Parallel Interaction Flows
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 during its execution. Since an Interaction Flow executed in a parallel loop creates multiple URLs for the same Interactions, which will be sent to multiple users or cases, all Interactions related to the Interaction Flow must be contained within the loop.