Trigger Nodes

Trigger nodes are the entry points for workflows. Each workflow must have exactly one trigger node. Trigger nodes determine how and when the workflow starts.

Autodesk Construction Cloud

Webhook Creation: Simply add an ACC Trigger to your workflow to begin the automation. To Configure the Webhook enter all the required information in the Task Confirguration form and click create Webhook button. Success will be indicated with a Green Tick.

You must be signed into Autodesk in order to create a webhook

The hook will remain live for 60 days unless deleted before.

Webhook Deletion: Open the workflow and click the delete button to delete the Webhook

File Version Created Webhook

Fires when a new version of a file is created in Autodesk Construction Cloud.

Use Case: Automatically process or notify stakeholders upon file updates.

Folder Created Webhook

Fires when a new folder is created in Autodesk Construction Cloud.

Use Case: Trigger automated provisioning or record-keeping when project structure changes.

Autodesk Vault

Job Queue

Fires when a job is added to an Autodesk Vault job queue.

Use Case: Kick off downstream processing when Vault tasks complete.

General

Manual Trigger

A manual start trigger available only within the workflow designer UI.

Use Case: Ad-hoc execution during testing or debugging.

Run Now

An interactive trigger exposed via the workflow’s chat interface.

Use Case: Enable users to run the workflow on demand without leaving the chat.

Scheduled

Fires at a user-defined schedule (cron-style).

Use Case: Automate recurring processes (daily reports, maintenance tasks, etc.).

Mesh

Record Action

Fires when a specific action is recorded in the Mesh platform.

Use Case: Initiate workflows based on user interactions or events in Mesh.

Mesh Chat

Fires when a predefined chat event occurs 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

Fires when a Mesh widget emits an event (e.g., button click).

Use Case: Connect UI interactions to backend processes.

API Webhook

GET

An HTTP GET endpoint that triggers the workflow.

Use Case: External systems can start workflows by sending query-parameter-based requests.

POST Multipart

An HTTP POST endpoint accepting multipart form data.

Use Case: Trigger workflows with file uploads or mixed content submissions.

POST

An HTTP POST endpoint for JSON or form-encoded payloads.

Use Case: Start workflows via standard API calls carrying structured data.

MinuteView

Capture Submit

Fires when a MinuteView form is submitted.

Use Case: Process user submissions or form-based inputs through automation.