Skip to content

Product Guide

Integrations

Your audience joins a PollsLive session from any device by code, QR or link, with no app to install. Leads from your surveys can go straight to Slack, Google Sheets or a webhook, and on Pro and up the REST API and signed webhooks connect PollsLive to your own systems.

Overview

IntegrationBest forPlan required
Code, QR or linkYour audience joins from any phone, tablet or laptopEvery plan
Survey leadsNew contacts from your surveys, sent to Slack, Google Sheets or a webhookPro and up, or webhooks with an Event Pass
REST APIProgrammatic poll creation & resultsPro and up
WebhooksReal-time event notificationsPro and up

Join from any device

Show the 6-digit code or the QR code on the screen, or send the join link. People join in the browser on a phone, tablet or laptop, with no app and no account.

Sharing guide →

Send survey leads to your tools

When someone answers a survey and leaves their contact details, PollsLive can send that lead to Slack, to a Google Sheet or to a webhook of your own. Add each destination once in Studio → Integrations, then choose which ones each survey sends to.

When a lead is sent

A lead is sent only when all of these are true:

  • The survey has Contact details turned on, with its consent box.
  • The person ticks the consent box and gives at least one of their email, name or company.
  • Your workspace has lead capture. It comes with the Pro and Premium plans, and an Event Pass adds it for the deck it is on.
  • The destination is ticked in the survey's Contact details card.

Only new leads are sent. If someone already captured on a survey answers it again, nothing new goes out.

You can add a webhook destination on any plan and press Test on it, but real leads only go out with lead capture, as above. Slack and Google Sheets destinations need the Pro or Premium plan, so with an Event Pass alone, use a webhook.

Choose destinations for each survey

Adding a destination does not send anything on its own. Open the survey in the editor, go to its Contact details card and tick each destination under Destinations. Each survey can send to a different set. Automation rules in the same card can also send a lead to one more destination when an answer matches.

Test a destination

Press Test next to a destination to send it a sample lead, with the email sample.lead@example.com and the tag test. Nothing is saved in PollsLive, so test as often as you like. A test shows only that the destination can be reached: real leads still need everything above.

Webhook

A webhook sends each lead to a URL you choose, such as your own app or an automation tool. Paste the URL when you add the destination. PollsLive then shows a signing secret once: copy it straight away, because it is not shown again.

The URL must begin with https:// and be reachable from the internet. Local and internal addresses are refused, and redirects are not followed, so paste the final URL.

These lead webhooks are separate from the Developer API webhooks further down this page. Expect the body and headers below.

Each lead arrives as one POST request with a body like this:

Request body
{
  "type": "lead.captured",
  "createdAt": "2026-11-12T09:30:00.000Z",
  "data": {
    "leadId": "cm3x8k2p40001",
    "pollId": "cm3x7v9q10000",
    "pollSlug": "customer-feedback",
    "pollTitle": "Customer feedback",
    "createdAt": "2026-11-12T09:30:00.000Z",
    "email": "alex@example.com",
    "name": "Alex Morgan",
    "company": "Example Ltd",
    "answers": { "budget": "10k-50k", "rating": 4 },
    "score": 85,
    "tags": ["hot"],
    "source": "survey"
  }
}

email, name and company are null when the person left them out. answers holds each answer under the name you set in Field mapping, or under the question id. score runs from 0 to 100, and tags lists the tags your automation rules added.

Each request carries these headers:

  • Content-Type: application/json
  • User-Agent: PollsLive-Leads/1.0
  • X-PollsLive-Event: lead.captured
  • X-PollsLive-Signature: t=<t>,v1=<v1>

In X-PollsLive-Signature, t is the time the request was sent, in Unix seconds, and v1 is the signature, in hex.

