Integrations overview

Integrations send responses from Usertick to other tools as they arrive. Depending on the tool, a response becomes a message in Slack or Microsoft Teams, an issue in Linear or Jira, a HubSpot contact update, a row in Google Sheets or BigQuery, an event in an analytics or messaging tool, or a signed webhook call.

​

What the catalog includes

Settings → Integrations lists every tool. Tools that are already connected appear first, under Connected, with their status and how many workflows use them, such as “Used in 2 workflows”. The other tools appear under Add an integration (or Connect your first tool when nothing is connected yet), grouped by these chips: Search integrations finds a tool by its name or its description. The connector catalog describes every tool that has no guide of its own. Opening the catalog and connecting, changing or disconnecting a tool need the Manage integrations permission. Workflows, which decide what a connected tool receives, need the Manage workflows permission.

​

Plans

• On every plan, the widget can send an event to Google Analytics, FullStory and UXCam on your site.
• On the Starter plan and above, Slack, Microsoft Teams, Google Sheets, webhooks, Zapier and the tools with Zapier work too.
• Every other tool in the catalog, API keys for the REST API and the MCP server require the Pro plan or higher.
• While the organization’s plan doesn’t include a tool, its tile names the plan that does.
• After a move to a lower plan, connections stay connected and keep their settings. Workflows that use a tool the plan no longer includes stop until an upgrade, and the workflows list names the plan they need. See Plans and billing.

​

How a tool connects

A connection belongs to the organization, so a tool connected once is available to every workflow.

• Sign in with the tool. Slack, Microsoft Teams, HubSpot, Google Sheets, Linear, Jira, Mailchimp, Klaviyo, Productboard, Intercom and Zendesk connect with OAuth. The connect button opens the tool’s own consent screen in a popup, and no key is copied. Intercom first asks for the Data center, and Zendesk for the Zendesk subdomain. Only a Productboard workspace admin can approve Productboard. Microsoft Teams also needs the Usertick app added to a team in Teams. Google Sheets can access only the spreadsheets Usertick creates and the ones selected in Google Drive.
• Enter a key from the tool. Customer.io, Braze, Iterable, Amplitude, Mixpanel, Segment and BigQuery connect with a key or token that the tool issues. The panel’s Where to find these says where each value is in the tool. Keys are stored encrypted and never shown again.
• Switch it on per site. Google Analytics, FullStory and UXCam need no connection. When they are switched on for a site, the widget sends them an event through their own script on the page. See Google Analytics, FullStory and UXCam.
• Use a Zap. A tool with Zapier never connects inside Usertick. A workflow’s step for the tool hands responses to a Zap made for that step, and the tool’s tile opens a ready Zap that starts on each new response. See Tools with Zapier.

Test in a connection’s menu checks the connection again, with a call that writes nothing in the tool. Braze and Segment keys can’t be checked without sending data, so those connections show Not checked, and the workflow’s activity shows whether the key works after the first response is sent. The connector catalog has the details for each tool.

​

Send responses to a tool with a workflow

Connecting a tool sends nothing by itself. A workflow decides which responses of a survey go to which tool, with a trigger, conditions and one step for each action. A new step uses the connection the organization chose the last time it used that action, or else the tool’s default connection. Each survey can have its own workflows, so a support survey can post to Slack while a research survey creates Linear issues. Workflows covers conditions, branches, waits, test runs, activity and what happens when a step fails.

​

How a tool knows who answered

When a response goes to a tool that keeps track of people, Usertick names the person by two values only: your user ID from identify() and the respondent’s email. Usertick never uses the browser’s anonymous ID or the response ID as a person. The email comes from one of three places:

• the contact an email campaign was sent to,
• identify(), as the email trait or in the token,
• a Contact details question.

An answer to any other question never names the person, even when it is an email address. When several emails are known, the campaign contact comes first, then an email from identify() that a hash verified, then the Contact details email, then an email from identify() without a valid hash. Each tool needs a different part of that, and receives it in its own fields: A response without what the tool needs is skipped, and the workflow’s activity gives the reason: “The response has no user ID from identify().”, “The response has no user ID or email.” or “The response has no email address.” A skip isn’t a failure. Google Analytics, FullStory and UXCam receive no person at all. See who it is sent for for the details. HubSpot finds the contact by your user ID, then by the email, and can create one. See How Usertick finds the contact. Mailchimp finds the contact by the respondent’s email and skips a response without one. By default it also skips a person who isn’t a contact in the audience. Zendesk makes the respondent the ticket’s requester, and Productboard links the respondent to the note as its customer, when the email is known. In the Monitor and Enforced verification modes, an email that came from identify() without a valid hash never reaches a CRM, a mailing list or an event tool. Only the contact an email campaign was sent to, a verified email and an email typed into a Contact details question count. Your user ID is sent in every mode, except to HubSpot, which uses only a verified user ID in these modes.

​

Responses past your plan’s limit

When the organization reaches its monthly response limit without extra responses, Usertick stops collecting responses, so no new response reaches your tools until collection starts again. When the organization has extra responses, responses past the limit reach your tools like every other response. See how response limits behave.