Triggers

Triggers make things happen on autopilot. Reply to every customer email as soon as it comes in? Run payroll every two weeks? Send a project status update every Monday? Triggers handle it.

Two Types of Triggers

Scheduled Triggers

Run on a recurring schedule. You set the time, and it happens.

  • Daily standup report: Every weekday at 9 AM, your agent posts a summary to Discord
  • Weekly team report: Every Friday at 5 PM, your agent compiles the week's progress into a Google Sheet
  • Monthly invoice reminder: First of every month, your agent sends payment reminders

Each scheduled trigger shows its schedule in plain language (like "Weekdays at 9:00 AM") alongside the underlying schedule expression.

Event Triggers

Fire when something happens. You define the event, and your agent responds.

  • Incoming customer email: When a new email arrives in your support inbox, your agent drafts a response
  • New GitHub issue: When someone opens an issue, your agent triages it
  • Slack mention: When your team mentions a keyword, your agent jumps in

Event triggers watch a source service (like Gmail or GitHub) and react instantly.

What a Trigger Looks Like

Every trigger has:

  • Name: What this trigger does (e.g., "Daily Standup Report")
  • Prompt: The full instruction telling the agent what to do when the trigger fires
  • Type: Scheduled or Event
  • Agent: Which agent handles it (usually the Team Lead)
  • Status: Active, paused, or error
  • Activity: How many times it ran in the last 30 days

Some triggers also have an Approval badge, meaning the agent will ask for your sign-off before completing the action. See Approvals.

Managing Triggers

From the Triggers page in the portal, you see a table of all your triggers. You can filter by type (scheduled vs. event), search by name, and check activity at a glance.

Click any trigger to see its full prompt, adjust its schedule or event configuration, toggle it active or paused, or delete it.

Click "Add Trigger" to create a new one. Pick the type, choose the agent, write the prompt describing what should happen, and set the schedule or event source.

Triggers and Approvals

For high-stakes actions, you can mark a trigger as requiring approval. The agent will do the work but pause before taking the final action and ask you to confirm. This way you get automation without losing control over the decisions that matter.