Automation library · Content

Archive Zoom cloud recordings to Google Drive

Started by another system calling it, and works across Slack. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 2Logic 4Service 4

The steps in the order they run, from what starts it.

  1. 1Zoom recording.completedWebhookStarts it
  2. 2Verify Zoom signatureCodeLogic
  3. 3Respond to ZoomRespond To WebhookStarts it
  4. 4Recording event? (not the handshake)IfLogic
  5. 5SettingsCodeLogic
  6. 6Pick MP4 and build filenameCodeLogic
  7. 7Download recording from ZoomHttp RequestService
  8. 8Start Drive uploadHttp RequestService
  9. 9Upload file to DriveHttp RequestService
  10. 10Post link to SlackSlackService

How it's built

Starts on
Another system calling it
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Slack account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 10 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.