← All templates

Meetings

Zoom Recording Distribution

A recorded call that nobody can find is the same as a call that was never recorded. This workflow takes the finished recording, files it somewhere with a sane name, creates the Notion page holding the summary and the decisions, tells the channel where it is, and reminds the host to write down the decisions while they are still remembered — because the recording is not the useful artefact, the decision list is.

6 stepsRequires Zapier Starter or higher20 minEasy
ZoomDropboxNotionTwistDelay by Zapier

What you get

Recordings are filed under a findable name instead of a meeting ID.
Every call gets a Notion page for decisions and actions.
People who missed the call are told where it is, not left to ask.

Workflow blueprint

ZO
When this happens
ZoomNew Recording
1DR
DropboxUpload File
2NO
NotionCreate Database Item
3TW
TwistSend Message to Thread
4DE
Delay by ZapierDelay For
5TW
TwistSend Direct Message

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 1 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Twist has no native n8n node, so that step arrives as an HTTP Request node with the endpoint left for you to fill in.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Detect the finished recording

Configure this step using the field mapping in the blueprint.

2
File it with a readable name

Configure this step using the field mapping in the blueprint.

3
Create the meeting page

Configure this step using the field mapping in the blueprint.

4
Post the link to the channel

Configure this step using the field mapping in the blueprint.

5
Prompt the host for decisions

Configure this step using the field mapping in the blueprint.

Implementation notes

  • Rename on upload. The single most common failure of meeting recording is a Dropbox folder full of identically named files that nobody can search.
  • Prompt for decisions after thirty minutes, not immediately. The host is usually walking into another call, and a prompt that arrives mid-call gets dismissed permanently.
  • The "not decided" heading earns its place. Deferred items with nothing recorded are the ones that get relitigated a fortnight later from scratch.
  • Otter, Fathom, Fireflies and Grain all produce better summaries than a raw transcript, and all have Zapier triggers if you would rather start there.