AGENT ATLASa field guide to agent workflows
Back to Automation & triggers
Automation & triggers

Event-driven triggers

Fire the workflow when something happens — a webhook, a new row, an email.

1 agentCore

How it works

  1. 1Subscribe to the event source — webhook, queue, or watch.
  2. 2Filter to the events you actually care about.
  3. 3Trigger the workflow with the event payload as input.
  4. 4Make handling idempotent so duplicate events don't double-act.

Use it when

Reacting to real-world events in near-real-time — new signup, new ticket, file uploaded, payment received.

Reach for something else when

The event is noisy or high-volume without filtering, or you actually want batched periodic runs.

Where you stay in the loop

You define which events matter and the idempotency rules; the agent reacts. Watch the filter — noisy triggers and double-acting on duplicates are where unattended automation bites.

In the wild

When a new support email arrives, an agent classifies it and drafts a reply for review.

Hand this to your agent

Design an event-driven automation.

For my trigger event, tell me: (1) what payload the event carries, (2) a
filter rule for which events should actually run the workflow, (3) the steps
the agent takes with that payload, (4) how to make it idempotent so
duplicates are safe.

Event: <...>

Replace the <…> placeholders, paste it into your agent, and it'll scaffold the workflow with you.