Docs
Search K

Appearance

Trigger Nodes ​

Trigger Nodes are the entry points for workflows. Each workflow must have exactly one Trigger Node. While you can insert multiple triggers, only a single trigger per workflow is supported—using more can cause inconsistent behavior.

What is a Trigger Node and What is it Used For? ​

A Trigger Node defines how and when your workflow starts. Unlike Task Nodes (which perform actions), Trigger Nodes listen for external or user-driven events and kick off the automation.

  • Entry Point: Every workflow begins with a trigger—without it, the workflow will never run.
  • Event Types: Triggers can be based on webhooks, schedules, manual actions, chat events, file system changes, and more.
  • Single Trigger Restriction: For predictable results, each workflow should contain one—and only one—Trigger Node.

Configuring a Trigger Node ​

The Trigger Configuration dialog is identical in layout to the Task Node Configuration dialog:

  • Header: Task Name, Description & Accounts (same fields and behavior)
  • Left Pane: JSON Viewer (shows last event payload or root on first run)
  • Right Pane: Configuration Fields (form-based input types)
  • Footer: Cancel and OK/Update buttons

Note: Depending on the trigger type, the dialog may require specific input fields, service accounts, or third-party accounts—just like Task Nodes.

Node Tools for Trigger Nodes ​

Above each Trigger Node, you’ll find three buttons:

  • Play: Simulates the trigger firing (e.g., opens a dialog to specify a file for webhooks or immediately fires a manual trigger).
  • Edit: Reopens the Trigger Configuration dialog for modifications.
  • Delete: Removes the trigger and its configuration from the workflow.

The Clone button is not available for Trigger Nodes.

Connecting a Trigger Node ​

  • Output Dot: Triggers have a single output connection point.
  • Connecting: Click and drag from the trigger’s output dot to the input dot of the first Task Node.
  • Directionality: Flows from Trigger → Task Node.

Available Trigger Types ​

Autodesk Construction Cloud (ACC) ​

ACC Webhook Trigger ​

  • Webhook Creation: Add an ACC Trigger to your workflow; fill in the configuration form and click Create Webhook (success = green tick).
  • Webhook Lifetime: Active for 60 days unless manually deleted.
  • Webhook Deletion: Open the workflow and click the Delete button.

alt text

File Version Created Webhook ​

Fires when a new version of a file is created in ACC. Use Case: Automatically process or notify stakeholders upon file updates.

Folder Created Webhook ​

Fires when a new folder is created in ACC. Use Case: Trigger automated provisioning or record-keeping on project structure changes.

Autodesk Vault ​

Job Queue Trigger ​

Fires when a job is added to an Autodesk Vault job queue. Use Case: Kick off downstream processing when Vault tasks complete.

General Triggers ​

Manual Trigger ​

A manual start trigger available only in the designer UI. Use Case: Ad-hoc execution during testing or debugging.

Run Now ​

An interactive trigger exposed via the chat interface. Use Case: Let users run the workflow on demand without leaving chat.

Scheduled Trigger ​

Fires on a user-defined schedule (cron-style). Use Case: Automate recurring processes like daily reports or maintenance tasks.

Mesh Platform ​

Record Action ​

Fires when a specific action is recorded in Mesh. Use Case: Start workflows based on user interactions or events in Mesh.

Mesh Chat ​

Fires on a predefined chat event in Mesh. Use Case: Integrate conversational triggers into automation.

Chat with Model ​

Fires when a chat model request is received. Use Case: Start AI-driven workflows upon user prompts.

Widget Trigger ​

Fires when a Mesh widget emits an event (e.g., button click). Use Case: Connect UI interactions to backend processes.

API Webhooks ​

GET Endpoint ​

An HTTP GET endpoint that triggers the workflow. Use Case: External systems start workflows via query parameters.

POST Multipart ​

An HTTP POST endpoint accepting multipart form data. Use Case: Trigger workflows with file uploads or mixed content.

POST Endpoint ​

An HTTP POST endpoint for JSON or form-encoded payloads. Use Case: Start workflows via standard API calls with structured data.

MinuteView ​

Capture Submit ​

Fires when a MinuteView form is submitted. Use Case: Process user submissions or form-based inputs through automation.

Tentech 2024