What's New?

With our new Loop experience, building Loops is more intuitive than ever! Within the new Loop UI, you can easily switch between types and modes, add next-step operators, and conveniently rename Loop values and keys.

We’ve introduced new integrations for Sweet Security, Toast, and Veeam and new steps for existing integrations like CrowdStrike, VictorOps, and Microsoft Outlook. For full details, check out the complete digest.

​

​

We’ve introduced the Resume Execution step, which provides you with precise control over workflows involving the Wait operator.
​

Use the Resume Execution step to signal a Wait operator to stop waiting and continue the workflow for a given execution. This allows workflows to resume automatically based on defined conditions, such as completing an approval process or gathering enough threat intelligence for further action.

We’ve added a Custom Fields Operator parameter in the Query Cases step, providing greater control over case filtering. Select AND or OR to refine your queries, with OR set as the default for maximum flexibility.

We’ve added a Loading Screen operator to Torq Interactions, allowing you to display customized messages to keep end-users informed about Interaction Flow progress.

Add a Loading Screen between Interactions and use markdown to personalize messages with text, images, or GIFs, making the waiting experience more dynamic and user-friendly.

We’ve introduced the ability to continue Interaction Flows within nested workflows, making parent workflows more organized and easier to manage.

Simply add an Interaction Flow parameter to the On-Demand trigger of the nested workflow, pass the Interaction Flow from the parent workflow, and assign any nested interactions to it. This ensures a seamless end-user experience while keeping your workflows efficient and organized.

Torq’s custom steps offer unparalleled flexibility to meet your organization’s unique needs. Now, you can share a workflow with custom steps or custom integrations, and they’ll automatically be included and available in the destination workspace.

When exporting a workflow, its description and tags are now included, ensuring they remain intact when imported into another workspace.

This enhancement enables seamless transfer of additional workflow details across workspaces, preserving essential information such as categorization and context during exports and imports.

Establish a case review process to ensure quality, compliance, and adherence to investigation protocols before taking further actions such as resolution, escalation, or stakeholder updates.

• Assign reviewers to assess case investigations and approve or reject them.
• Conduct the review process through the Cases page or automate it with the provided steps and Torq Cases trigger scenarios.

To get started, enable the Case review setting on the Cases settings page.
Once a reviewer is assigned, their icon appears next to the case assignee's icon. When a review conclusion is provided, the verdict replaces the reviewer’s icon, ensuring clarity and immediate visibility.

Automatically manage workflow publishing and unpublishing using the new System Events trigger scenarios:

• Workflow published
• Workflow unpublished

For example, you can automate notifications to stakeholders to ensure compliance, prevent errors, and enhance collaboration.

More information is available in our knowledge base.

We've introduced new integrations for Clutch Security, CrowdStrike Identity Protection, and NetBox, along with new steps for existing integrations. For full details, check out the complete digest.

You can now create table workspace variables by specifying the table columns in JSON format. This approach enables dynamic table schema definition, either by retrieving it from existing tables or a centralized source such as a workspace variable.
For example, this option is helpful for replicating tables across workspaces.

Use the Create a Workspace Variable step, switch to JSON mode, and specify the table schema using one of these methods:

1. From Workflow Context: Define the table schema using the workflow context, such as the output from a previous Get a Workspace Variable step that was used to retrieve the schema of an existing table.
2. Custom JSON Format: Manually specify the table schema in JSON format.

More information is available in the knowledge base.

When importing a workflow with nested workflows into your workspace, conflicts may arise if workflows with identical names already exist. You can now choose Override original alongside other conflict resolution methods:

• Keep original: Retain the existing workflows as they are. The imported workflow is added as a duplicate, referencing existing nested workflows.
• Override original: Replace the existing workflows with the imported versions.
• Duplicate: Create duplicates of any nested workflows and update the imported parent workflow to reference the duplicates.

Automate imports using the Import a workflow step, which defaults to Keep original for conflict handling. Add the Conflict handling mode optional step parameter to select Override original or Duplicate.

For more details, refer to our Knowledge Base.

Gain real-time visibility of users actively viewing a case, available in both the case quick and expanded views. When incidents require teamwork, knowing who is actively engaged with a case enhances coordination and reduces duplicated efforts. Real-time visibility of case viewers fosters better collaboration, ensures timely communication, and leads to faster, more efficient case resolutions.

We've introduced new integrations for Autotask, Jamf Protect, SecurityScorecard, and Wazuh, along with new steps for existing integrations, various enhancements, and new templates. For full details, check out the complete digest.

We've introduced new integrations for Cyera, FIRST, and SSLLabs, along with new steps for existing integrations, various enhancements, and new templates. For full details, check out the complete digest.

Want even more streamlined automation? Use Torq's new Deduplicate Operator! Effortlessly handle burst events, recurring reports, repeated indicators, and more without clogging up your workflows.

The Deduplicate Operator automatically identifies and processes duplicate entries across workflow executions, based on your specified criteria and time range. The operator helps avoid repetitive input, allowing you to consolidate repeated trigger events, prevent duplicate case creation, streamline records, and more!

Say goodbye to data clutter and hello to a cleaner, more powerful automation experience with Torq!

Case management settings are now centralized in the Settings > Cases page, simplifying customization to align with your organization’s specific needs.

We’ve introduced three new settings:

• Categories: Manage categories for accurate case classification.
• Resolution Reasons: Manage the reasons analysts can specify when resolving or closing cases.
• States: Create custom states and edit the default ones for accurate tracking.

More details can be found in our knowledge base.

Introducing the Data Transformation Operator! Processing large amounts of data to create consistent and navigable output can be overwhelming, so Torq's Data Transformation Operator is here to help! Give instructions in natural language to generate JQ code on any JSON input.

Data Transformation supports mapping and extraction, converting data types, math functions, and more! As with all Torq operators, its use is intuitive for builders of all levels - coders and non-coders alike.

So what are you waiting for? Go transform your data - and your automations - now!
​
If you do not see the new Data Transformation operator, it may be because your organization opted out of Torq AI features. Please contact Torq support if you have not opted out and still do not see the feature.

We've added a Generate with AI input field for CLI, scripting, and data manipulation steps.

Simply enter a natural language description of the desired action (e.g., AWS list running workspaces) and let AI fill in the relevant step input fields.

For more details and a complete list of supported steps, visit our knowledge base.