The MeetingPulse app for Zapier sends your participants' responses to other tools automatically, without exporting reports. When someone answers a poll or submits a question, Zapier picks it up and passes it to the app of your choice, such as Google Sheets, Slack, Salesforce or HubSpot.
The integration offers two triggers:
Trigger | Fires when | Works with |
Poll, Survey or Form Answers | A participant answers questions in a survey | Polls and Forms modules |
QnA, Ideas or Topic Answers | A participant submits a question, idea or comment to a topic | Q&A and Ideas modules |
Typical uses: logging survey answers in a spreadsheet as they come in, posting new audience questions to a Slack channel for moderators, or adding attendee feedback to contact records in your CRM.
Before you start
To use Zapier you need API access on your MeetingPulse account. It is available as an add-on to Enterprise plans. If you don't see an API section on your Account page, contact your account manager to add it.
You also need a Zapier account. Any Zapier plan works, but on free plans Zaps are limited to two steps.
Get your MeetingPulse API key
Sign in to MeetingPulse and open your Account page from the dashboard.
In the API section, click Generate next to Access token.
Click Copy. Keep the key private: anyone with it can read your meeting data.
Each account has one key. Clicking Regenerate creates a new key and stops the old one working, so any Zaps using the old key will need to be reconnected.
Connect MeetingPulse in Zapier
In Zapier, create a Zap and search for MeetingPulse as the trigger app.
Choose one of the two triggers described below.
When asked to sign in, paste your API key and confirm.
Zapier remembers the connection, so you only do this once per MeetingPulse account. Zaps only see meetings that the account owning the key has access to.
Trigger: Poll, Survey or Form Answers
This trigger sends one record per participant, containing that person's answers to every question in the survey you pick. Use it with the Polls and Forms modules.
Set it up
Field | What to enter |
Meeting | Pick the meeting from the list. You can also paste the meeting's link or custom URL. |
Survey | Pick the survey whose answers you want. Choose In-meeting polls for polls that aren't inside a survey. |
Pull updates to answers | No (the default) sends each participant once. Yes sends a new record every time the participant answers something. See below. |
When records are sent
With Pull updates to answers set to No, Zapier sends a participant's record the first time it finds at least one answer from them. Answers they give after that are not sent. This works well when people complete a survey in one go and submit it.
If participants answer questions over time, for example polls launched one by one during a live session, set it to Yes. Each new answer then sends a fresh record holding all of that person's answers so far. Your Zap will receive several records for the same person, so use the receiving app's update or find-and-update step, matched on Participant ID, rather than adding a new row each time.
Fields you can use
Field | Notes |
Participant ID | MeetingPulse's ID for the participant. Stays the same across records. |
Participant name | Empty if the participant didn't give a name. |
Participant email | Only present if you collect email, for example through registration or invites. |
External participant ID | The ID from your own system when participants sign in through SSO or an integration. |
First seen on | When the participant joined the meeting. |
Record ID | Same as Participant ID, unless Pull updates to answers is Yes, in which case it has a timestamp added. |
Q#1, Q#2, … | One field per question in the survey, labelled with the question text. |
Question fields hold the participant's answer, or nothing if they skipped that question. Multiple-choice answers with several selections are joined with commas. Rating, numeric and NPS answers come through as numbers.
The question fields are built from the survey as it is when you set up the Zap. If you add or reword questions later, open the Zap's trigger step and click Refresh fields so the new questions appear.
Trigger: QnA, Ideas or Topic Answers
This trigger sends one record for each question or idea a participant submits to a topic. Use it with the Q&A and Ideas modules.
Set it up
Field | What to enter |
Meeting | Pick the meeting from the list. You can also paste the meeting's link or custom URL. |
Topic | Pick the Q&A or Ideas topic to watch. Each topic needs its own Zap. |
When records are sent
Each submission is sent once, when Zapier first finds it. Newest submissions are picked up first.
Zapier doesn't resend a submission when it changes afterwards. Votes, score and moderation state are captured at the moment Zapier picks the submission up, so they will usually be low or show it awaiting moderation. For final vote counts, use the topic's report or CSV export after the session.
All submissions are sent, including ones that haven't been approved yet. If the topic is moderated and you only want questions your moderators have seen, keep that in mind before posting them anywhere public.
Fields you can use
Field | Notes |
Item text | The question or idea. If it has been translated, this is the translated text. |
Posted on | When the participant submitted it. |
Item ID | MeetingPulse's ID for the submission. |
Item state | Its moderation state when Zapier picked it up, for example submitted, pending or approved. |
Number of votes cast | Upvotes at the time Zapier picked it up. |
Voting score | Weighted vote score at the time Zapier picked it up. |
Participant ID | MeetingPulse's ID for the person who submitted it. |
Participant name | Empty if the participant didn't give a name. |
Participant email | Only present if you collect email, for example through registration or invites. |
External participant ID | The ID from your own system when participants sign in through SSO or an integration. |
Example Zaps
Goal | Trigger | Action | Tip |
Log survey answers in a spreadsheet | Poll, Survey or Form Answers | Google Sheets: Create Spreadsheet Row | Map each Q# field to its own column. |
Keep one up-to-date row per participant | Poll, Survey or Form Answers, with Pull updates to answers set to Yes | Google Sheets: Update or Create Row (lookup on Participant ID) | Avoids duplicate rows as people keep answering. |
Send new audience questions to moderators | QnA, Ideas or Topic Answers | Slack: Send Channel Message | Include Item text and Participant name in the message. |
Add feedback to contact records | Poll, Survey or Form Answers | Your CRM: Find or Create Contact, then add a note | Match on Participant email, so collect email in the meeting. |
Troubleshooting
How quickly do responses arrive? Zapier checks MeetingPulse on a schedule rather than instantly. How often depends on your Zapier plan, from every minute to every 15 minutes. Use Run in the Zap editor to check straight away while testing.
"The API key you supplied is incorrect." The key was mistyped or has been regenerated. Copy the current key from your Account page and reconnect MeetingPulse under Apps in Zapier.
"Standalone API keys are not available to your account." Your account doesn't include API access. Contact your account manager.
My meeting or survey isn't in the list. The list shows meetings the connected account can access. Check that the key belongs to the meeting owner or a manager, and that the survey contains at least one question. The In-meeting polls option only appears once the meeting has polls outside a survey.
"Your reference survey does not seem to exist" or "Cannot find the topic in question." The survey or topic was deleted or moved after the Zap was set up. Edit the trigger and pick it again.
A participant's later answers never arrived. With Pull updates to answers set to No, each participant is sent once. Switch it to Yes, as described above.
Name or email is blank. MeetingPulse only has what participants give it. Turn on registration or send invites if you need names and emails on every record.
Still stuck? Contact us through the chat in the bottom corner of the app.