FLOWS TRIGGERS · EVENT-DRIVEN
Automation that fires
when it matters.
A workflow is only as good as what starts it. Maxx Stacks Flows supports eight trigger types — from webhooks and schedules to AI agent outputs and intelligence threshold breaches — so your automation fires on exactly the right event, every time.
TRIGGER CONFIGURATION — WEBHOOK
TRIGGER TYPE
Webhook (POST)
AUTHENTICATION
Bearer Token
CONDITION GATE
payload.status == "confirmed"
RETRY POLICY
3× · exponential backoff · 30s
TRIGGER ACTIVE
ALL TRIGGER TYPES
Trigger Library
Every event that can
start a flow.
Trigger Type
Description
Status
Webhook
Fires on inbound HTTP POST. Configurable authentication, payload schema validation, and immediate or queued execution.
live
Schedule
Cron-based or interval-based. Fires at fixed times, recurring intervals, or one-time dates. Timezone-aware.
live
Data Event
Fires when a record is created, updated, or deleted in a connected data source. Supports field-level filters.
live
API Call
Fires when an external system calls the Flows API endpoint. Pass arbitrary payload data and receive a response.
live
Agent Output
Fires when a Maxx Stacks AI agent completes a task and emits a trigger signal. Closes the loop between intelligence and action.
live
Threshold Breach
Fires when a monitored metric crosses a defined boundary. Integrates with MSIL monitoring for intelligence-aware triggering.
live
Manual Trigger
Fires on demand from the Flows dashboard, API, or portal. Useful for testing and on-demand automation.
live
Email Event
Fires when a specified email condition is met: received, opened, clicked, or bounced. Connector-based.
beta
TRIGGER CONFIGURATION
Core Trigger Types
Configure any trigger
in minutes.
Each trigger type has a dedicated configuration panel in the Flows Builder. Set conditions, authentication, retry policies, and chaining rules — all without writing code.
Webhook Trigger
Configure the endpoint URL, authentication method (Bearer, API key, HMAC signature), and expected payload schema. Validate incoming data before the flow begins.
Schedule Trigger
Define cron expressions or choose from interval presets (every minute, hourly, daily, weekly). All schedules are timezone-aware and observable from the monitoring dashboard.
Data Event Trigger
Connect to any data source in your Flows connector library. Select the record type, choose create/update/delete events, and add field-level filters to target only the records that matter.
Threshold Trigger
Monitor any numeric field or computed metric. Set upper and lower boundaries. When the value crosses the boundary, the trigger fires — with hysteresis support to prevent rapid re-firing.
Advanced Features
Trigger Chaining
Define sequential trigger conditions. Flow A's output can be the trigger for Flow B, creating end-to-end automation pipelines across your entire operation.
Conditional Logic
Add condition gates to any trigger. Field-level expressions determine whether the trigger should pass or be suppressed — keeping your flows targeted and your execution logs clean.
Retry Policies
Every trigger type supports configurable retry logic: number of attempts, delay strategy (fixed, exponential, linear), and fallback behavior on final failure.
Dead Letter Queue
Failed trigger events that exhaust retries are sent to the dead letter queue. Inspect, replay, or discard from the monitoring dashboard without losing data.
Trigger Chaining
One event becomes
a cascade.
Trigger chaining lets you link flows so that the completion of one automatically initiates the next. Build multi-stage automation pipelines that span systems and teams.
TRIGGER
Data Event
FLOW 1
Validation & Enrichment
TRIGGER
Agent Output
FLOW 2
Decision & Route
TRIGGER
Threshold Breach
FLOW 3
Alert & Escalate
FAQ
Common questions about Flows Triggers
A trigger is the event or condition that starts a flow. Triggers can be scheduled (time-based), reactive (webhook or API call), data-driven (a field change, threshold breach, or record event), or intelligence-driven (an AI agent output or MSIL signal).
Yes. Trigger chaining lets you define sequences of trigger conditions. For example, a threshold breach can fire a secondary trigger only when a prior data event has also occurred. This allows you to build highly specific firing conditions without complex code.
Each trigger type supports retry policies. You define the number of retries, the backoff interval, and the fallback behavior. Failed trigger events are logged with full payload data so you can replay or investigate after the fact.
Yes. Before passing control to the first node, every trigger supports a condition gate — a set of field-level filters that must evaluate to true before the flow begins. This prevents unnecessary flow executions and keeps your system efficient.
GET STARTED
Configure your first trigger today.
Request access and build event-driven automation that fires on exactly the right conditions.