Validate Buildkite access after Zoom user changes
Keep account changes from creating hidden access gaps.
Trigger
User Information Changed
Triggers when a Zoom user's information changes. Detects changes such as: - Profile information updates (name, email, display name) - Role or type changes - Department, job title, or location updates - Contact information changes (phone, timezone) - Status changes (active, inactive, pending) - Settings updates (language, pronouns, etc.)
Action
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Why this helps
Profile or role updates can coincide with operational ownership changes and missed credentials.
- Adds an access checkpoint to user changes
- Reports token validity and scopes
- Supports cleaner ownership transitions
Setup
Build it in a few focused steps.
- 1Connect Zoom and Buildkite once in Notis.
- 2Create a new automation and name it.
- 3Tell Notis to retrieve Buildkite token details and summarize access implications after a Zoom user change.
- 4Pick the Zoom User Information Changed trigger.
- 5Choose a report channel, then test with one real user update.
Questions about this workflow
Does this change Buildkite permissions?
No. It only retrieves the current token details.
Which Zoom changes count?
The selected trigger covers profile, role, department, contact, and status changes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zoom to Buildkite. A trigger fires from one place; an action lands in another.
Zoom triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
Daily Usage Report Changed
Triggers when the Zoom daily usage report changes for a selected year/month. This trigger monitors daily usage statistics including: - New users added - Number of meetings held - Participant counts - Meeting minutes consumed
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Meeting Details Changed
Triggers when a specific meeting's details change. Detects changes such as: - Meeting topic changes - Agenda updates - Schedule changes (timezone, duration) - Settings modifications (waiting room, recording, video, etc.) - Password changes - Recurrence pattern updates
Meeting Recording Changed
Triggers when a specific meeting's cloud recordings change. Detects changes such as: - New recording files appearing - Recording processing completion (status changes) - Recording metadata changes (count, size, etc.) - New participant audio files
Meeting Summary Created or Updated
Triggers when a meeting summary is created or updated for a specific meeting. IMPORTANT: This trigger requires a PAID Zoom account (Pro, Business, or Enterprise plan). Free Zoom accounts cannot use this feature. Additionally requires: - AI Companion feature enabled in account settings - Meeting must not be end-to-end encrypted (E2EE) - Meeting summary must be enabled and generated for the meeting
New Cloud Recording
Triggers when a new cloud recording meeting instance appears for a user.
New Meeting Created
Triggers when a new Zoom meeting is created for a user.
Connect any two apps with Notis in the middle.
Zoom and Buildkite, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Buildkite.