Check the signature

  1. Read the request body as raw text, before you parse it.
  2. Split the X-PollsLive-Signature header at the comma into t and v1.
  3. Compute an HMAC-SHA256 of t, a dot and the raw body, with your signing secret as the key, written as hex.
  4. Compare the result with v1 in constant time. Reject the request if they differ, or if t is more than a few minutes old.
Node.js
import crypto from "node:crypto";

// rawBody: the request body exactly as received, as a string
// header:  the X-PollsLive-Signature header
// secret:  the signing secret PollsLive showed you (whsec_...)
export function verifyLead(rawBody, header, secret) {
  const parts = Object.fromEntries(
    header.split(",").map((pair) => pair.split("="))
  );
  const expected = Buffer.from(
    crypto
      .createHmac("sha256", secret)
      .update(`${parts.t}.${rawBody}`)
      .digest("hex")
  );
  const received = Buffer.from(parts.v1 ?? "");
  const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300;
  return (
    fresh &&
    expected.length === received.length &&
    crypto.timingSafeEqual(expected, received)
  );
}

// After verifying: skip a lead you have already handled.
// const lead = JSON.parse(rawBody);
// if (await alreadyHandled(lead.data.leadId)) return reply(200);

Replies and retries

Reply with any 2xx status within 10 seconds. Any other status, or no reply in time, counts as a failed attempt.

A failed lead is sent again, up to 6 attempts in all, waiting about 1 minute, 5 minutes, 30 minutes, 2 hours and then 6 hours between them. Each attempt is signed again with a new t.

The same lead can reach you more than once, for example when your reply was lost on the way. Store data.leadId and skip any lead you have already handled. Lead webhooks have no X-PollsLive-Delivery header.

Slack

Slack gets a short message in the channel you pick for each new lead: the survey title and score, then the email, name, company and tags. Answers are not included.

  1. Create a Slack app for your Slack workspace, or open one you already have.
  2. In the app's settings, turn on Incoming Webhooks.
  3. Add a new webhook and choose the channel the leads should go to.
  4. Copy the webhook URL, which begins with https://hooks.slack.com/, and paste it into PollsLive. Other URLs are refused.

Slack explains each step in its guide to incoming webhooks.

Google Sheets

Google Sheets gets one new row for each lead, under the last row of the tab you choose.

  1. In Studio → Integrations, choose Google Sheets and copy the email address PollsLive shows for sharing.
  2. In your sheet, press Share, add that address and give it Editor access.
  3. Paste the sheet's link, or just its ID, into PollsLive. Type a tab name to send the rows to that tab, or leave it empty to use the first tab in the sheet.
  4. Add the destination. PollsLive shows a verification code and keeps the destination off for now.
  5. Add a tab named exactly PollsLive to your sheet and paste the code in cell A1.
  6. Press Verify. When the code matches, the destination turns on. You can delete the PollsLive tab afterwards.

Each row has these columns, in this order: the time the lead was captured, email, name, company, survey title, answers (all in one cell), score and source. PollsLive does not add a header row, so type your own in row 1 if you want one.

REST API

The PollsLive REST API lets you create polls, record responses, control live sessions, and pull results, all programmatically. Authenticate with a Bearer API key or OAuth 2.0 access token.

Quick example
curl -X POST https://pollslive.com/api/v1/polls \
  -H "Authorization: Bearer $POLLSLIVE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "title": "Team sync vote", "content": { "questions": [...] } }'

Developer guide → · API reference →

Webhooks

Subscribe to events and receive signed HTTP POST payloads to your endpoint. Events include poll.published, session.started, response.created, and more.

All payloads are HMAC-SHA256 signed using your webhook secret. Verify the signature before processing the event.

Set up webhook endpoints in Studio → Developer API → Webhook endpoints or via the API.

Full webhook guide →

Still have questions?

Our team is happy to help.

Contact us

We use essential cookies to keep you signed in and stop duplicate votes. With your permission, we also use Cloudflare Web Analytics to count page views and the Whop Pixel to see which visits lead to a purchase. Cookie Policy