Skip to main content
Automation triggers let agents act without a human starting the conversation. Set up schedules, react to conversation events, or let agents manage their own automations.

​
Enabling Triggers

1

Open Agent Settings

Navigate to Agents > Select your agent > Settings
2

Find Automation Triggers

Scroll to the Automation Triggers section
3

Toggle Trigger Types

Enable the trigger types you need:
  • Scheduled (Cron) — Time-based triggers
  • Event-Based (Whenhook) — Conversation event triggers
  • Proactive Automations — Agent self-creates automations
The master Enabled toggle must be on for any triggers to function. Individual toggles control which types are available.

​
Creating a Scheduled Trigger

1

Open Automations

Agents > Select agent > Automations tab
2

Click Create

Click Create Automation and select Time-based
3

Configure Schedule

  • Name — Descriptive name (max 200 characters)
  • Frequency — Once, Daily, Weekly, Monthly, or Yearly
  • Time — When to fire (HH:MM)
  • Date options — Varies by frequency (day of week, day of month, etc.)
  • Prompt — The message sent to the agent when triggered
4

Optional Settings

  • Max runs — Stop after N executions (leave blank for unlimited)
  • Active hours — Restrict to specific hours and timezone
  • Expiration — Auto-disable after a date
5

Save

Click Create. The automation appears in the Time-based tab.

​
Schedule Types

Under the hood, these are converted to cron expressions. You can also set cron expressions directly via the API or agent tools.

​
Creating an Event-Based Trigger (Whenhook)

1

Open Automations

Agents > Select agent > Automations tab
2

Click Create

Click Create Automation and select Event-based
3

Configure Condition

  • Name — Descriptive name (max 200 characters)
  • Description — Natural language condition (sent to LLM for evaluation)
  • Keywords — Comma-separated trigger words for fast prefiltering (required)
  • Confidence threshold — How sure the LLM must be (0.0–1.0, default: 0.7)
4

Configure Action

  • Prompt — The message sent to the agent when the condition matches
5

Optional Settings

  • Cooldown — Minimum time between firings (default: 1 hour, minimum: 5 minutes)
  • Max triggers — Stop after N firings (leave blank for unlimited)
  • Active hours — Restrict to specific hours and timezone
  • Expiration — Auto-disable after a date
6

Save

Click Create. The automation appears in the Event-based tab.

​
How Event Evaluation Works

When a message is processed in a conversation with this agent:
  1. Keyword prefilter — Fast check: does the message contain any of the keywords? (case-insensitive)
  2. LLM evaluation — If keywords match, an LLM evaluates whether the condition description is truly met
  3. Confidence check — If the LLM’s confidence exceeds the threshold, the trigger fires
  4. Cooldown — The automation enters cooldown regardless of whether it fires (prevents rapid re-evaluation)
Choose keywords carefully. They act as a cheap gate — only messages containing at least one keyword reach the LLM evaluation step.

​
Proactive Automations

When Proactive Automations is enabled, the agent gains access to self-management tools:

​
Schedule Tools

​
Event Tools

Example conversation:
Agent-created automations follow the same quotas and limits as manually created ones.

​
Managing Automations

​
Viewing

The Automations tab shows two lists:
  • Time-based — All scheduled automations with next run time, run count, and status
  • Event-based — All whenhook automations with trigger count, cooldown, and status

​
Status

Each automation shows:
  • Active — Running normally
  • Paused — Manually disabled or auto-disabled

​
Creator

Automations show who created them:
  • User — Created via Console
  • Agent — Created via proactive automation tools

​
Deleting

Click the delete action on any automation to permanently remove it.

​
Limits

Daily firing budgets reset at midnight UTC.

​
Best Practices

​
Use Specific Keywords

Broad keywords like “the” or “data” will cause excessive LLM evaluations. Use specific terms related to the condition you’re watching for.

​
Set Appropriate Cooldowns

The default 1-hour cooldown works for most cases. Lower it for time-sensitive monitoring, raise it for daily summary triggers.

​
Monitor Failure Counts

Automations auto-disable after 5 consecutive failures. Check the Automations tab for paused automations and investigate the cause.

​
Use Active Hours

Restrict automations to business hours when relevant. This saves daily firing budget and prevents off-hours noise.

​
Start Conservative

Begin with higher confidence thresholds (0.8+) and adjust downward if the trigger isn’t sensitive enough. It’s easier to loosen than to deal with false positives.

​
Troubleshooting

​
Next Steps