Skip to content

Connect your survey to the tools you use.

Send survey notifications to Slack, update HubSpot contacts, or keep a Google Sheet in sync. Connect recruitment panels and custom workflows using the guides below.

Survey links also accept URL parameters, and up to 10 are saved with each response (names up to 40 characters, values up to 200). Use them to carry a CRM reference, ticket ID, session or cohort from another system.

Notify your team and update contacts

Workspace owners connect these in the survey builder under Settings → Delivery. Add an optional answer condition to send only the completions relevant to the workflow.

SlackPRO

Send a survey title, response ID and dashboard link to a chosen Slack channel. Answer text stays in Plumeform.

See setup details

HubSpotPRO

Create or update a contact matched by email. Map the name, company and phone fields you want to send from your survey.

See setup details

Recruiting participants

All three work the same way: the panel appends a participant id to your survey link, Plumeform records it with the response, and a redirect or a completion code closes the loop. Nothing to install, and no third-party script on the page a participant sees.

Prolific

Study URL template, participant and session ids, completion codes and redirects, screen-out routing, duplicate blocking, and a test mode that keeps pilot rows out of your results.

See setup details

Sample providers

Any panel company or fieldwork agency: its respondent ID on your survey link, and its complete, terminate and over-quota links, so every respondent is counted the way the provider bills.

See setup details

Getting the answers out

Send new responses to a spreadsheet or webhook, or fetch completed responses through the API on your own schedule.

Google SheetsPRO

Each completed response appended as a row to a spreadsheet Plumeform creates for the survey, in survey order, with answers written the way a person reads them. One-way, and best-effort by design: a broken connection stops new rows but never loses a response.

See setup details

WebhooksPRO

A signed POST to your endpoint the moment a response completes. One event, HMAC-SHA256 over the raw body, five-second timeout, and a test event you can fire before a single respondent exists.

See setup details

Results APIPRO

Three read-only endpoints with bearer keys, keyset pagination and an incremental since parameter. Read-only on purpose: a leaked key exposes data and cannot change it.

See setup details

Slack setup

A response arrives. Your team gets a link.

  1. Create an incoming webhook in your Slack workspace and choose the destination channel.
  2. As the owner of a Pro workspace, open your survey's Settings → Delivery → Connected delivery. Select Slack and paste the webhook URL.
  3. Save and enable the connection. Complete a real response to verify delivery, then check its status in Connected delivery.

Use a channel appropriate for survey notifications. Messages include the survey title and a dashboard link, but do not include the respondent's written answers.

HubSpot setup

Put the contact details where you use them.

  1. Create a HubSpot private app with the crm.objects.contacts.write permission.
  2. Select HubSpot in Connected delivery and enter the private-app access token. Choose the survey's email question and any optional contact fields to map.
  3. Enable the connection and submit a response with a valid email. Verify the contact in HubSpot and review the delivery status.

Existing contacts are matched by email. A missing or invalid email skips delivery. Updating a contact does not subscribe that person to marketing.

Checking a connection

Only new, completed responses are sent. Test-mode and screened-out responses are excluded. Deliveries usually run within a minute, with up to four attempts in total. Check recent status, correct credentials or mappings, and retry a failed delivery from the builder. Slack can receive a duplicate if an acknowledgement is lost.

For Zapier today, use a Catch Hook with Plumeform's webhook or the Results API. Our native Zapier connector has been built but is not published in the Zapier directory.

Connected delivery in the help center

Missing one you need? The help center covers exports, versioning and the survey settings used here. Contact us if you need an integration we do not support.