Every workflow in MergePoint starts with a trigger — the event that decides when and why the workflow runs. The trigger is always the first node on the canvas. You pick the trigger type in the Start node inspector.
| Trigger | What it does |
|---|---|
| Apps | Runs when something happens in a connected external app (Outlook, Gmail, OneDrive, SharePoint, Linear, Airtable, Typeform, Docusign, and more) |
| Chat message | Runs when a chat message is received in MergePoint Chat |
| Manual Trigger | Runs when a user starts it on demand, or when another workflow calls it |
| Schedule | Runs automatically on a recurring timer — hourly, daily, weekly, monthly, or a custom interval |
| Form | Runs when a linked MergePoint form is submitted |
| Webhook | Runs when an external system sends an HTTP request to a generated URL |
| Mergebase | Runs when a record in a MergePoint table is created, changed, or meets specified conditions |
| Evaluation | Runs a set of test cases against your workflow to evaluate AI responses |
Open any workflow and click the Start node. The inspector panel on the right shows the trigger picker. Select a trigger type — it expands in-place to show its specific configuration options.
Each trigger has its own configuration. See the individual trigger articles in this section for details.
A trigger becomes active when the workflow is published. Draft workflows do not process live trigger events.
For scheduled and webhook triggers, the schedule or URL is registered the moment you publish. For app triggers, the connected account must still be authorised at the time events arrive.
