An agent that only runs when you click a button is a tool. An agent that runs when a payment comes in, when a lead is created, when a repository gets a push, when a schedule fires — that's infrastructure.
Today, we're launching 55+ triggers and webhooks that make your AACFlow agents event-driven. They don't wait for you. They respond to the world.
The Three Trigger Types
Every trigger on AACFlow falls into one of three categories:
Webhook triggers — your agent runs when an external service sends an HTTP request to your workflow's unique webhook URL. A Stripe payment succeeds → webhook fires → agent processes the order, updates the CRM, sends a receipt. A GitHub push lands → webhook fires → agent runs CI checks, posts to Slack, updates the deployment tracker.
Polling triggers — your agent checks an external service for new data on a configurable interval. Every 5 minutes: check Gmail for new emails matching a query. Every 15 minutes: check AmoCRM for new leads. Every hour: check Wildberries for new orders. The platform handles the polling loop, rate limiting, and deduplication — you just configure the source and the interval.
Scheduled triggers — your agent runs on a cron schedule. "Every weekday at 9 AM: generate a daily sales report and post to Slack." "Every Monday at 8 AM: pull bank statements, match against invoices, flag discrepancies." Standard cron syntax, full timezone support.
