Peak Docs · Resource · Automation recipes
Recipes for
document work.
Document work as traceable flows: three recipes from trigger to result, with what works in Peak Docs today and a local preview for what is planned.
Where do you want to make progress?
Write open points as a checklist in the notes.
Trigger. Step.
Result.
A good automation starts as a good process.
Before anything happens automatically, it must be clear who does what and when. These recipes describe three flows as trigger, step and result. The steps use what Peak Docs can do today: mentions, comments, tasks from documents. Scheduled and cross-app triggers are only a local preview here.
Have this ready for the recipes.
- A recurring document flow
- The people involved in it
- The result that tells you it's done
The learning path
Three recipes, step by step.
Recipe 1: meeting → tasks
Trigger: meeting notes are finished.
- Write open points as a checklist in the notes.
- Mention the owner with @; they see it in their inbox.
- Turn every checklist item into a task.
Every point from the meeting is a linked task.
If you get stuck
What works today and what is planned.
Does a recipe run on its own?
No. You carry out the steps in Peak Docs yourself today. The trigger preview on this page runs only locally in your browser and saves nothing.
Can Peak Docs send documents automatically?
No. Sending and scheduling are planned. Today you share a version through a read-only link.
Can an agent monitor documents?
Monitoring agents are planned and not available today. Freshness signals already show you which documents haven't been looked after for a long time.
Your quality check
Is your recipe traceable?
Tick what you have checked. Your selection stays in this view only.
0 of 3 points checked
What this article is based on.
Recipes with made-up examples, local preview without saving. @ mentions with inbox notifications, assigning and resolving comments, comment and checklist item → task, templates from your own documents (partial) and versions exist in Peak Docs today. Scheduled triggers, automatic sending and monitoring agents are planned.
- Editorial demo
Editorial example with made-up sample data. It describes features Peak Docs has today; everything else is marked as example, concept or planned.
Your first flow fits in three lines.
Try in the live preview how a document turns into tasks.
Frequently asked questions
Do the recipes on this page actually run?
No. They are a local preview in the browser. Nothing is saved or sent.
What works in the product today?
Comments and checklist items become tasks, and mentions land in the Inbox.
Are there monitoring agents?
No. Scheduled triggers and monitoring agents are planned.