Skip to main content
All CollectionsBuild AutomationsTriggers
Trigger Workflow Executions with Uploaded Files
Trigger Workflow Executions with Uploaded Files

Learn how to trigger workflow executions using uploaded files as inputs.

Updated this week

When using an on-demand trigger, you can add a file input parameter to allow users to upload files for the workflow. These files are only accessible within Torq steps through a non-shareable link provided in the trigger event.

You can also use Torq Interact to allow users to upload and download as many files as desired. Torq Interact can be used as a workflow trigger or used at any time within a workflow to communicate with end users.

How to Use

  1. Create a new workflow or select an existing one with an On-Demand trigger.

  2. Click + to add a trigger input parameter.

  3. Specify the parameter as File type and determine if it's required.

  4. Add at least one step to your workflow and click Test Run at the top right corner of the screen.

  5. Upload a file when prompted by the workflow.

    Upload a file when triggering the workflow
  6. The file link is available in the trigger event. The link is non-shareable and can only be used in Torq steps.

    Use the file link in workflow steps
  7. Use the file in the workflow steps. The file link is available at:

    {{ $.event.<file parameter name> }}

    To get the file content, use:

    {{ file $.event.<file parameter name> }}

    The file inline function is required when accessing the file content since the link is non-shareable.

    Use the file content in workflow steps

Trigger Nested Workflows with Files

You can pass a file URL to a nested workflow that has a file type trigger parameter. The nested workflow can also return a file URL as an output.

Only non-shareable links that have the format tqfile://steps/XXXXXXXXX can be passed as trigger parameters.

Pass a file link to a nested workflow
Did this answer your question?