Triggers
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.
Why triggers matter
- Kick off execution instantly: Triggers listen for specific events, then launch the flow as soon as they occur.
- Deliver context to steps: The trigger supplies initial data (like the record, user, or payload) so downstream actions know what to work on.
- Keep automations aligned: By choosing the right trigger, you make sure flows run when they should — and only when they should.
When a trigger runs
- The subscribed event happens in Business Central or via an external call.
- AutoFlow starts a new execution with the trigger payload.
- The flow continues through each step, using the trigger output.
Common trigger sources
- Business Central events: Table insert/modify/delete, page actions, or system events raised by core apps and custom extensions.
- Workflow editor actions: Manual runs that let designers test or demo a flow directly from the graphical interface.
- External systems: HTTPS or webhook calls that integrate partner apps, portals, or middleware with AutoFlow.
Where to configure triggers
Head to the flow editor and create a new blank flow to open the Trigger list. From there you can:
- Select a predefined Business Central event, and add additional record filters.
- Choose one of the built-in special events, like manual or scheduled execution.
- Pick a custom event provided by another extension.
Best practices
- Stay specific: Narrow record filters and event scopes to avoid unnecessary executions.
- Validate inputs early: Use initial decision steps to guard against missing or malformed trigger data.
- Document intent: Add trigger descriptions so teammates know exactly what causes the flow to fire.
Ready for the next step?
Explore the rest of the Triggers section to dive into every trigger AutoFlow ships with, complete with payload details, configuration tips, and usage examples — so you can pick the right starting point for each automation.