Use “Brief the next meeting from its minutes” in Recued. Start from the last minutes and the project as it stands: what was carried over, where each action is now, what is overdue, what moved, and who holds what. No AI or calendar involved, and nothing is saved.
Brief the next meeting from its minutes
Use “Brief the next meeting from its minutes” in Recued. Start from the last minutes and the project as it stands: what was carried over, where each action is now, what is overdue, what moved, and who holds what. No AI or calendar involved, and nothing is saved.
Complete workflow
Use Meeting Minutes in Recued. Write the minutes yourself, turn each action item into a task for the person it names in a federated project, and brief the next meeting from what happened since, with no AI, calendar, or recording involved.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Record meeting minutes into project work” in Recued. Write the decisions, the action items and what is still open. Each action becomes a task for the participant it names, what you took on becomes your promise, and the next briefing starts from it. No AI or calendar involved.
Start the meeting from where the last one ended
Pick the project and Recued prepares the briefing from two things it already has: the last minutes you recorded for the project, and the project's tasks as they stand now.
Nothing outside Recued is involved: no calendar, no AI model, nothing to connect. Every line comes from a recorded minute or a task, so nothing in the briefing is a guess.
What it shows
- Carried over: the open questions the last minutes kept for this meeting.
- Last time's actions: every task the last minutes created, and where it stands now: done, in progress, overdue, not started, or no longer in the project. A task reassigned since shows who holds it today.
- Overdue: open tasks due before the meeting starts.
- Changed since and Done since: what moved after the last meeting.
- Open work by person: every open task, grouped by who holds it.
- Your open promises: what you took on for this project and have not yet done.
- Waiting on other teams: blocking dependencies on work in someone else's Recued.
- Decided last time: the decisions from the last minutes, for reference.
The window
"Since" means since the last minutes recorded for this project. Enter a time under Look back from to use a different one. With no minutes recorded yet, the briefing shows current work only and leaves the "since" sections empty rather than treating everything as new.
What it reads
Up to 200 tasks and 200 of your most recent promises. The briefing says how many tasks it did not read. It saves nothing, so run it as often as you like.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
since
setting
=
meeting at
setting
=
project ref
setting
=
[object Object]
meeting title
setting
=
Uses (5 operations)
core.work-entity.get
core.storage.shared.read
recued-core.federated-projects.participant.search
core.work-entity.list
recued-core.federated-projects.remote_dependency.search
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
2 more aren't listed here. You'll see them at install.