Zoom Integration — A Zoom Meeting for Every Booking

Zoom integration gives every meeting booked through Personyze its own Zoom meeting, created in the
host’s own Zoom account, with the join link sent to the visitor.

What it does

Personyze Meetings lets visitors book a time with your team from your website — a booking page, a pop-up, or the
AI assistant. With Zoom connected for a host:

Every booking with that host creates a scheduled Zoom meeting in the host’s own Zoom account, in the host’s time zone. The host finds it in Zoom like any other meeting.
The visitor gets the Zoom join link in the booking confirmation email (“Join here”), in the calendar invite, and as a Join the meeting button on their booking page.
When the visitor cancels or reschedules, Personyze deletes that Zoom meeting, so the old link stops working. A reschedule gets a new meeting and a new link.

Zoom only creates the meeting. It does not tell Personyze when a host is busy — Zoom has no free/busy information. To avoid double-booking, also connect the host’s Google Calendar on the same page — see Connecting a host’s calendar.

What you need

A Zoom account for each host who should get Zoom meetings (any Zoom plan; a free Zoom account limits meetings to Zoom’s own free-plan length).
Personyze Meetings, with the host added under Meetings → Hosts.
A meeting type set to Zoom: in Meetings → Meeting types, open the type and choose Zoom under Where.

Add the app: connect a host’s Zoom

Each host connects their own Zoom account. It takes a minute, once per host.

In Personyze, go to Meetings → Hosts.
In the host’s row, click Connect Zoom.
Zoom opens and asks the host to sign in (if they are not already) and to allow Personyze. Sign in with the Zoom account the host uses for their meetings — a personal Zoom account instead of the company one is the most common mistake.
Click Allow. Zoom sends you back to the Hosts page, which says Zoom connected., and the host’s Zoom cell reads connected.

Meetings → Hosts in Personyze, with Connect Zoom in each host’s Zoom column — **Meetings → Hosts**: each host’s Zoom cell offers **Connect Zoom** until that host has connected. Click to enlarge.

The host does not need a Personyze login to be connected: whoever manages Meetings in Personyze can click Connect Zoom and let the host sign in to Zoom on that screen.

Or start from the Zoom App Marketplace

Personyze is also listed on the Zoom App Marketplace. Click Add there, sign in to Personyze, and you land on Meetings → Hosts. Then click Connect Zoom in the host’s row, as in step 2 above. The Zoom card in Integrations leads to the same page, and shows how many hosts have connected.

What Personyze asks Zoom for, and why

On Zoom’s screen the host allows three permissions. Personyze uses each only for this:

Permission	Used for
Create a meeting for a user (`meeting:write:meeting`)	Creating the Zoom meeting for each booking with this host
Delete a meeting (`meeting:delete:meeting`)	Deleting that meeting when the booking is cancelled or moved. Personyze only ever deletes meetings it created
View a user (`user:read:user`)	Reading the host’s own Zoom email (shown in Personyze, so you can see which Zoom account is connected) and Zoom user ID (so the connection can be deleted when the host removes the app in Zoom)

Personyze does not read the host’s recordings, chats, contacts, or any meetings it did not create.

All three are needed. If Zoom does not grant all three (for example, an unticked permission), Personyze refuses the connection and says which permission is missing — without delete, a cancelled booking would leave a working Zoom link behind. Connect again and allow every permission.

Use it

Nothing more to do. From now on every booking with a connected host, for a meeting type set to Zoom, gets its Zoom meeting automatically:

Booked — the meeting is created in the host’s Zoom, scheduled for the booked time and length, and the visitor receives the link. The meeting is set so the visitor can join before the host, without a waiting room, with computer audio and phone dial-in both available.
Cancelled — the Zoom meeting is deleted.
Rescheduled — the old meeting is deleted and a new one is created; the visitor receives the new link.

If the host also has a calendar connected, the Zoom link is put in the calendar event too, so the host can join from their calendar.

Remove the app: disconnect a host’s Zoom

Either of these disconnects a host:

In Personyze: Meetings → Hosts, the host’s Zoom cell, Disconnect. Personyze also tells Zoom to withdraw its access.
In Zoom: the host signs in at marketplace.zoom.us, opens Manage → Added Apps, and removes Personyze.

After disconnecting:

New bookings with that host no longer get a Zoom meeting.
Meetings already booked keep their Zoom meetings and links — they stay in the host’s Zoom.
Personyze can no longer delete those meetings if such a booking is later cancelled — delete it in Zoom yourself.

