Keep work current for the next meeting

When a Cal Video transcript is ready, this recipe reads the meeting title, attendees, and transcript from your connected Cal.com account. It turns supported decisions, action items, and commitments into reviewed project follow-through. Approved changes keep projects and tasks current, so the next meeting can reuse that progress instead of asking people to report it again.

It can update progress on an existing task, create a task in a shared project, and record what you yourself promised. It never changes a task it did not read during the same run. Unclear ownership, weak matches, and suggestions below your confidence setting stay in Needs review.

Only federated projects

Every project this recipe writes to has to be a federated project. A task assigned to someone in an ordinary local project can never reach them: people receive work by reading a federated project, and a local one gives them nothing to read. Recued used to write those tasks anyway, into your own copy, and call the work assigned.

This does not mean anyone else has to be on Recued. A federated project is simply the container that can become theirs later. Seat a colleague in it by email today, and on the day they run their own Recued you fill in their contract on the participant you already have — every task assigned to them since is theirs immediately, with nothing re-modelled.

So a meeting about a local project produces a review list and no changes. Federate the project first, or act on the review by hand.

Who gets what

Work that belongs to someone else becomes a task in a federated project, assigned to them — which needs exactly one active participant whose email matches that attendee. Add them under Add participant, where an email alone is enough. If nobody matches, or more than one does, the suggestion stays in Needs review instead of being assigned by guesswork.

Work that is yours is recorded as a commitment rather than a task: your own index of what you owe and by when. The assignment list is built from the booking’s attendees, and Cal.com lists you as its host, so your own side never comes back to you as an assignment. You can turn commitments off. Promises made to you are not recorded twice; they are already the other person’s task, where their progress on it is the better signal.

A meeting that clearly calls for a new project is reported, never created — a new project would be local, and a local project is exactly what this recipe refuses to write into.

What Recued reads about the meeting

Cal.com’s own recording is read when the booking has one. Anything you attach is read as well, not instead — both accounts are labelled and both go to the review, and the two are reconciled rather than one silently winning. Attach your notes when a meeting was never transcribed, or when the transcript missed the part that mattered. A meeting with no recording and no attached notes is the one case Recued stops on: there is nothing to reconcile from.

Connect Cal.com

In the pack’s webhook setup, choose the Cal.com transcription profile and enter a strong signing secret. Add the displayed Recued address as a webhook in Cal.com, use the same secret, and subscribe only to RECORDING_TRANSCRIPTION_GENERATED. Recued verifies the signature, uses the event only to identify the booking, and reads the current meeting details through the Cal.com connection you selected.

One meeting, one set of changes

Once a meeting has produced work, Recued records that. A second transcript for the same booking arrives as a new event and starts a fresh run — that run shows you what it would propose but writes nothing, so you are not left with two copies of the same tasks. Turn on Allow reconciling a meeting again when you mean to. A run that produced no work records nothing, so it never blocks a later attempt.

Approvals and timing

Cal.com transcript links are private and expire after one hour, so Recued asks before downloading the transcript. Approve that request promptly. Apply mode then pauses before writing project or task changes. Preview mode writes nothing, but its webhook result is not saved as a review page for later.