PulseZapier integration
Building automations in Zapier triggered by Pulse notes, and what data is sent.
Connecting Zapier lets you automate the work that follows a meeting — creating a task from a note, updating a CRM record, notifying the responsible team — without copying and pasting. It can be combined with any service in Zapier's app directory.
Personal plan Team plan Enterprise plan
Setting up the integration
- a Pulse account on a paid plan (Personal, Team or Enterprise) and the desktop app (macOS / Windows)
- a Zapier account
- to trigger from a folder, collaborator or owner permission on that folder
Zapier shown in the list of connectable external services, with the button to begin setup.
Open connectors in settings
In Pulse's settings (opened from your avatar at the bottom left), choose “Connectors” and begin setup from Zapier.
Search for Pulse in Zapier
The screen for configuring a trigger event opens in Zapier. Search for Pulse in the app search field and choose the integration.
Choose a trigger
Choose when the Zap should run. For meetings that recur — a weekly sales review, say — the folder trigger suits; for meetings you decide about case by case, the manual trigger does.
- Note Added to Folder — runs automatically when a note is added to the folder you specify. It covers only notes added to the folder after you set the Zap up.
- Note Shared to Zapier — runs when you send a note to Zapier manually from the note's sidebar.
Configure the integration's details
- Name — the name given to the integration. It appears in the note's sidebar under this name, so something that describes what it does, such as “Send tasks to Linear”, reduces mis-selection.
- Share with your workspace — whether members of your team can also run the same Zap from Pulse.
- Folder — where you chose the folder trigger, which folder it applies to.
Test it
Zapier finds up to three recent meetings and offers them as test data. Choosing one lets you see exactly what will be sent. Check here that the fields you expect are present.
Add the action to run
Add the app you want to run after the trigger. Common combinations are creating records in a CRM (HubSpot, Salesforce, Attio) or applicant tracking system (Greenhouse, BambooHR, Ashby), notifying internal communication tools (Slack, Microsoft Teams), and creating tasks in task managers (Asana, Trello, Monday, Linear). Any other service in Zapier's app directory can be connected the same way.
The two trigger types offered as options.
The name field, the workspace sharing toggle, and the target folder selector.
- Zapier's test retrieves data containing the fields you expect
- the Zap's name appears in the note's sidebar
What is sent to Zapier
When a Zap runs, Pulse sends Zapier a webhook payload containing the following from the meeting note.
| Field | Content |
|---|---|
| Title | the meeting note's title |
| Author | the name and email address of the person who created the note |
| Attendees | the list of meeting attendees (each with name and email address) |
| Calendar event | details of the linked calendar event (title, date and time) |
| Your own notes | the notes you typed during the meeting. This is the content of the personal notes field opened from the three-line icon at the top right of a note — the part not shown to other attendees |
| Summary | the AI-enhanced note's summary (in Markdown) |
| Transcript | the meeting's full transcript |
| Link | the share link to the note in Pulse |
Zapier receives not only the summary but the full transcript and your own notes. A transcript can contain small talk that did not make the summary, and conversation from before and after the meeting. Work on the basis that it may contain personal data and information that must not leave your company, and check where the Zap connects to and where data flows on from there. How to account for sending to external services as handling of personal data is covered in Integrations overview.
To automate only particular meetings, the folder trigger with a controlled set of notes going into that folder is easier to manage. If you do not want transcripts leaving, build the Zap so that later steps reference only the fields you need and never pass the transcript field on.
Running it once set up
Once a Zap is configured, it appears in the note's sidebar. Clicking it runs the Zap.
The configured Zaps' names listed in the sidebar, ready to run with a click.
Where you chose the folder trigger, you can also see the active Zaps from the folder's integration settings.
The active Zaps shown in the integration settings opened from the folder header.
If something is not working
Q. Zapier syncing has stopped
A. Where a Zap that was working no longer runs, check these three things on Zapier's side.
- Is the Zap on? Zaps can be paused or switched off. Check the Zap is running.
- Reconnect the trigger. If you deleted and recreated the Zap, or disconnected and reconnected the integration, open the Zap in Zapier's workflow editor and reconnect the Pulse trigger.
- Is the right workspace selected? Check that each Zap's trigger configuration specifies the correct Pulse workspace.
Q. Zaps do not run when I belong to several workspaces
A. Where you belong to several workspaces, the Zapier integration has to be updated to the newer version. For each configured Zap:
- Open the Zap in Zapier's workflow editor and select the Pulse trigger.
- A prompt to move to the newer version appears; follow it and continue to the next screen.
- After updating, selecting the target Pulse workspace becomes mandatory. Choose the correct workspace here.
- Republish the Zap.
Q. My folder does not appear in the Zap settings
A. To use a folder as a trigger you have to be a collaborator or owner of that folder. If you only have viewer permission, ask the folder's owner to change it in the sharing settings.
Q. I need help with something on Zapier's side
A. For building Zaps themselves, see Zapier's help centre. If Pulse is behaving unexpectedly, contact tharada@the-unchain.com.