Automations

Automations

An automation connects something that happened to something that should happen.

Events

• a workflow run finished (succeeded, or failed)
• a monitor detected a change
• a schedule fired
• an inbound webhook arrived

Actions

Action	What it does
run_workflow	Run another workflow, optionally passing data from the event.
webhook	POST a payload to a URL you control.
notification	Raise an in-app notification.
email	Send mail through your configured SMTP server.

Chains are allowed: a monitor trips → a workflow collects the detail → its completion fires a webhook into your own system.

Building one

Automations → New. Pick the trigger, pick the action, and map any data the action needs from the event. The flow builder shows the chain as blocks.

Webhooks out

The webhook action POSTs JSON to your endpoint. Outbound targets are subject to the same SSRF guard as everything else — a private or loopback address is refused unless ALLOW_PRIVATE_TARGETS=true. If you are posting to a service on the same host, that is the setting you need, and you should understand what it opens up before enabling it.

Webhooks in

An inbound webhook can trigger a workflow, which is how you drive Writ from another system without polling.

Notifications

Channels are configured in Settings → Notifications and driven against your own accounts: SMTP for email, Pushover, or Twilio for SMS/WhatsApp. Nothing is relayed through a third party. Per-event preferences live in the notification matrix, so a noisy automation does not have to mean a noisy inbox.