Automate
Triggers
A trigger runs your agent automatically — on a schedule or in response to an event — so it works while you're away. Use triggers for daily digests, monitors, reminders, and reports.
Types of triggers
Scheduled (cron)
Run a prompt on a timetable — for example “every weekday at 9am, summarize my open GitHub PRs and post to Telegram.” Backed by the instance's built-in cron scheduling.
Inbound email
Every instance has a unique inbound address (see Email). Mail sent to it arrives as a message your agent can act on — forward alerts or newsletters and let the agent triage them.
Chat commands & webhooks
Messages from a connected channel trigger the agent in real time. For programmatic events, combine a scheduled task with an integration (e.g. polling GitHub) to react to outside systems.
Create a scheduled trigger
Describe the task
In chat, tell your agent what to do and when — for example, “Every day at 8am, check my calendar and send me today's agenda.” The agent sets up the schedule for you.
Make sure the tools are connected
If the task needs an external service, add the matching secret to your Agent Environment Profile and connect the integration first, then Redeploy.
Pick where results go
Tell the agent which channel to post to (Telegram, Slack, Discord, or email). It will deliver each run there.
Confirm it's scheduled
Ask the agent to list its scheduled tasks to confirm the trigger exists, then let it run. You can adjust or remove it anytime by asking.
Tips & troubleshooting
- Schedules run in the instance's time zone. Be explicit (e.g.
9am UTC) to avoid surprises. - Triggers need a running instance.A stopped instance won't fire scheduled tasks — keep it Running if you rely on automation.
- No output? Check that the target channel is connected and the required secret is present, then redeploy. See Troubleshooting.