Automations

Automations are single-agent jobs you can stand up in under a minute. Write a prompt, pick a model, pick a few tools, pick a trigger — and Scrydon runs the agent on your schedule or whenever a webhook fires.

Automations are the right choice when you want an agent to do one well-defined thing repeatedly. For multi-step flows with branching, human-in-the-loop, or custom blocks, use a workflow instead.

When to Use an Automation vs a Workflow

Creating an Automation

1. Open Automations from the sidebar.
2. Click Create your first automation (or New automation if you already have some).
3. Fill in the form:
   • Name — shown in the list and the Monitor.
   • Description — optional context for teammates.
   • Prompt — what you want the agent to do on each run. Written in plain English.
   • Model — pick from the available models (e.g. anthropic/claude-sonnet-4-6).
   • Tools — the tools the agent may call during the run. Add vendor slugs (e.g. gmail, slack) or specific tool IDs.
   • Trigger — either:
     • Schedule: pick a preset (hourly, daily, weekdays, weekly) or enter a custom cron expression and timezone.
     • Webhook: optionally pick a URL path; Scrydon generates one for you if you leave it blank.
4. Click Save. The form saves even if it has warnings so you can come back and fix them later.
5. Toggle the Enabled switch to activate it.

Triggers

Schedule

Scheduled automations fire at times you define using cron syntax. The form offers common presets; if you need something custom, pick Custom and enter a cron expression.

Presets:

Timezone defaults to UTC. You can pick another timezone from the list if your schedule needs to align to a specific local time.

Webhook

Webhook automations fire when an HTTP request hits the automation's URL. You can leave the path blank — Scrydon generates one — or pick your own for a more memorable URL.

Fire an automation manually at any time from the detail page with Fire now. This bypasses the schedule/webhook and runs the agent immediately with an empty input (or whatever input you POST to the fire endpoint).

Tools

Tools are how the agent reaches out to the world: reading Gmail, posting to Slack, querying a CRM, and so on. You list the tools the agent is allowed to use; Scrydon exposes them to the model at runtime.

You can specify tools two ways:

• Vendor slug (e.g. gmail) — gives the agent access to the vendor's full tool set.
• Specific tool ID (e.g. gmail.send) — gives the agent access to just one tool.

Connect a vendor from the Connections page before referencing it in an automation. The strict-mode validator will flag any tool the agent cannot actually call.

Monitoring Runs

Every automation run is logged the same way workflow runs are, so the Monitor page shows them too.

• Click Monitor in the sidebar.
• Use the [All | Workflows | Automations] filter at the top to narrow the view.
• The URL updates to ?type=automations so you can bookmark or share the filtered view.

Automations also show Enabled/Paused status on the list page so you can see at a glance which are actively running.

Enable, Disable, Delete

From the automation's detail page you can:

• Toggle Enabled — pause or resume without losing configuration.
• Fire now — run once on demand. Useful for testing.
• Edit — re-open the form to change prompt, model, tools, or trigger.
• Delete — permanently remove the automation and its schedule.

Disabling is always allowed — you can pause a running automation even if its configuration has since drifted.

Limits

• Automations are scoped to a workspace, not an environment. Switching environments does not change which automations you see.
• An automation is always a single agent with a single trigger. If you need more, build a workflow.
• Webhook automations accept JSON bodies; the payload is passed to the agent as input.

Related

• Schedule triggers in workflows
• Webhook triggers in workflows
• Connecting tools and vendors