Send completed responses to your CRM

Connect HubSpot, Salesforce, Pipedrive, Intercom, or Zoho CRM and add completed survey responses to matching records.

Last reviewed
integrationsrespondents

Before you start

You must own the survey and be authorized to send its answers to the chosen CRM. Availability varies by environment: a card marked Coming soon cannot connect yet. Salesforce requires an edition with API access. Have a test contact and an approved way to identify respondents by email.

Steps

  1. Connect the CRM account

    Open account Settings > Integrations, find the CRM card, and choose Connect for that provider. For Intercom, select the correct Workspace region first: United States, Europe, or Australia. Complete authorization and verify the Connected badge and account label.
  2. Enable delivery for this survey

    Open the owned survey’s Settings > Integrations > CRM. Turn on Send responses to [provider]. Connecting the account alone does not enable survey delivery. Responses go to the survey owner’s connection; collaborator edit permission is not enough to configure it.
  3. Decide how to handle unknown emails

    Review Create a [record] when none matches. When off, responses from emails not found in the CRM are skipped. Turn it on only if you want new CRM records created.
  4. Supply the respondent’s email

    Ask an Email question, or add the email merge field from your campaign tool as the survey link’s email parameter. Use &email= if the link already has a query string. Send yourself a test campaign email and check that the merge field resolves. A valid email in the link takes precedence over an Email-question answer; do not share a personalized link with other people.
  5. Verify an authorized live completion

    Complete the published survey with approved test content and the intended test contact. Preview and synthetic tests do not establish CRM delivery. Check the expected CRM record for the note or task and its View this response in QuestionPunk link. Open that link with an authorized QuestionPunk account and compare the response.
  6. Stop delivery when needed

    Turn off the survey switch to stop that survey’s delivery. Account Disconnect stops all survey syncs for that provider. Verify disconnection succeeds; a failed disconnect can leave it connected. After reconnecting, configure the survey switches again. Disconnecting does not remove notes or tasks already delivered.

Details and limitations

HubSpot: matches a contact by email and adds a note; optional creation adds a contact. Salesforce: checks contacts before leads and adds a completed task; optional creation adds a lead.

Pipedrive: matches a person and adds a note; optional creation adds a person. Intercom: matches a user or lead by email and adds a contact note; optional creation adds a lead. Zoho CRM: checks contacts before leads and adds a note; optional creation adds a lead.

Notes contain answered questions in order and a link to the full response. Long answers can leave later answers out of the CRM note, so use the linked response for the complete record.

This sends eligible completed responses. It is not two-way field synchronization or a historical import. Missing or invalid emails are skipped, and plan response-visibility limits can prevent external delivery. Do not assume reconnecting will backfill missed responses; there is no user-facing replay control in this workflow.

For custom mappings or other destinations, see webhook-based automation and webhook delivery settings.

Check the result

The account shows Connected, the owned survey’s delivery switch is enabled, and an authorized live completion appears on the expected CRM record.

If something goes wrong

For a missing note or task, check the connected account, survey switch, completion status, matching email, create-missing setting, and plan visibility allowance. Inspect the original link email if it matched the wrong person. For Intercom connection problems, check Workspace region. If delivery still fails, contact support with the provider, time, and error, leaving out credentials and respondent answers.