Trigger Nodes

Trigger nodes are the entry points for workflows. Each workflow must have exactly one trigger node. While the designer allows multiple triggers to be placed, only a single trigger per workflow is supported — using more can cause inconsistent behaviour.

Purpose

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 start the automation.

• Entry point: Every workflow begins with a trigger — without one the workflow will never run.
• Event types: Triggers can be based on schedules, webhooks, manual actions, chat events, API calls, file changes, and more.
• Single trigger restriction: Each workflow should contain one and only one trigger node for predictable results.

Configuring a Trigger Node

The trigger configuration dialog is identical in layout to the task node configuration dialog:

• Header: Task name, description, and accounts
• Left pane: JSON viewer showing the last event payload, or root on first run
• Right pane: Configuration fields specific to the trigger type
• Footer: Cancel and OK / Update buttons

Depending on the trigger type, the dialog may require specific input fields, service accounts, or third-party accounts.

Node Controls

Each trigger node has three buttons above it:

• Play: Simulates the trigger firing. For webhook-based triggers this opens a dialog to provide a test payload; for manual triggers it fires immediately.
• Edit: Reopens the configuration dialog.
• Delete: Removes the trigger and its configuration from the workflow.

The clone button is not available for trigger nodes.

Connecting a Trigger Node

Triggers have a single output connection point. Click and drag from the output dot to the input dot of the first task node to connect them. Flow always runs from trigger to task node.

Available Triggers

Autodesk Construction Cloud

Webhook note: ACC webhook triggers are active for 60 days unless manually deleted. Click Create Webhook in the configuration dialog to register the webhook (a green tick confirms success). To remove it, open the workflow and click Delete on the trigger node.

Trigger	Description
ACC File Created	Fires when a new version of a file is created in ACC.
ACC Folder Created	Fires when a new folder is created in ACC.

Autodesk Vault

Trigger	Description
Vault Job Queue	Fires when a job is added to the Vault job queue.

General

Trigger	Description
Manual	Starts the workflow manually from the designer. Useful for testing and debugging.
Run Now	Exposes the workflow via the chat interface for on-demand execution.
Scheduled	Fires on a user-defined cron schedule.
Fail	Entry point for a failure-handling sub-workflow. Receives context about the failed task.
Sub Task	Entry point for a sub-workflow called from a parent workflow.

MinuteView API

Trigger	Description
GET	Exposes an HTTP GET endpoint that starts the workflow.
POST	Exposes an HTTP POST endpoint that starts the workflow.
POST File	Exposes an HTTP POST endpoint that accepts a file upload alongside form data.

Mesh

Trigger	Description
Mesh Search	Fires when a user submits a search query in Mesh.
BIM Orchestrator	Fires when a chat message is sent to a BIM model in Mesh.

MinuteView Capture

Trigger	Description
Capture Submit	Fires when a Capture review form is submitted.

Configurator

Trigger	Description
Completion	Entry point for a workflow that runs when a Configurator session completes.
Initial Value	Fires when a Configurator control needs its initial value calculated.
Iteration	Fires on each iteration step within a Configurator calculation.
Report	Entry point for a workflow that generates a Configurator report.
Validate Control	Fires when a Configurator control value needs validation.