Draft · not indexed. Part of what this page describes is not generally available yet.
Peak One · Product
Repeated chores don't need a person. Decisions do.
Peak Automations handles recurring steps by your rules: trigger, condition, action. Every automation is tested before it is switched on, and risky steps wait for approval.
Try it
Step 1 of 4 · Trigger
Sample data · nothing is savedA task in the “relaunch” project moves to “review”.
Interactive demo with invented sample data. No account, nothing is saved or sent.
Trigger, action, outcome
Trigger, condition, action
When a task moves to review and the client is X, create a follow-up task. Easy to read, no code.
Test first, then switch on
An automation only runs once a test of its current version has passed.
Approval for risky steps
Steps with outside effect wait in the Inbox for confirmation or for approval by an owner or admin.
Writes to the real objects
A created task is a regular Peak Task row, not an entry in a separate automation list.
Agents: planned
Agents that steer projects on their own are planned. Today there are automations with approval.
An example
Onboarding at Agentur Nordlicht
Example: When a new client project is created at Agentur Nordlicht, an automation adds the three kickoff tasks. The step “Welcome email to the client” waits in Sophie's Inbox for her approval.
All pages in this area
Frequently asked questions
Are automations available?
Yes. Peak Automations is available in Peak One.
And AI agents?
They are planned. Until then, automations with tests and approval handle the recurring steps.
Can an automation send something wrong?
Steps with outside effect wait for confirmation. Without it, nothing leaves the workspace.
Who can approve?
Depending on the risk, the person themselves or the workspace owners and admins.
Routine to rules, judgment to you.
Walk through the flow in the demo, then build your first automation for free.
Start for free