Peak Automations

How do I build an automation?

Write or say in one sentence what should happen automatically, for example “When a deal is won, create an onboarding task”. Peak shows what it understood as an if-then, asks only about what's still open, and checks connections, permissions and duplicate automations. Before turning it on, you test it: a test never runs anything externally.

1. 01Open Peak Automations and describe what should happen.
2. 02Answer the follow-up questions with one click.
3. 03Tap “Test” and then “Turn on”.

How do I build a multi-step workflow, such as client onboarding?

Under Automations › Workflows, owners and admins create workflows: from a template or step by step, with tasks in Peak Task, approvals in the inbox, actions, waiting periods and milestones, each with days from the start. Once published, a version is fixed; changes become the next version, and runs in progress keep their steps. You can start a workflow there via search, on a person's or company's page, or automatically with the “Start workflow” action in an automation.

1. 01Open Automations › Workflows and tap “New workflow”, or “Customize” on a template.
2. 02Define the steps and publish the workflow.
3. 03Start it under “Runs” for a person or company, or let an automation start it.

What happens when an automation fails?

For temporary errors, Peak retries a step several times with increasing intervals. Peak doesn't blindly repeat actions that send something externally, so nothing arrives twice. If it ultimately fails, the automation appears under “Needs attention”, you get a message in your inbox, and the history explains in plain language what's missing, such as “Reconnect Slack”.

Which automations need approval?

Steps with an external effect, such as an email to customers, wait for confirmation in the inbox before running. Only owners and admins approve risky steps. You can choose stricter approval for any step, but never looser than its risk requires.