📄️ Overview
Every flow starts with a trigger — the event that tells AutoFlow, “It’s go time.” Whether a record changes inside BC or an external service pings your environment, the trigger is the entry point that spins up the flow and hands over the first set of values to work with.
📄️ Global Insert
Use the Global Insert trigger whenever you want a flow to start the moment a new record lands in Business Central. It listens at the database level, so any insert that matches your configuration will spin up the flow, whether the record was created through the Business Central UI, an API call, or a background process.
📄️ Global Modify
Use the Global Modify trigger to start a flow whenever a record changes in Business Central. Like Global Insert, it listens at the database level, so updates from the UI, an API call, or a background job all wake up the flow. Optionally pick a set of watch fields so the flow fires only when one of those specific fields changes — the rest of the record can move freely without spinning up the flow.
📄️ Global Delete
Use the Global Delete trigger to start a flow whenever a record is deleted from a Business Central table. Unlike the Modify and Insert triggers, the deleted record is gone by the time the flow runs, so the trigger lets the author choose specific fields to capture as outputs before the row disappears.
📄️ Webhook
Use the Webhook trigger when you want a flow to start in response to an HTTP call from outside Business Central – a third-party callback, a custom integration, a Slack bot, anything that can POST JSON. The flow can run fully asynchronously (the caller gets an immediate empty 200) or synchronously up to a Respond to Webhook step (the caller waits for your flow's response).
📄️ Manual
Use the Manual trigger when you want a flow that only runs on demand. It exposes no Business Central event hook and no schedule — the only way to start a flow with this trigger is the Run this flow action on the Flow card.
📄️ SubFlow
Use the SubFlow trigger when you want a flow that other flows can call as a step — like a function. SubFlows are reusable building blocks: you define common logic once (e.g. "normalize customer number", "validate address", "send compliance notification") and any other flow can invoke it inline with typed inputs and outputs.
📄️ Scheduled
Use the Scheduled trigger to run a flow on a recurring cadence. There is no event source — the trigger is wired to a Job Queue Entry that AutoFlow creates when the flow is published, and every Job Queue run starts a fresh execution.
📄️ PDF Print
Available from the first paid AutoFlow plan onward.