Peak Automations · Academy
Your first automation,
learned step by step.
Peak Automations Academy: three lessons on describing a routine in one sentence, testing it safely and only then switching it on, with approvals for risky steps.
Where do you want to make progress?
Start with the trigger: “When a form is submitted …” or “Every Monday at eight …”.
Describe. Test.
Only then switch it on.
- 01Lesson 1 · Describe the routine
- 02Lesson 2 · Read the test run
- 03Lesson 3 · Switch on and understand approvals
Automating here doesn't mean wiring boxes together.
You type or say what should happen, for example “When someone submits the enquiry form, create the contact and give me a task for tomorrow”. Peak turns the sentence into a checked automation, asks when something is unclear and shows it to you as a sentence and as a flow. It only goes live once a test run of the current version has passed.
What you need for the lessons.
- A Peak One workspace and a routine that keeps coming back for you
- For external steps, a connection a person set up under Settings → Integrations
- Ten quiet minutes to read the test run properly
The learning path
One sentence. One test. One approval.
Lesson 1 · Describe the routine
What should happen, when, and for whom?
- Start with the trigger: “When a form is submitted …” or “Every Monday at eight …”.
- Then name the actions in the order they should run.
- Answer the questions Peak asks back instead of skipping them.
An automation you see as a sentence and as a flow of boxes and arrows.
If you get stuck
When something gets stuck.
Peak asks me a question instead of building the automation.
Then one part of your sentence is ambiguous, such as who should get the task. Peak doesn't guess; it asks. Answer the question or extend the sentence.
The test run reports a missing connection.
External steps such as a Slack message only run through a connection of your workspace. A person adds it under Settings → Integrations; Peak connects nothing in the background.
A run says “Waiting for approval”.
The step counts as risky, for example an e-mail to customers. It only runs once someone confirms it in the Inbox or an owner or admin approves it.
Your quality check
What you can do after the academy.
Tick what you have checked. Your selection stays in this view only.
0 of 3 points checked
What this article is based on.
Lessons with a fictional sample company, no real data. Describing by text or voice, clarifying questions, sentence and flow view, test runs, activation after a passed test, versions, approvals through the Inbox and run history are available in Peak Automations today.
- Editorial demo
Editorial example with made-up sample data. Describing in a sentence, clarifying questions, test runs, activation after a passed test, versions, approvals for risky steps and run history exist in Peak Automations today; everything else is marked as example or planned.
One routine less to keep in your head.
Start Peak Automations, describe your first routine in one sentence and read the test run before you switch it on.
Frequently asked questions
Do I need to know how to code?
No. You describe in one sentence, typed or spoken, what should happen. Peak asks when something is unclear.
Why do I have to test before switching on?
An automation only goes live once a test run of its current version has passed. That way you see beforehand what it would do.
What happens with risky steps?
They wait for a confirmation or an owner or admin approval in the Inbox, for example before an e-mail goes out.