Calls

Zoom, Google Meet and Microsoft Teams calls on your events, and what comes back after them.

Peractor doesn't host video. It makes the call in the video service your organization already uses — Zoom, Google Meet or Microsoft Teams — on an organization or project event, shows Join on the event and its reminders, and after the call keeps its transcript (and, if your organization wants, its recording) in your project's files, where a workflow can write the notes.

Install a provider

An admin installs each provider once for the whole organization, in Settings ▸ Connectors ▸ Calls. Installing needs Manage connectors in Peractor, and the person consenting must be an admin of the provider's account:

• Zoom: Install opens Zoom, where your Zoom account's admin approves Peractor's app.
• Google Meet: your Google Workspace admin approves Peractor for the domain. Calls are made for people whose address is in that domain.
• Microsoft Teams: your Microsoft 365 admin consents for the tenant, and grants the app the access policy that lets it make meetings for your people (the page says how).

There are no personal connections: calls are always made in the organization's account. With more than one installed, mark one as the default; it is offered first. Uninstall stops new calls and keeps the settings for a reinstall; calls already made stay with the provider.

Add a call to an event

On an organization or project event, Add a call makes a meeting at the provider. The event's owner hosts it, matched by their email address; with no such user in the provider's account, Peractor says so and makes nothing — "You have no Zoom user in Acme's Zoom account. Ask an admin to add you." Anyone who can edit the event can add or remove its call.

Once added, the event shows the provider, Join, and two switches: Transcribe and Record, set from the integration's defaults. Moving the event moves the call; Remove call, or deleting the event, cancels it. A repeating event has one call for every occurrence. A personal event has no call. A link you paste into an event's description still shows Join, on any event; on an organization or project event, a pasted link from your organization's own account is also heard after the call, as if Peractor had made it.

Join

Join leads the event from fifteen minutes before it starts until it ends. Reminders carry it too: in the inbox, and on the phones as a Join action on the notification. Invitations a run sends to people outside the organization include the link, so their own calendar shows Join.

After the call

When the call is over, Peractor asks the provider what came of it — as soon as the provider says the call ended, and again over the next two days until everything the call was set to make is in. Each time somebody held the call, the event lists it under After the call: when it ran, who joined, its transcript and recording, and the runs it started. A call nobody joined isn't listed.

Each integration decides what is kept:

• Store transcripts (on by default) writes the transcript as Markdown into the event's project, at a path like meetings/{date} {title}/transcript.md.
• Store recordings (off by default) copies the video into the project too. Off, the event links to the provider's own recording.

The folder is the project's choice: Call transcripts go to and Call recordings go to in the project's Assets settings, its first Assets folder when it chose none. A folder kept in the project's repository or in git gets one commit per file. Recordings need a folder on object storage or git; Peractor's database holds no recordings. An organization event's files go to the shared project the integration names. When nothing can be kept — Assets are off, the folder is full or too small for the file — the event says why, and a transcript is still read from the provider while it keeps one. The integration's page shows where files will land before you turn a switch on.

Who may read what follows the files: the meeting is read by whoever reads the event, and a stored transcript by whoever can open its folder.

Notes, decisions and action items

An on: meeting trigger starts a workflow when a call ends, or when its transcript or recording is ready. The run gets the meeting and its transcript as files — never the provider's credentials. The Office work pack's Meeting notes workflow writes the notes, proposes the action items as tasks, and drafts the email to everyone who joined, each waiting for a person at its gate. A run's calendar step can ask for a call on the event it proposes; it is made when somebody approves the booking, hosted by them.

Calls from Chat

With a provider installed, Start a call in a Chat conversation's header makes a meeting starting now for an hour, hosted by you, and posts it in the conversation with Join. When the call is over, its transcript is kept as the integration's settings say, in the shared project it names, and the call's thread links it.

The assistant and MCP

The assistant can add a call to an event it proposes, and reads an event's meetings and transcripts when you ask about them. What people said in a call is something it reads, never instructions it follows. MCP tools read meetings and set up the integrations under the caller's permissions.