01 / The existing evidence
A concept, not a feature
Document automations are not built. Nothing on this page runs in the product.
Mapping
- Mapping
- Concept
- Arrival in the workspace
- Not checked
Peak Docs · Automations (preview)
Recurring steps
as a flow you can check.
The idea: when a document reaches a state, a defined next step follows. Document automations are planned and not available yet. This page shows a concept.
Start Peak DocsPlanned – not available yet · concept preview · no execution
Peak DocsThe triggerTaskThe actionTask · Example mapping
One mapping in detail
01 / Peak DocsTrigger
02 / Fictional test valueApproved (example)
03 / Task
document.statusA readable path as an example. No transfer.
View all 5 mappings
| Peak Docs | Task element |
|---|---|
| Trigger | document.status |
| Condition | checklist.open |
| Action | task.create |
| Owner | task.assignee |
| Status | availability |
Concept
No transfer
No transfer
Document automations are planned. In the product you create tasks by click today.
One concrete targetTaskArrival in the workspaceNot checked yet
Understand structure. Keep the source.
TaskArrival in the workspaceNot checked yetThe mapping shows the translation. Only a test in your workspace shows what actually arrives.
02 / What exists today
Today by click. Later as a flow.
The manual step is already built: a comment or a checklist item becomes a task with one click.
- 01 / The trigger
Today: checklist → task
A checklist item becomes a task linked to the document on click.
When should something happen?Document doneComment openDate reached - 02 / The action
Today: comment → task
A comment can be taken over as a task and assigned.
What follows?Create a taskAssign a personNotice in the Inbox - 03 / The status
Planned: trigger and rule
A flow that suggests such steps itself at a given state. Not available yet.
What exists already?By hand: builtAutomatic: plannedSending: no
Trust needs clarity
Status, requirements and limits.
Mapping02 / Your check
No sending
Even the plan includes no silent sending. Steps with an outside effect should need approval.
- Account
- Not connected
- Permission
- Grant in the product
03 / The clear limit
By hand today
Today you create tasks from comments and checklists yourself, with a click.
- By hand
- Concept
- Planned
- No sending
The next step
By click today. The rest is coming.
Start Peak Docs and turn your first checklist item into a task.
Start Peak Docs→Today you create tasks from comments and checklists yourself.
Frequently asked questions
Do document automations exist yet?
No. They are planned. This page shows a concept; none of it runs in the product.
What works today?
You turn a comment or a checklist item into a task with one click, linked to the document.
Will documents be sent automatically later?
Peak Docs sends nothing today. Planned steps with an outside effect are meant to require approval.