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.
Record meeting minutes into project work
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.
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 “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.
Minutes that become the work
Write what the meeting decided, who took on what, and what is still open. Recued saves it as a note on the project, turns every action item into a task for the person it names, records what you took on yourself, and keeps what the next briefing needs.
Nothing outside Recued is involved: no calendar, no recording, no AI model, nothing to connect. What you write is read exactly as written, so the same minutes always produce the same result.
How to write the action items
One per line, in three parts separated by a vertical bar:
Send the revised quote | alice@example.com | 2026-10-03
- What needs doing becomes the task title.
- Who is the email of a participant in the project, or
mefor something you took on. - Due is a date like 2026-10-03, meaning by the end of that day. Leave it off if there is none.
Decisions and the items for next time are one per line as well. Bullets are fine; they are removed.
Who gets what
Work for someone else becomes a task in the project, assigned to them. That needs exactly one active participant in the project with that email. Add them under Add participant, where an email alone is enough and they do not need to be on Recued. When they run their own Recued, the tasks assigned to them are already theirs.
Work that is yours (me) is recorded as a promise in your own list, linked to the project, so it shows up in the next briefing and in Open commitments. Turn that off to keep it in the minutes only.
A line that cannot be written is never guessed at: an email that matches nobody, a date that is not understood, a missing owner. It stays in the minutes and is listed under Needs your attention with the reason.
Only federated projects
The project has to be a federated project, because a task assigned to someone in an ordinary local project can never reach them. A project run with Federated Projects is one, even when you are the only person in it.
Preview, then apply
Preview shows exactly what would be written and changes nothing. Apply saves the minutes as a note on the project and writes the tasks and promises, asking for approval first.
Correcting minutes
Minutes are filed by project, meeting name and date. Applying the same minutes again changes nothing. Applying a corrected version updates the same note and adds only what is new: a task already created is not created twice, and a promise already recorded is not recorded again. A task whose line you changed or removed is left as it is and listed, so you can close it on the board if it was dropped.
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.
notes
setting
=
decisions
setting
=
meeting at
setting
=
write mode
setting
=
preview
project ref
setting
=
[object Object]
action items
setting
=
carry forward
setting
=
meeting title
setting
=
[object Object]
attendee emails
setting
=
record promises
setting
=
true
Uses (9 operations)
core.work-entity.get
recued-core.federated-projects.federation.search
recued-core.federated-projects.participant.search
core.storage.shared.read
core.work-entity.note.create
core.work-entity.note.update
core.work-entity.task.create
core.work-entity.commitment.create
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.