Natively integrations and connectors

How notes move from a call to your other tools

Natively has no bot in the meeting, and your meetings are not kept on a Natively server unless you publish one as a share link. It hears the call through your computer's microphone and system audio, writes the transcript and notes, and saves them in a local database. Connectors are the doors out of that database. Each one has to be connected by you in Settings, and each one sends something specific: a Slack message, a Notion page, a note on a CRM contact, an email, or a JSON request to an address you control.

Calendars

A connected calendar lets Natively name each meeting after its event, show your next meetings in the Launcher, and know who was invited. The invitee list matters for more than the title: it gives the notes real names, and it is how the CRM connectors find the right contacts. Calendars are set up in Settings > Calendar, and every source only reads.

Natively never creates, edits or deletes calendar events. When it writes notes, the event's title, time and invitees are part of what the notes model is given, so with a cloud AI provider that information goes to the provider together with the transcript.

Email and workspace: Gmail, Slack, Notion

Gmail is called directly from your computer, using Google's sign-in for desktop apps, and the tokens are kept in an encrypted file on your machine, so mail never passes through Natively's servers. You can also skip the connector entirely: the follow-up email can open as a draft in your computer's own mail app, such as Mail or Outlook.

CRMs: HubSpot, Salesforce, Attio, Pipedrive, Affinity

The CRM connectors log a meeting on the people you met. Natively takes the invitee emails from the calendar event (leaving out your own address and room calendars), looks each one up in the CRM, and writes the notes only to records that match. When you send from a meeting's Share menu, you see who matched before anything is written. Nobody new is created, and fields, deal stages and pipelines are left alone.

Matching only works when the meeting is linked to a calendar event with invitee emails. A call started without a calendar event has nobody to match, so an automatic rule skips it rather than failing. Pasted Salesforce access tokens expire; when one stops working, paste a fresh one or use the sign-in instead.

Clearbit sits with the CRMs but works the other way round: it looks attendees up rather than writing to them. With a Clearbit key saved, pressing Look up attendees on a meeting sends the attendees' email addresses to Clearbit and returns a job title and company for each. Every result is a suggestion on the People page that you accept or ignore, and nothing is looked up in the background.

Zapier and webhooks

For any tool without its own connector, add a webhook. When a meeting's notes are ready, or a minute after you finish editing them, Natively sends a POST request with the notes to the HTTPS address you entered. A Zapier connector is the same mechanism with a guard: the address must come from a Catch Hook step in Webhooks by Zapier. You can add up to 20 endpoints, limit each one to a folder of meetings, and choose whether it gets the transcript.

{
  "type": "note.generated",
  "timestamp": "2026-10-31T15:04:05.000Z",
  "data": {
    "meeting_id": "…",
    "title": "Weekly pipeline review",
    "date": "2026-10-31T14:00:00.000Z",
    "duration": "32:10",
    "attendees": [{ "email": "dana@example.com", "name": "Dana" }],
    "summary_markdown": "…",
    "sections": [{ "heading": "Decisions", "bullets": ["…"] }],
    "action_items": [{ "text": "…", "owner": "Dana", "done": false }],
    "transcript": [{ "speaker": "Dana", "text": "…", "offset_ms": 0 }]
  }
}

• Events: note.generated when notes are ready and note.edited after you change them. Pick one or both per endpoint.
• Signature: each request carries webhook-id, webhook-timestamp and webhook-signature headers in the Standard Webhooks format, an HMAC-SHA256 under the endpoint's whsec_ secret, so your receiver can reject anything Natively did not send.
• Transcript: included only if you turn it on for that endpoint.
• Retries: a failed delivery is tried again after 30 seconds and after 2 minutes, then the row in Settings says what went wrong.
• Timing: requests leave from your computer, so they go out only while Natively is open. There is no Natively server that could send them for you. Use Send test event in Settings to check your receiver before relying on it.

Sending by hand and sending automatically

1. 1Connect the serviceOpen Settings > Connectors, choose the connector and sign in or paste its token. Tokens and webhook addresses are stored encrypted on your computer and are not shown again.
2. 2Send one meetingOn a meeting page, open Share and pick Slack, Notion or your CRM. Slack opens an editable draft and a CRM shows who matched; nothing goes out until you press Send.
3. 3Or create a ruleOn the connector's page, use Send automatically for all meetings or one folder. Each meeting is sent once per destination, even if you regenerate its notes, and rules run while Natively is open.
4. 4Check the resultEach rule and webhook shows its last delivery, so a failure is visible in Settings instead of silent.

Plans and platforms

Every connector on this page, the calendar sources and the MCP server are included in the free app. Pro adds modes, note templates and other features described on pricing, not extra connectors. Connectors behave the same on macOS and Windows, with two differences: Apple Calendar exists only on a Mac, and secrets are encrypted with the macOS Keychain on a Mac and with Windows' own data protection (DPAPI) on Windows. Natively does not run on Linux.

What is not integrated

• Task trackers. There is no Jira, Linear or Asana connector. A webhook or a Zap can create tasks there if you build that step.
• Applicant tracking systems. Nothing for Greenhouse, Lever or Ashby. Recruiters can use a webhook, Notion or Slack instead.
• Meeting platforms' APIs. Natively does not connect to Zoom, Microsoft Teams or Google Meet accounts. It captures the call from your computer's audio, so it works with any of them without a sign-in.
• Two-way calendar sync. Calendars are read, never written.
• Other email providers for sending. Sending from inside Natively uses Gmail; for other accounts, open the draft in your mail app.
• Other CRMs. No connector for Microsoft Dynamics, Zoho CRM or Close. A webhook is the route there.
• A cloud API. Natively has no hosted API for your meetings, because the meetings are not on a server. Local AI apps use the MCP server instead.

Your data, in one paragraph

Connector secrets live in encrypted files in Natively's user-data folder on your computer. For Slack, Notion, HubSpot, Salesforce, Pipedrive and Attio, the browser sign-in passes through Natively's server, which holds those services' client secrets and later renews expiring tokens, but meeting content is sent from your computer straight to the service. Gmail and the calendars sign in with Google or Microsoft directly. Once notes arrive in Slack, Notion, a CRM or your endpoint, that service's own terms and retention apply. The privacy policy has the full list of what Natively itself collects.