Automation library · Scheduling

Automated meeting attendance tagging for Zoom Webinars

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 25 steps, 7 branches, 1 loop or waits: large, and worth reading before you trust it with anything live.

Large

Download free
25 stepsLarge: read it before trusting it with anything live
7Branches: places the flow splits
1Loop or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 3Logic 13Service 9

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

  1. 1Listen to ending Zoom webinarsWebhookStarts it
  2. 2URL Validation checkIfLogic
  3. 3CryptoCryptoService
  4. 4Build Normal Event BodySetLogic
  5. 5Build Validation BodySetLogic
  6. 6Respond to Webhook (Events)Respond To WebhookStarts it
  7. 7Respond to Webhook (Validation)Respond To WebhookStarts it
  8. 8Wait 1 secondWaitLogic
  9. 9Get past Zoom webinar absenteesHttp RequestService
  10. 10Get past Zoom webinar participantsHttp RequestService
  11. 11Split webinar absenteesSplit OutLogic
  12. 12Split webinar participantsSplit OutLogic
  13. 13Route by meeting name1SwitchLogic
  14. 14Filter internal usersFilterLogic
  15. 15Tag absentee for non attendanceKlicktippService
  16. 16Tag absentee for non attendance1KlicktippService
  17. 17Route by webinar nameSwitchLogic
  18. 18Check full attendanceIfLogic
  19. 19Check full attendance1IfLogic
  20. 20Tag participant for full attendanceKlicktippService
  21. 21Check general attendanceIfLogic
  22. 22Tag participant with full attendance1KlicktippService
  23. 23Check general attendance1IfLogic
  24. 24Tag participant for general attendanceKlicktippService
  25. 25Tag participant for general attendance1KlicktippService

How it's built

Starts on
Another system calling it
Steps
25, with 7 branches, 1 loop or waits
Size
Large: read it before trusting it with anything live
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n 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?

Take your time. At 25 steps it is large: read it before trusting it with anything live.

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 25 steps before you point it at anything that matters.