a zoom bot for finding what happened in the right session
**last week's workshop has the same title as today's.
it has a different attendance list.** a zoom bot can find the ended session, look up who attended and retrieve its summary when available. give the bot the host and session date. get the follow-up in dusk chat without mixing two workshops together.

what a bot can do in Zoom
keep the meeting id and the session identifier together. one recurring meeting can have several ended instances. each instance has its own uuid. use that identifier when attendance, notes or a recording need to match a particular date.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| List meetings | read | find upcoming scheduled workshops for the host |
| Get a meeting | read | read the time and settings for a chosen occurrence |
| List meeting registrants | read | count approved registrations for the upcoming workshop |
| List past meeting instances | read | find the ended instance on the workshop date |
| Get past meeting participants | read | read attendance for that specific instance |
| Get a meeting summary (Paid accounts only) | read | retrieve the available summary using the session uuid |
| Get meeting recordings | read | see which cloud recording files zoom returns for the session |
composio, the connection service behind dusk bot's apps, lists 111 Zoom actions (version 20261120_00, read 20 november 20263). dusk bot treats 60 as reads, 3 as sends and 48 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like create iq conversation comment, and waits for your Allow unless you set a daily amount.
connect Zoom
- open Connected apps in the sidebar.
- pick Zoom and sign in on Zoom's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Zoom.
- ask in plain words. reading and drafting happen freely; sending asks you first.
start with a workshop you hosted and a date you recognize. connect zoom for the host account and allow the listed reads. tell the bot your time zone and meeting series. ask which ended instance it found before relying on the attendance list.
routines to copy
build each run around one occurrence. name your workshop series in chat. the prep list uses the upcoming occurrence. the two follow-ups start by finding the ended one.
host's prep list
each monday at 8, find my scheduled workshops for this week matching <series title>. list each start time in my zone and its approved registrant count. read all registrant pages for that occurrence. omit join links and passcodes.mondays at 08:00 · workshop times and expected turnout for the host
attendance after class
every thursday at 5, find the ended instance of my workshop from today. read its participants by instance uuid. show names here, flag repeat entries and leave uncertain matches separate. if it hasn't ended, say so. never use last week's attendance.thursdays at 17:00 · an attendance sheet tied to a specific class
materials for the recap
on fridays at 10, look up this week's ended workshop. read its available zoom summary and cloud recording inventory. pull any promised follow-up materials from the summary. list the recording file types available. if either source is missing, label the gap. keep download links out of the recap.fridays at 10:00 · promised materials and recording availability for the organizer
what it asks you first
give the bot read access for host reports. it can retrieve details without changing the meeting. a schedule update or deletion is a write, outside send approval. if you let a scheduling bot edit meetings, put “ask me before you change anything” in its routine.
what it cannot do
- produce zoom's summary for an ineligible session. the host needs a paid plan and the relevant ai companion setting. end-to-end encrypted meetings don't support summaries.
- pull attendance for any meeting ever held. the participant action needs a pro or higher account and covers the last 15 months. single-person meetings are excluded by default.
- recover a local recording through the cloud inventory. an empty result means the lookup returned no cloud files. confirm the host account and session before declaring a recording lost.
when you need someone in the call
use another tool if you need a live meeting participant. these zoom actions retrieve meeting records. there is no join-and-listen action here. for an ended call, ask for promises the available summary actually contains and have the host confirm any owner it leaves unnamed.
what it looks like
an example from a recurring workshop.
before
rosalie hosted the same workshop on 4 and 11 june. the follow-up concerns the earlier class. the meeting id is the same.after the bot
4 june instance selected. use its participant list.
materials promised in this summary: the worksheet. keep the 11 june recap separate.an illustration with made-up names and numbers.
questions
why did i get attendance for the wrong week?
a meeting id can select the latest instance. resolve the date to an instance uuid and use that for the participant lookup.
does a registration count tell me how many people attended?
registration counts signups. after the meeting, use its participant records for attendance. someone can register and never join.
sources
- dusk bot docs: connected apps
- dusk bot docs: routines
- composio, Zoom toolkit (catalog version 20261120_00), checked 20 november 2026
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
turn meeting notes into a decision log
a calendly bot that brings the booking details to the call
a calendar bot that finds you room to think
add new airtable rows without rewriting existing records
turn a calendly booking into an opening question
meeting prep briefs for outside calls, every weekday at 8