PulseIntegrations overview
The external services Pulse can connect to, and what data each integration sends.
There are times when you want meeting notes to reach the tools you already use rather than staying inside Pulse. Several integrations exist for that, and you can choose between sending notes manually and sending notes in a folder automatically. This article lists the services you can connect and what each integration sends out.
Integrations are connected and disconnected under Connectors in the desktop app's settings (macOS / Windows). The only integration available on the free plan is Slack. The others require a paid plan. For the differences between plans, see Plans and billing.
The external services you can connect, shown as cards under “Connectors” in settings (opened from your avatar at the bottom left). Connected services are marked as such.
Services you can connect
The CRM integrations (Attio, HubSpot, Affinity) automatically look for the matching record in the CRM using the calendar attendees' email addresses and offer it as a suggestion. Where no record has a matching email address, no suggestion appears and no data is created.
The setting for sending notes added to a folder automatically is on the folder itself. The steps are under “Automatic posting from a folder” in Spaces and folders.
What each integration sends externally
Before deciding which integrations to enable, check what leaves your company through each. The table below summarises what each typically sends. The details per field are in the individual articles. Fields can change when the destination service changes its own specification, so confirm the exact scope against each integration's article and the destination service's published documentation.
| Destination | Data sent | When it is sent | Can administrators restrict it |
|---|---|---|---|
| Slack | the share link to the note, and the body of the AI-enhanced summary | when sent manually from a note / where automatic posting is set on a folder, notes added to that folder after it was configured | partly. Controlled by whether the app is added to the workspace and to each channel on Slack's side. Whether rich previews apply across the organisation is set by the Pulse workspace administrator |
| Notion | the note's content (created as a page in the destination database) | when a note is sent to Notion | controlled by the permissions granted to the integration on Notion's side and the sharing scope of the target database |
| Zapier | the note title, the author's name and email address, attendees' names and email addresses, calendar event details, your own notes, the AI-enhanced summary, the full transcript, and the note's share link | when the Zap's trigger fires (a folder addition, or a note sent manually to Zapier) | partly. The Zap's creator chooses whether to share it within the workspace. A Zap targeting a folder can only be configured by that folder's collaborators or owner |
| Attio | the AI-enhanced note (added as a note on the target record) | when sent manually from a note / where automatic sending is set on a folder, notes added to that folder after it was configured | partly. Controlled by whether the Attio workspace connection is permitted |
| HubSpot | the AI-enhanced note (created as a meeting or note record) | when sent manually from a note / where automatic sending is set on a folder, notes added to that folder after it was configured | partly. Controlled by whether the HubSpot account connection is permitted. A Google Workspace or Microsoft 365 account is required |
| Affinity | the AI-enhanced note (added as a note on the target record) | when sent manually from a note | partly. Controlled by whether API keys can be issued on Affinity's side |
| MCP server | in response to queries from the connected AI tool: the list of notes, their bodies, attendees, folder information and transcripts | each time the AI tool queries | yes. On the Enterprise plan, administrators can set the scopes members are allowed; disabling both means members cannot use it |
| API | the notes, transcripts and AI-enhanced notes within the API key's scope | each time an external system makes a request | yes. Available on Team and above; on the Enterprise plan administrators can set the scopes members are allowed. Whether a space is readable through the API can also be toggled per space |
What to check before sending data out
The destination services are operated by providers other than UNCHAIN, Inc.. Meeting notes and transcripts normally contain personal data such as attendees' names, organisations, email addresses and what they said. How sending a note containing personal data to an external service should be accounted for depends on your contract with the destination and how the destination handles data. The reasoning is covered in the section on external sharing in Sharing notes and in Sharing controls. Where the destination is an overseas provider, cross-border transfer of personal data can come into play. See also Security and privacy FAQs.
Before enabling an integration, check the following.
- that you have checked, in the table above, what data that integration sends out
- that it falls within your own personal data handling rules and the purposes of use you have published
- that the people who can see the destination channel or record are appropriate for the content of the notes
- that you have a plan to try it with a limited team first, check what actually gets written, and widen from there
Data after you disconnect an integration
Disconnecting an integration does not remove data already sent to the destination. A summary posted to Slack, for example, is a Slack message in its own right, so changing the note's sharing setting to private in Pulse afterwards does not remove the posted text. Where sent data has to be deleted, delete it in the destination service itself.