Platform

Automations

Rules that watch your work and act on it — on an event, on a schedule, on a webhook, or when you say so.

Four ways to start

An automation runs when something happens in your workspace (an email arrives, a file changes, a meeting is created, a contact is updated), on a schedule in your own timezone, when a third-party system calls a signed webhook, or when you run it by hand.

Conditions in fields or in words

Match on concrete fields — sender, subject, label, size, project — or describe the condition in plain language and let the automations agent judge it. It is deliberately literal and conservative: a rule that fires when it should not is worse than one that occasionally does not fire.

Chains, not single actions

Steps run in sequence: notify someone, run an agent, write a document, publish a dashboard card. A step can be an agent decision whose answer gates everything after it, so a chain can branch on judgment rather than only on field values.

A human in the loop where it matters

Any step that reaches outside — sending mail in particular — can pause for your approval and resume exactly where it stopped once you answer. Approvals arrive as notifications, and nothing sends silently on your behalf.

·Event, schedule, webhook and manual triggers
·Structured or natural-language conditions
·Multi-step chains with agent-decision gates
·Approval-gated sends with durable resume