Event-triggered actions

How Automations run

Each of your organization’s Automations has one trigger, optional conditions and one action, does its durable work outside the browser and records every run in Run history.

Each Automation saves a single action

When the same event should drive two outcomes, create a second Automation with its own state and history.

Disable an Automation and keep its history

An enabled Automation processes matching events. A disabled one keeps its definition and history but ignores normal events. New webhook Automations start disabled.

Signed and timestamped requests

Each request is a POST with one JSON object up to 256 KiB, a Unix timestamp within five minutes, an HMAC-SHA256 signature and an idempotency key of up to 200 bytes.

The signing secret is shown once

You see the signing secret only when you create or rotate it. Rotating invalidates the old one immediately, with no overlap.

Map headings and links from trigger fields

Map an Agent message’s prefix and suffix from $trigger fields so headings and links stay exact. Trusted instructions take up to 20,000 bytes, a message up to 40,000.

Control Automations with Contacts permissions

view_contacts lets you browse Automations and their history. manage_contacts is required to create, edit, enable, test or retry one.