Skip to main content
All CollectionsBuild AutomationsTriggers
On-Demand Triggers in Torq: Enable User-Initiated Executions
On-Demand Triggers in Torq: Enable User-Initiated Executions

Set up and customize on-demand triggers in Torq workflows, allowing manual initiation from anywhere, anytime.

Updated over a month ago

On-demand triggers in Torq allow users to manually start workflows at any time, from the designer, through platforms like Slack, via web forms, or within other workflows. Customize these triggers with parameters to tailor the start event.

Setting Up an On-Demand Trigger

  1. Create or Modify a Workflow: Choose the on-demand trigger when making a new workflow or change an existing trigger by clicking the replace icon.

  2. Configure Trigger Parameters: Customize the trigger with parameters that appear as a form upon execution. Details include:

    • Type: Set the data type (e.g., text, JSON, number). The default is text.

    • Name & Description: Name your parameter and optionally describe it.

    • Defaults & Requirements: Set default values and mark parameters as required or optional.

Upload files to be accessed during workflow execution. The file link generated is secure and private, accessible within Torq using {{file $.event.<parameter_name>}}.

Running and Testing Your Workflow

  • Test Run: After adding steps, click Test Run to manually initiate the workflow.

  • From Other Platforms: Start the workflow from platforms like Slack by providing values for the trigger parameters.

  • Using Trigger Data: Incorporate event data in workflow steps with $.event.<parameter_name>.

Enabling Web Form Triggers

  • Publish and Share: Publish your workflow and select Trigger As Web Form to share a URL that allows external users to initiate the workflow.

  • Embedding: Place the link in service tickets, messages, or websites for easy access.

  • User Input: External triggers require users to input values for required parameters.

Resending Trigger Events

Use the Event Log tab to resend trigger events, allowing modification of parameter values for each resend.

Did this answer your question?