What happens to the host’s data

What Personyze stores for a connected host:

The access granted by Zoom (OAuth tokens) — stored encrypted.
The host’s Zoom email address and Zoom user ID.
For each booking: the Zoom meeting’s ID and join link, kept with the booking.

When the host disconnects in Personyze, or removes Personyze in Zoom, Personyze deletes the tokens, the email and the Zoom user ID straight away. The meeting ID and link stay on bookings already made, as part of your booking records.

See the Personyze Privacy Policy for how personal data is handled and how to exercise data rights.

One Zoom app for every host

Instead of each host connecting, an admin of your company’s Zoom account can create one Server-to-Server OAuth app, and every host gets Zoom meetings at once — nobody authorises anything, and there is no grant that can quietly expire.

In the Zoom App Marketplace, signed in as an account owner or admin, choose Develop → Build App → Server-to-Server OAuth.
Fill in Basic Information — the company name, the developer name and the contact email. Zoom will not activate the app without them.
On Scopes, add meeting:write:meeting and user:read:user, then activate the app.
In Personyze, open Meetings → Connections, click Change beside Zoom, enter the Account ID, Client ID and Client Secret, and click Save and test. Personyze says when Zoom accepted it; every host can get Zoom links from then on.

Whose Zoom the rooms are made in: the Zoom user

With one app for the account, each host’s room is made as a named user inside your Zoom account — by default, the user with the host’s own email address. When a host’s Zoom user is not the address they take bookings at (a team sharing one licensed seat, for example), set it: on Meetings → Hosts, click the address in the host’s Zoom cell (their own address until you set one; Set a Zoom user when there is none) and type the Zoom user’s email. Leave it empty to use their own address. It changes nothing else: the calendar invitation, the reply-to and the host’s own copy all keep using their email.

The Zoom user is saved at once — inside a Meetings campaign too, not with the campaign’s Save — and Zoom is asked again straight away, so the row can say whether it worked.

What the Hosts screen says about each host

The Zoom cell reads	The line under it	What it means
rooms on	Rooms are made as <address>, their own address. — or Rooms are made as <address>. for a Zoom user you set	Bookings get a Zoom room.
basic seat	Rooms are made as <address>, a Basic Zoom seat – those meetings stop at 40 minutes.	Rooms are made, and Zoom ends them at 40 minutes. Set a Zoom user on a licensed seat.
no rooms	In red: Zoom has no user <address>, so bookings get no link. Set a Zoom user that exists in your Zoom account.	Zoom cannot make rooms for this host. Correct the Zoom user just below the line.
on for everyone	—	Zoom could not be asked about this host just now; the account’s app covers everybody.

When a recent booking with the host got no room, the cell also says, in red, A recent booking got no room; point at it for Zoom’s reason.

Good to know

One Zoom account for the whole company instead? A Server-to-Server app under Meetings → Connections gives every host Zoom meetings at once, with nothing for any host to connect — see One Zoom app for every host.
Zoom does not block busy times. Connect a calendar too, or a host connected only to Zoom can be booked over other appointments.
Data residency: if your Zoom account keeps data in a specific region, Personyze sends its requests to that region’s Zoom servers.

Troubleshooting

“Connect Zoom” shows a message instead of Zoom’s screen.
If it says no Zoom app is set up, contact Personyze support. If it says Zoom is already set up for the account, a Server-to-Server app is in place under Meetings → Connections and hosts need not connect anything.

The connection is refused, naming a missing permission.
Click Connect Zoom again and allow every permission on Zoom’s screen.

The host’s Zoom cell shows Connect Zoom again, or says “needs attention”.
Zoom no longer accepts the connection — usually because the host removed Personyze in Zoom. Click Connect Zoom (or Reconnect) and allow Personyze again.

The host’s Zoom cell says “no rooms”.
Zoom has no user with the address the rooms are made as. Set a Zoom user that exists in your Zoom account — see What the Hosts screen says.

A booking has no Zoom link.
Check that the meeting type’s Where is Zoom and that the host’s Zoom cell reads connected. If Zoom refused to create the meeting, the booking shows No joining link under Meetings → Bookings — point at it to see Zoom’s reason.

Personyze on the Zoom App Marketplace — the app’s listing at Zoom.
Book a meeting — the booker itself: hosts, meeting types, availability and the booking page.
Connecting a host’s calendar — busy times, and every booking on the host’s Google Calendar.