Triggers

A trigger is what wakes an agent up. Set it up once, then forget it. The agent runs whenever the trigger fires; you don't have to remember to start anything.

In practice you almost never set up a trigger by hand. You tell the agent the outcome ("every Monday morning…", "the moment a deal closes…", "whenever someone emails support…") and it picks the right kind of trigger for you. This page is just so you know what's possible.

Ways an agent can wake up

• On a schedule. "Every weekday at 9." "First of the month." "Every fifteen minutes during business hours." Good for digests, periodic reports, recurring cleanups.
• When something happens in a connected tool. A new email lands. Someone @-mentions you in Slack. A deal closes. A form is submitted. A row is updated. The agent reacts within a second or two.
• When you message it. Sometimes you just want an assistant on call. The trigger is your message. Agent wakes, does the work, replies, goes back to sleep.
• When another agent asks for help. Agents can hand work to each other when the job is bigger than one of them.
• From an inbound email or text. Give the agent its own email address or phone number. Anything sent there wakes it up, attachments and all.

Keeping the noise down

Some triggers can fire constantly. Every Slack message in a busy channel. Every webhook from a chatty vendor. You don't want the agent waking up for stuff that doesn't matter. Just tell it the criteria in plain English when you set it up:

Only wake up for messages in #engineering. Skip anything from bots. Only fire if the message mentions "deploy" or "rollback."

The agent sets the filter up and plays back what it heard.

Setting one up

You almost never click through a form for this. You just ask in chat:

Wake up every weekday at 9 AM and post the engineering standup digest to #engineering.

The agent picks the trigger, wires the connections, and shows you the plan before saving anything. You can review, edit, or kill the trigger anytime from the agent's detail page.

Reviewing and pausing

Every agent's detail page lists its triggers, when each one last fired, and a Pause button. Pause takes the agent offline without losing setup or history. Resume brings it back exactly where it was.