Connect Zoom

Zoom in Exabloom is a push-only, action-side integration. Nothing flows from Zoom into Exabloom — no calendar sync, no attendance data, no triggers. It works the other direction: your workflows reach into a connected Zoom account and create, change and cancel meetings on it.

Two facts about ownership explain almost every question people have about it.

First, the connection is personal. The Zoom card in Settings shows only your accounts, and you can hold several — your own work account and a shared one like hello@yourcompany.com. Your colleague’s accounts never appear on your card. This is the opposite of Calendly, which is one shared account for the whole workspace.

Second, the host pool is shared. Every account connected by anyone in the workspace lands in one list, and a workflow step picks its meeting host from that list. That’s what lets one person build the automation while someone else hosts the calls.

The third thing worth knowing up front: the meeting is created the instant the step runs, not on the day it happens. So the join link already exists by the time the next step in your workflow fires — which is exactly why you can confirm a booking over WhatsApp, with the link, seconds after someone says yes.

Three things, and none of them is a paid upgrade:

• A Zoom account you can sign into. Any type works, including Zoom Basic (free). Zoom’s own plan limits still apply to the meetings themselves — a free account cuts group meetings short, so host longer calls on a licensed account.
• Access to Settings → Integrations in Exabloom. Connecting is a personal action, not an admin one — each person connects their own accounts from their own login. If you can’t see the Settings area, ask an admin to grant it (see Roles & permissions).
• Somewhere for the meeting time to come from. The Schedule step needs a start time. That’s usually a date/time field holding the slot your AI agent confirmed, or a fixed date you pick by hand. If you have neither yet, build that part first — the Zoom step is the easy half.

Adding the integration takes about a minute and happens entirely inside Exabloom — there’s nothing to install in Zoom first.

Something not going to plan? Jump to Troubleshooting & pitfalls — it covers blocked popups, the “Something went wrong” screen, and the workspace-approval case.

The Zoom consent screen lists the permissions in Zoom’s own language. Here’s what each one is actually for, and — just as usefully — what the integration never gets near.

Exabloom never sees your Zoom password: you sign in on Zoom’s own page and Exabloom receives only an access token, which is stored encrypted and renewed automatically in the background. Access tokens are short-lived by design — roughly an hour — and Exabloom refreshes them shortly before they expire, so you should never need to reconnect just because time has passed.

Once an account is connected, three new actions appear in the workflow builder’s action drawer, grouped under ZOOM. Add them the same way as any other action: open a workflow, click the + on the branch where you want the step, and pick one.

Schedule Zoom meeting — book the call

This is the step that does the work. It creates a real meeting on the host’s Zoom account at the time you give it, and hands the join link to the rest of the workflow.

• Host. Which connected account the meeting is created on. The list shows every account in the workspace as staff name — Zoom email; an account that needs attention is marked (reconnect needed) but stays selectable, so a saved workflow never loses its setting.
• Topic. The meeting title as it appears in Zoom. Insert fields with the { } picker — e.g. Consultation with {{contact.name}}.
• Start date & time. There’s no free typing here on purpose. In dynamic mode you pick a field, and only date & time fields are offered — normally the slot your AI agent confirmed and saved. Switch to static to choose a fixed date on a calendar instead.
• Duration. 15, 30, 45, 60 or 90 minutes, or Custom… for anything else. Defaults to 30.
• Timezone. Defaults to your workspace timezone. Set it explicitly when the slot was captured somewhere else — this is the single most common cause of a meeting landing an hour or eight out.
• Agenda. Optional description carried into the Zoom meeting. Accepts fields too.

Waiting room, passcode requirements and join-before-host all follow the host’s own Zoom settings. Exabloom doesn’t re-model Zoom’s settings screen, so change those in Zoom if you want different behaviour.

Update Zoom meeting — the reschedule

Moves or edits a meeting an earlier step created. The important property: the join link doesn’t change, so the link the contact already has keeps working. Send them the new time, not a new link.

• Meeting. Insert the meeting_id chip from the Schedule step. This field is required.
• New start date & time, topic, duration. All optional — leave any of them unset to keep the meeting’s current value. An Update step that only changes the time is perfectly normal.
• No Host field. You don’t choose one. Exabloom works out which connected account owns that meeting and uses it.
• No Timezone field either. A new start time is read in your workspace timezone, so make sure the field feeding it already holds a time in that timezone.

