Use “Prepare the next meeting from its minutes” in Recued. Starts from the last minutes you recorded and current project progress, adds what is new since, and prepares the project portion: what is still open, decisions for the room, and new topics.
Prepare the next meeting from its minutes
Use “Prepare the next meeting from its minutes” in Recued. Starts from the last minutes you recorded and current project progress, adds what is new since, and prepares the project portion: what is still open, decisions for the room, and new topics.
Complete workflow
Use Meeting Secretary in Recued. One person keeps the meeting loop: upload the minutes you wrote and AI turns them into tasks in the federated projects you share, mail the minutes out, then brief the next meeting from the last minutes, current progress and what is new.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Turn a minutes file into project work” in Recued. Upload the minutes you wrote, then review supported progress and task changes in the projects you share, plus an index of what you promised. The next briefing starts from these minutes.
Use “Mail the minutes and who does what” in Recued. Send the last minutes you recorded for a project to the people who were there, each with the tasks the meeting assigned. From your own mail account, one message per person, never twice.
Use “Mail the briefing before the meeting” in Recued. Send the briefing prepared for a project’s next meeting to the people who were at the last one. From your own mail account, one message per person, never twice.
Prepare the next meeting from its minutes
This is the second half of Meeting Secretary. After each meeting, record the minutes with Turn a minutes file into project work. Before the next one, run this.
It starts from three things and asks you for only one of them:
- The last minutes you recorded for these projects — found by itself, and read again for what is still open.
- Current progress on the projects’ tasks — what people already recorded, so nobody reports it twice.
- New things — anything that has come up since, or that the last meeting missed. This is the one box you fill in, and changing it is how you change the direction of the next meeting.
What it prepares
Progress already covered by the project updates, what is still open since the last minutes, decisions that need the room, and what is new since last time. Coverage and omissions say what Recued could not prepare, including a project whose last minutes could not be read.
The briefing that is mailed
From that preparation, Recued writes the briefing the people in the meeting will read: tasks and projects by name, no Recued ids, plain text, in the meeting’s own language. Say how you want it under How to write it — another language, bullet points only, a formal tone, a length — and save it in this recipe’s settings to use it every time. It changes how the briefing reads, never what it says.
The briefing is kept with each project, so Mail the briefing can send it to the people who were at the last meeting. Keeping it is the only thing this writes, and nothing is sent: Mail the briefing asks you before anything leaves.
Federated projects
A selected federated project is included only when one of the people in the meeting matches exactly one active participant in it. Missing or ambiguous matches are reported under omissions instead of exposing that project’s tasks.
Inputs and limits
- Projects — up to eight. Required; save them in this recipe’s settings to use them every time.
- Meeting and When it starts — optional. Blank uses the name of the last minutes, and a briefing with no time says when it was prepared instead of inventing one.
- Who is in it — optional. Blank uses the attendees of the last minutes.
- New things — optional, plain text, used for this briefing.
- How to write it — optional: the language, layout, tone or length of the briefing that is mailed.
With no minutes recorded yet there is no activity window: every current row is in scope, which is right for a first meeting, and coverage says so. Task reads are capped at 50 per included project and report any remaining count.
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.
meeting at
setting
=
new things
setting
=
project refs
setting
=
[object Object]
meeting title
setting
=
attendee emails
setting
=
writing instructions
setting
=
Uses (8 operations)
core.storage.shared.read
core.storage.data-file-read
core.work-entity.get
recued-core.federated-projects.federation.search
recued-core.federated-projects.participant.search
core.work-entity.list
core.ai.extract
core.storage.shared.write
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.