Enable & connect

For a first-time setup, open Settings > PRO, find the Integrations card, choose Turn on, then choose Open Integrations. Returning users can use the Automation API switch at the top of Settings > Integrations. Turning it off closes the ports and stops every assistant and key, but recording, transcription, and summarization keep running.

Below the collapsed Apps & scripts header, use Allow the CLI on this computer. The underlying auto-created credential remains named loopback, is Meetily-owned, has Read-only access, and can be used only from this computer.

For a script or app of your own, click + Create key in Apps & scripts. Give it a name and choose what it may do:

• Read is always on - it can access full meeting content, including transcripts, summaries, search results, and exports, as well as notifications. Grant it only to a client you trust with that content.
• Record lets it start, stop, pause, and resume recording; it also includes Read. Starting from another machine requires the host to pre-arm remote recording.
• Write lets it change configuration, create and manage jobs, and run imports. On hosted (paid) processing this can cost real money.
• Delete (off by default) lets a computer-only key delete meetings. Deleting their stored audio/video files is a separate opt-in; network-reach keys and paired devices cannot hold Delete.

More options sets the key's reach (this computer, or network) and expiry (90 days, 30 days, or never).

Copy the secret now - Meetily shows the raw value once. The dialog includes a ready-to-run curl you can paste to test it. The screenshot below redacts the secret for documentation. Then turn on Allow for the new key too (it also starts "Not allowed yet").

To have Meetily deliver webhooks, expand Advanced and turn on Outgoing (webhooks). To deliver to a receiver on this machine or network (such as a local script, n8n, or Node-RED), add its host:port under Local targets. Additions and removals apply immediately; removing a target prevents later retries to it.

After a key registers a webhook, Meetily shows a "Waiting for you" banner at the top of the Integrations tab, for example: "New secret key wants to send meeting events to http://127.0.0.1:8787. Event notices only, never content." with Allow / Don't allow. Approve it there, or later under Advanced > Destinations, so its approval_state becomes allowed - only allowed delivers. A destination left pending fails silently: no error, nothing delivered.

To connect an AI assistant, make sure the Automation API is on, then open AI Assistants (MCP) and choose Connect beside a detected client. In the permission sheet, Read is always included; Record, Write, and Delete are optional. Choose Connect to add Meetily to that assistant's configuration.

An assistant may send the meeting content it reads to its own AI provider. See the MCP server privacy note before connecting one.

A new connection starts disabled. Turn on its Allow switch, then restart the assistant so it loads the new server configuration.

See MCP server for the tools and data it exposes.

To pair another machine, turn on Advanced > Incoming (LAN) and choose Pair a device in Apps & scripts. Follow Pairing & remote access to verify the host fingerprint, approve the request, and allow the paired device before making calls.

Meetily requests the operating system's microphone and screen-recording permissions during its onboarding (first run), not from this Integrations screen. If you skipped them, grant them later from your OS Privacy settings. Recording needs both.