Agents can run on events and on schedules. Schedules are stored as cron strings and run on the server, so they work after you close the tab.
Triggers
- Event: for example, a contact form was submitted on your site.
- Schedule: a recurring time, such as weekdays at 10:00 or Monday at 09:00.
- Manual: the Run now button.
The built-in agents use the schedules above: a proposal reminder on weekdays at 10:00 Eastern, a weekly report on Monday at 9:00 Eastern, and social posts on Tuesday and Thursday at 11:00 Eastern.
Reading cron strings
A cron string has five fields: minute, hour, day of month, month, day of week.
0 14 * * 1-5 at 14:00 UTC, Monday to Friday
0 13 * * 1 at 13:00 UTC every MondayKeplar stores schedule times in UTC. If you see a cron string and want to know your local time, convert it; remember that UTC does not shift with daylight saving time, so a schedule that is 10:00 Eastern in winter is 11:00 Eastern in summer unless it is adjusted.
What a scheduled run may do
It may read, think and prepare. Every outbound action it wants to take is placed in the approval queue. Nothing is sent without you.
When a run does not happen
- The agent is paused or killed.
- The workspace was stopped with Stop all agents.
- The per-agent or workspace caps were reached.
- Your plan no longer includes agents.
Checking history
The audit log and the agent's activity list show every run, including skipped ones and why.
Related
- Agent guardrails: Spend caps, approval gates, auto-send rules, kill switches and the audit log: how Keplar limits what an agent can do and spend.
- Agents overview: What a Keplar agent is, which plans include agents, the built-in agents, how to run, pause and stop them, and what they cost.
- Business tools: forms, CRM, inbox and dashboard: How a contact form on a Create site becomes a lead, a deal and a drafted reply, and what the dashboard, CRM, inbox, orders and audit log show.