The moment it happens
Post Zoom's meeting summary to Slack
The summary Zoom AI Companion writes is shared in your channel when it's ready.
- Runs
- The moment it happens
- Apps
- Zoom
- AI
- Not needed
- Access
- meeting_summary:read
Send this to your assistant
Create a ClickRuntime automation: when Zoom finishes its AI meeting summary, post it to #meetings in Slack with the meeting topic.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Zoom AI Companion can write a summary of a meeting, but it lives in the Zoom web portal or in an email to the host. People who were not the host, or did not attend, never see it. A team lead who wants the recap in the team channel must open Zoom, copy the text and paste it into Slack. That chore gets skipped, and the summary that took no effort to produce reaches nobody.
When Zoom announces that a meeting summary is ready, the event arrives at the trigger link. The summary is fetched from Zoom, and a post goes to Slack with the overview and next steps. No transcript processing is needed because Zoom has already written it.
For teams that already have AI Companion turned on and want the output shared.
What you get out of it
Summaries reach the whole team
Posting to a channel means people who missed the call read what happened. Information is no longer limited to the host's inbox, so the whole team starts from the same understanding.
No copy and paste
Nobody moves text between Zoom and Slack by hand. The recap arrives when it is ready, so sharing no longer depends on someone remembering after a long day of calls.
Next steps are in front of everyone
Having next steps in a shared channel makes ownership visible. People follow through more reliably when their commitments can be seen by teammates, not left in a private email. Everyone can see commitments.
Searchable meeting history
Slack search finds past summaries by keyword. Finding what was said about a customer last month takes seconds, not a hunt through recordings and calendar invites. Search beats scrolling through old threads and invites.
Value from a feature already paid for
If your plan includes AI Companion, sharing its output makes the feature useful across the company, not only to the host. The summaries get read because they arrive where people already work.
Consistent meeting records
Every summary lands in the same place in the same format. Over time, the channel becomes a lightweight meeting archive for the team. The channel doubles as a lightweight archive that teammates can search any time.
How it works
What happens, step by step
When Zoom AI Companion finishes the summary of a meeting, Zoom tells ClickRuntime straight away.
The automation fetches that summary from Zoom.
It posts the meeting topic, the overview and the list of next steps to your #meetings Slack channel.
Before it runs live
- Connect Zoom
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Zoom steps into one automation
Under the hood
The code that runs this automation
from urllib.parse import quote
from clickruntime import on_event, credentials, http, notify
@on_event
def handle(event):
if event.json.get("event") != "meeting.summary_completed":
return {"skipped": True}
meeting = event.json["payload"]["object"]
uuid = quote(quote(meeting["meeting_uuid"], safe=""), safe="")
resp = http.get(f"https://api.zoom.us/v2/meetings/{uuid}/meeting_summary",
headers={"Authorization": f"Bearer {credentials.connection('zoom', 'work')}"})
resp.raise_for_status()
s = resp.json()
steps = "\n".join(f"• {n}" for n in s.get("next_steps", []))
notify.slack(f"*{s['meeting_topic']}*\n{s.get('summary_overview', '')}\n\nNext steps:\n{steps}",
channel="#meetings")
return {"posted": s["meeting_topic"]}FAQ
Common questions
Do I need Zoom AI Companion enabled?
Can the summary go to different channels by meeting?
How is this different from the transcript-based summary?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Hear in Slack when someone joins or waits
You're pinged when a participant joins your meeting or is sitting in the waiting room.
See how it worksGet an attendance list when a meeting ends
When your meeting ends you get who attended and how long each person stayed.
See how it worksTrack webinar sign-ups as they happen
Each new registrant reaches you with their details and the running total.
See how it worksKeep exploring
Set up “Post Zoom's meeting summary to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.