Peak Automations / For project teams
The work is finished.Nobody knows yet.
In projects, time is rarely lost in the work itself but between two people. With Peak Automations you describe in one sentence what should happen when a task is completed, blocked or a project is created: Peak creates the next task, notifies people in the Inbox or posts to your Slack channel. It only goes live after a passed test.
Put the goal into words. Add perspectives and timing right below.
Two typical hand-offs. One sentence per automation.
One project / two typical hand-offs
From “done” to the next task.
- When
- A task in Peak Task is completed
- Only if
- The title contains “Draft”
- Then
- Create a review task and notify in the Inbox
Your first project automation
How would you describe it?
Create a local note from three answers. Nothing is connected, tested or switched on; the note stays in this preview.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three thoughts. A hand-off that runs on its own.
Draft · not yet put together
- The trigger
- Still open
- The next person
- Still open
- The step
- Still open
Two moments in everyday project work
Which hand-off sticks for you?
Choose the case. Trigger, steps and sample note follow the situation.
Running project
A draft task is marked as done.
- The action
- Peak creates a review task about the same thing and notifies the responsible person.
- The intent
- The review starts without anyone having to ask.
The hand-off note
- Trigger
- Task completed
- Step
- Create task, notify
- Before going live
- Test run with a sample task
The example makes the flow clear. The product proof shows where it starts in Peak Automations.
To the product proofDoes this fit you?
Recurring hand-offs. Clear limits.
One project,
fewer follow-ups.
This is where Peak Automations helps.
- You work with tasks and projects in Peak and want to stop triggering hand-offs by hand.
- You want blockers to show up in Slack or the Inbox as soon as they're set.
- You need to trace when which automation did what.
Every change a version
What it doesn't do today.
- An automation doesn't branch into several paths today; for two paths you create two automations.
- Inactivity triggers (“no movement for three days”) are planned and not available yet.
- Peak doesn't plan projects for you or hand out work at its own discretion.
The next proof is the product
Describe your first hand-off in Peak.
Write the sentence in Peak Automations, look at the flow view and start the test run. Templates only show you what fits the apps your workspace has connected.
Start Peak AutomationsPeak Automations / Your next step
The best hand-off is the one nobody has to think about.
Pick the hand-off that sticks most often for you. That becomes your first automation.
See the project examples
Hand-offs that don't get lost in chat.
Create a review task and notify in the Inbox
Frequently asked questions
Which project events can trigger an automation?
Today: task created, completed or blocked, and project created. Plus schedules, webhooks and manual start. Inactivity triggers are planned.
Can one automation take several paths?
A condition lets an automation continue or stop. Branching inside one automation is planned; today you create two automations for two paths.
What happens when I change an automation?
Every change becomes a new version. It only goes live once its test run has passed.