They start clean, then every exception adds a fork. After a year it is a maze nobody wants to touch.
Nobody notices the pricing-page visit at 10:47 PM. Nobody reads the Gong transcript that mentioned a competitor.
Check-every-hour cadences turn a two-minute response window into a two-hour miss.
n8n, Make, Tray — the flow is a graph in a tool the GTM team cannot read.
Point any system at a Trigger URL. The payload becomes structured context for the dispatched agent.
Watch Gmail for replies, bounces, out-of-offices. Each triggers the right follow-up agent with full thread context.
HubSpot or Salesforce: a stage change, new contact, or custom field flip dispatches the matching agent instantly.
LinkedIn post signals, 6sense intent surges, RSS feeds, Reddit mentions — pluggable sources, one dispatch layer.
Cron-style schedules for recurring audits — daily pipeline health, weekly closed-lost rollup — no babysitting.
ICP filters, dedup windows, per-agent rate caps (Reply Guy caps at 5 Reddit / 10 X per day) enforced by the platform.
You do not build a graph. You pick an agent, a filter, a source. The agent's doctrine handles the long tail.
Every dispatched run shows up in the runs list with source event, filter decisions, tool calls, and outcome.
Pause or remove a Trigger with one click. The receiving agent keeps working on the runs already in flight.
Declare the payload shape once; incoming events are validated before an agent ever sees them.
Two signals about the same contact in 30 minutes become one agent run, not two duplicate outreaches.
Transient failures retry on an exponential schedule. Dead-letter queue for anything beyond the limit.
Every trigger-started run writes a full transcript to `runs/<date>-<agent>/` — grep-able, replayable.
Gmail, HubSpot, Salesforce, Apollo, Gong, Clay, Stripe, Segment, Linear, GitHub, Slack, Zendesk.
A one-off chat that solved a problem can be promoted to a recurring trigger in two clicks.
For revenue workflows, yes. Zapier is great for static flows. Triggers dispatch to agents that handle judgment — edge cases, long tails, weird inputs — without you building a forked graph for each one.
Per-agent rate caps, per-trigger daily caps, and a global kill-switch that pauses every trigger across the workspace in one click.
Yes — the Runs list is chronological (fixed in 0.5.21) and includes both chat-initiated and trigger-initiated runs.
Cron-style schedules fire the same dispatch path — Pipeline Ops daily at 8am, Closed-lost Analysis every Monday, whatever cadence you want.
