Enable & connect

Open Settings > Integrations, expand Advanced, and turn on the Automation API master switch. Then restart Meetily so the change takes effect. This is the one switch: turning it off later closes the ports and stops every assistant and key, but recording, transcription, and summarization keep running.

Under Apps & scripts, Meetily lists an auto-created key named loopback ("Meetily's own", Read). It is what the meetily-pro CLI on this computer uses, and it starts Not allowed yet. Turn on its Allow toggle so the CLI can connect.

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 sees meetings and notifications (titles, timestamps, events), nothing more.
• Record lets it start and stop recording, nothing else.
• 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 it remove meetings, recordings, and jobs it created; deleting the underlying audio/video files is a separate, opt-in permission.

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 it once. The dialog includes a ready-to-run curl you can paste to test it. 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 the Webhook delivery door. To deliver to a receiver on this machine (a local script, n8n, Node-RED), add its host:port under Local targets, then restart Meetily - that allowlist is read once at startup.

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 Destinations) so its approval_state becomes allowed - only allowed delivers. A destination left pending fails silently: no error, nothing delivered.

To let an AI assistant drive Meetily, use the AI assistants (MCP) section: click Connect next to Claude Desktop, Claude Code, Cursor, or another detected client. Meetily mints a scoped, read-only-by-default token for that client and writes its config. See MCP server for what it exposes.

To reach Meetily from another machine, use Pair a device in Apps & scripts (the My network door, LAN https port 8421, opens automatically while the pairing window is open). The panel shows the LAN address, a one-time pairing code, and the exact command to run on the other computer; completing it within the ~10-minute window mints a 90-day network token. Full flow and TLS pinning: Pairing & remote access.

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.