Triggers — run on a schedule or when called
The Triggers tab — cron schedules with a time zone, inbound webhooks with a one-time secret, enable/disable and failure tracking.
The Triggers tab makes an agent run without anybody clicking Run. Needs a plan with Webhooks and triggers (Starter and up) — otherwise the tab shows a lock with an upgrade link. The agent must be active for a trigger to fire.
On a schedule
Pick a preset or type a 5-field cron, and a time zone:
| Preset | Cron |
|---|---|
| Every hour | 0 * * * * |
| Every day at 09:00 | 0 9 * * * |
| Every weekday at 09:00 | 0 9 * * 1-5 |
| Every Monday at 09:00 | 0 9 * * 1 |
| The 1st of each month at 09:00 | 0 9 1 * * |
At each tick Ragenta creates a run with empty input (the agent relies on its Instructions for the
job). Results appear in History with trigger schedule.
When another system calls it
Ragenta issues a URL of the form POST {origin}/api/v1/hooks/{triggerId} and a secret.
The secret is shown once, in the SecretOnce block right after creation. Copy it then; afterwards the only option is a new trigger.
The caller sends the header X-Ragenta-Secret: <secret> and a JSON body { "input": "..." }.
Every failure (wrong secret, trigger disabled, agent not active) answers 404 so nothing reveals
whether a trigger exists. Limit: 60 calls per minute per IP.
Managing
- The Enabled switch pauses a trigger without deleting it.
- The failures column counts consecutive failed runs; last error keeps the latest message.
- Remove deletes the trigger after confirmation.
Flow — multi-step processes
Draw the agent as a graph of steps on a canvas, draft it from a sentence, validate before publishing, and handle a failing step.
Versions — compare and go back
The Versions tab — the version list, a diff between two versions, restoring an old one, and trying one question against several versions.