Automations

Describe an automation in plain language. Your agent writes it, it runs on your server, and every run shows up in a built-in dashboard.

Describe it, don't build it

You don't hand-write cron jobs or webhook handlers. You tell your agent what you want — in a sentence — and it scaffolds, writes, and starts the automation:

"Email me the new signups every morning at 9."

"When Stripe says a payment succeeded, log it and post to Slack."

That's the whole interface. The automation becomes part of your app — same code, same database, same deploy — so it can use everything your app already can.

Runs on a schedule

An automation can run on a clock — every few minutes, hourly, every weekday morning, whatever you describe. The dashboard shows the next run time, and you can trigger one yourself with Run now instead of waiting for it.

"Every hour, check our status page and alert Slack if anything is down."

Reacts to events

An automation can also run when something happens elsewhere — a payment, a GitHub push, a form submission. For Stripe, GitHub, and Slack the request is signature-verified for you, so only the real provider can trigger it. You get a URL to paste into the provider's settings, and every delivery is stored with its full payload.

"When a GitHub issue is opened, label it and post it to our triage channel."

Every run, recorded

Open the automation and you get a dashboard: armed schedules and their next run, recent runs with status, duration, and output, and webhook deliveries with their payloads. Re-run anything with Run now; re-fire a stored webhook with Replay. The observability is built in — there's nothing to set up.

Keep your history

Run history lives in whatever database you bind — Postgres, MySQL, MongoDB, or Redis. Bind one and history survives redeploys; with nothing bound it's in-memory and resets, and the dashboard says so. The database is yours, so there's no retention limit and nothing to configure:

agentry service bind postgres

The automation picks it up on the next start — no change to ask for.

Ship it

An automation is a normal app, so it deploys like one: one click in the dashboard and it runs as a durable service at a stable URL, schedules and webhooks live. See Ship an app.

Next: Examples →