Schedule an automation

Who can do this

In a private feature, the owner (any User) can create automations. In shared features, creation requires Data Admin or a workspace admin. Any member can view the automations they have access to.

An automation pairs one trigger with one action. Like most resources, you create automations by asking Ronja in an exploration; the Automations page is where you monitor and manage them.

Create one

1. Open an exploration.
2. Ask for the automation — the product’s own suggestion: “Schedule a daily revenue summary every morning at 9 AM”.
3. Let Ronja author or find the Workflow or Saved Agent first — the action must exist before it can be scheduled.
4. Find the result on the Automations page, with run history and health at a glance.

The Automations page: every trigger–action pair, its schedule, and its recent runs.

Triggers and their allowed actions

Trigger	Fires when…	Can run
Schedule	a cadence you set — minimum interval is 1 hour	Workflow or Saved Agent
Email	mail arrives at the automation’s private Routable address	Saved Agent only
Webhook	JSON is POSTed to the automation’s Receiver URL	Saved Agent only
Table	a watched table finishes rebuilding	Workflow or Saved Agent

The trigger kind is fixed at creation (“Trigger kind cannot be changed after creation.”). Field-by-field detail lives in Automation triggers.

Whoever can reach the trigger can run AI on your data

Email and webhook triggers run AI-generated actions on content from outside your organization. Whatever can reach the trigger — a matching sender, or anyone holding the URL — can make Ronja act. Lock both down (allowlist, signing secret) as shown below.

Email. An admin must first set the organization’s Email-trigger ingest prefix (Organization → Governance). The automation then gets a private address — copy it from the Routable address chip — and you must allowlist sender domains or addresses; an email trigger can’t be enabled with an empty allowlist.

Caution

The sender allowlist is the entire authorization — anyone matching it can fire the automation with external content. Keep it tight. Rotate invalidates the old address immediately.

Webhook. Copy the Receiver URL into the calling system. Add a Signing secret so requests must be signed (“Signed (HMAC)”); without one, “the URL is the secret”.

Caution

The signing secret is shown exactly once — copy it when it appears. An unsigned webhook can be fired by anyone holding the URL. Webhooks cap at 1,000 runs per rolling 24 hours.

Table. Pick the Watched tables — “The automation fires when any watched table finishes (re)building.” Up to 25 watched tables, capped at 50 runs per rolling 24 hours as a loop guard.

Approval emails

When a workflow run needs a human decision, approvers receive an email — “[Ronja] A workflow run needs your approval” — with Approve and Reject buttons that open a confirmation page. Nothing is decided until you confirm there.

Caution

An automation cannot fire an approval-gated workflow — the run fails closed at the gate. Run gated workflows from a chat instead. See Create a workflow.

Pause, resume, run now, delete

1. Flip the on/off toggle on any row (or in the detail sidebar) to pause or resume. Paused email and webhook automations silently ignore inbound traffic.
2. Click the run icon on a row (or Run now in the sidebar menu) for an immediate manual fire — refused while a run is already in flight.
3. Delete via the row’s trash icon (the Delete automation confirm). The automation moves to the Trash for 30 days and is auto-paused; an admin can restore it.