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.
Mail the briefing before the meeting
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.
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 “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.
Send the briefing before the meeting
After Prepare the next meeting from its minutes has run, this sends the briefing it kept to the people who were at the last meeting.
One message each
Everyone gets their own message, from your own mail account; your own address is left out and counted as "not sent to yourself". The same message never goes to anyone twice; a changed one — a new note, the time corrected, the briefing prepared again — is a new message.
When the meeting is
Briefings are usually prepared the working day before, so say when the meeting is under When and where — "Monday 09:00, site office", "tomorrow 07:30 at the front desk". Leave it blank and the time you gave the briefing is used; if you gave none, the message states no time rather than inventing one. Add a Note for reminders; it goes in as written, for this send only.
Your own words, in your own language
The Subject and the Message are yours to rewrite — another language, another greeting, another order. {meeting}, {when}, {note} and {briefing} are filled in; a line with {when} or {note} is left out when that one is blank, and in the subject a blank {when} goes together with the " — " in front of it. Save them in this recipe's settings to use them every time. The briefing itself is written the way you asked when it was prepared, under How to write it.
Preview first
Preview shows who would receive it and sends nothing. Send asks for approval before anything leaves.
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.
note
setting
=
message
setting
=
Hello,
{note}
Here is the briefing for {meeting}.
When: {when}
{briefing}
send to
setting
=
subject
setting
=
Briefing: {meeting} — {when}
write mode
setting
=
preview
project ref
setting
=
[object Object]
meeting when
setting
=
sender mail instance
setting
=
[object Object]
Uses (3 operations)
core.work-entity.get
core.storage.shared.read
core.mail.send
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.