Cancel Zoom meeting — call it off

Deletes the meeting from the host’s Zoom account. It needs the same meeting_id chip and nothing else. Pair it with a WhatsApp message so the contact learns about it from you rather than from a dead link.

Schedule Zoom meeting and Update Zoom meeting publish their results as chips you can insert into any later step with the { } picker - into a WhatsApp message, into a contact field, into a webhook. (Cancel Zoom meeting hands nothing on.) The list below shows each chip’s picker label, then its key.

start_time is already formatted in local time and reads naturally in a message — and the same value saves cleanly into a date field, so you don’t need to convert anything.

The chip beside the Zoom heading summarises your card; each account row then shows its own state.

• Not connected. You haven’t authorized any Zoom account yet. Click Connect. Teammates’ accounts don’t show on your card.
• 2 accounts connected. Every account on your card is authorized and usable as a host. Nothing to do: access tokens renew themselves in the background.
• Reconnect needed. At least one account’s authorization stopped working - removed in Zoom, revoked, or expired. Steps using it as host are failing. The card only flips to this the next time a workflow step tries to use that account, so an idle account can look healthy until then.

Reconnecting is the same flow as connecting, and it’s non-destructive: because Exabloom recognises the Zoom account you’re re-authorizing, it refreshes the existing entry rather than adding a duplicate. Workflows that referenced that host keep working untouched — there’s nothing to re-select.

Four patterns that cover most of what businesses actually build with this.

You can remove the integration from either side, and both routes end in the same place: the authorization is revoked and Exabloom’s stored record of it is deleted.

Remove it from Exabloom

Remove it from Zoom

What removal does — and what it doesn’t

• The authorization stops working immediately. Exabloom can no longer create, change or cancel meetings on that Zoom account.
• Your stored authorization is deleted. The connection record and its encrypted tokens are removed from Exabloom. Disconnecting inside Exabloom also revokes the token with Zoom, so the app disappears from your Zoom authorized apps without a second visit.
• Meetings already booked are not deleted. They remain in Zoom exactly as they are and the links your contacts hold keep working. If you want them gone, cancel them in Zoom — or run a Cancel Zoom meeting step before you disconnect.
• Your workflows are not deleted. Steps that named that account as host will fail with a clear message until you pick a different host or reconnect. Nothing is silently skipped.
• Other people’s connections are unaffected. Connections are personal, so removing yours leaves colleagues’ accounts in the host pool untouched — even if they connected the same shared Zoom account.
• Nothing else about your Exabloom workspace changes. Contacts, conversations, leads and every non-Zoom workflow carry on as before. Exabloom holds no Zoom data beyond the connection record and the meeting details recorded in your workflow logs.

For how Exabloom handles personal data generally, see our Privacy Policy.

Symptom on the left, what to do on the right. Workflow step failures always surface in the workflow’s Logs tab with the exact message quoted below.

Good to know

• Your card shows your accounts only. A colleague’s connection will never appear there — but it is in the workflow step’s host list. An empty card doesn’t mean an empty host pool.
• Only Published workflows run. A draft containing a perfectly configured Zoom step does nothing. Publish it, then run a test.
• Re-authorizing is safe. Connecting an account you already hold refreshes it rather than creating a duplicate — so “just reconnect” is almost always a safe first move.
• Update and Cancel need the meeting_id chip. They act on a meeting an earlier step created; they can’t find a meeting by contact name or by date.
• Timezone beats guesswork. Leaving Timezone on the workspace default is right most of the time — and wrong in exactly the cases that hurt, like an overseas lead. Set it explicitly when in doubt.
• A burst of runs won’t break things. If many workflows book meetings at once and Zoom rate-limits the requests, Exabloom backs off and retries automatically before giving up.
• Disconnecting doesn’t clean up Zoom. Meetings already on the calendar survive. Cancel them first if you want a clean slate.

Our team is based in Singapore and answers on whichever channel suits you.

Prefer to read first? The Exabloom Help Center carries guides for every part of the product, and Troubleshooting & pitfalls above resolves most Zoom questions without needing us at all.