Connector catalog

Each tool on this page connects under Settings → Integrations and receives responses through a step in a workflow. Slack, Microsoft Teams, HubSpot, Google Sheets, Linear, Jira, webhooks and Zapier have guides of their own, listed in the overview.

​

The tools

The tables follow the chips in Settings → Integrations. Google Analytics, FullStory and UXCam work on every plan. Every other tool here requires the Pro plan or higher.

​

Marketing

​

Product research

​

CX & support

​

Data

Google Analytics, FullStory and UXCam receive no answers and no personal data. See Google Analytics, FullStory and UXCam. Salesforce, Freshdesk, Help Scout and the other tools that Usertick doesn’t connect to natively are listed under With Zapier. See Tools with Zapier.

​

Connect a tool

Some tools ask for more before the popup opens, or name the permissions they request:

• Intercom asks for the Data center: United States, Europe or Australia. If you sign in at app.eu.intercom.com, select Europe.
• Klaviyo asks to write events and profiles, and to read the account name.
• Zendesk asks for the Zendesk subdomain, the first part of your Zendesk address, such as yourcompany for yourcompany.zendesk.com. yourcompany.zendesk.com and the full address work too. If the value isn’t one account name, Usertick stops before the popup opens: “Enter your Zendesk subdomain, such as yourcompany for yourcompany.zendesk.com.” Usertick asks for tickets:read, tickets:write, users:read and users:write, so the respondent can be the ticket’s requester. Reconnect uses the same subdomain.
• Mailchimp asks for no audience. Each step selects the audience it updates, so one connection covers every audience in the account. Mailchimp has no call that lets Usertick remove its own access, so after the connection is disconnected in Usertick, the app stays connected in your Mailchimp account until you remove it there.
• Productboard connects only when a Productboard workspace admin approves it. Usertick asks for notes:read, notes:write, entities:read and entities:write, so it can create notes and link the respondent to them.

If Klaviyo, Zendesk or Productboard didn’t grant every permission, the panel says so, for example “Zendesk didn’t grant every permission Usertick requests, so workflow steps that use this connection may fail. Reconnect and approve all permissions.” If Klaviyo, Zendesk or Productboard ends the connection, for example because the app was removed there, the connection shows Revoked. If the Usertick app is removed in Intercom, Intercom refuses Usertick’s access and the connection shows Failing. In each case, select Reconnect. For a tool that uses a key, Where to find these, beside the form, says where each value is in the tool:

• Region is a list: United States, Europe, and India for Mixpanel. It starts on United States. Customer.io and Iterable detect their data center when Usertick checks the key.
• REST endpoint for Braze is a list of Braze’s REST endpoints, each with its instance beside it, such as US-01 or EU-01. Your Braze dashboard address shows which one to use: dashboard-01.braze.com uses US-01, and dashboard-01.braze.eu uses EU-01.

​

Where to find the keys

​

Check a connection

When a tool is connected, Usertick checks the connection with a call that writes nothing in the tool. Test in the connection’s menu checks it again. Braze and Segment keys can’t be checked without sending data. Their panels say “Usertick can’t check a Braze key without sending data. After the first response is sent, the workflow’s activity shows whether the key works.” Such a connection shows Not checked instead of Healthy, and Test leaves its status as it is. For Braze, Usertick checks only that the REST endpoint is one of Braze’s own.

​

Manage a connection

The menu on a connection’s row has Test, Rename, Reconnect, Set as default and Disconnect. A new step starts with the connection the organization used last for that action, or else the default connection. Disconnecting asks you to type the connection’s name, lists the workflows that use the connection, and their steps stop sending until another connection is assigned to them. When Usertick can’t check which workflows use the connection, it says so, and if any do, it lists them and asks again before the connection is disconnected.

​

Event tools

Mixpanel, Amplitude, Segment, Customer.io, Braze, Iterable, Intercom and Klaviyo each receive one event per response. To send one, add the tool’s Track an event step to a workflow. The step has one setting: The event carries the time the response arrived, not the time it was sent, and the tool’s own dedupe ID where the tool has one. A retry repeats the same event, so the tool doesn’t count it twice. Braze keeps no dedupe ID, so Usertick never sends a Braze event again after a send that got no answer. The run then says “Braze did not answer in time. The event may have arrived, so it was not sent again.”

​

Who it is sent for

Each tool receives the event only for a person it can name: your user ID from identify() or the respondent’s email, never the browser’s anonymous ID or the response ID. A response without what the tool needs is skipped. A skip isn’t a failure, and the workflow’s activity gives the reason. Some tools refuse a person they don’t have. Intercom never creates a contact from an event, and an email based Iterable project refuses an unknown user. The run then says “The tool has no person with this user ID or email.” When Braze, Amplitude or Iterable refuses the person for another reason, the run says “The tool did not accept this person.” Both are skips. Braze logs events only on users it already has, so a survey response never creates a Braze user. The email comes only from an email campaign’s contact, identify() or a Contact details question. See how a tool knows who answered for the fields each tool receives.

​

What the event carries

Every event tool receives these properties, each only when it has a value: An answer property’s name is the question’s text in lowercase letters, digits and _, up to 60 characters after answer_. When two questions of a survey have texts that make the same name, each of them gets the first six letters and digits of its question ID after the name, such as answer_how_was_it_3f2a9c, so one question’s property never moves to the other. Renaming a question starts a new property. File uploads, screenshots, signatures, Contact details answers and message screens are never sent, and neither is any value that holds a link to a stored file. Each tool receives the properties in the shape it accepts:

​

Test

During a workflow’s Test run, an event tool’s step never writes an event:

• On a real response, Usertick checks the connection the same way the connection’s Test does, and the step reads Checked, nothing sent. When the tool refuses the connection, the step reads Failed with the reason.
• On a sample response, Usertick contacts no tool at all, and the step reads Checked, nothing sent.

When the response lacks what the tool needs, the step is skipped with the same reason a run gives, such as “The response has no user ID from identify().”

​

Record tools

Zendesk, Productboard, Mailchimp and BigQuery each write one record per response. To send one, add the tool’s step to a workflow.

​

Zendesk

The action Create a ticket has these settings: A tag keeps lowercase letters, digits, _ and -, and any other character becomes _. A ticket gets up to 20 tags, each up to 80 characters. Custom fields starts with “No custom fields are set.” Add a custom field searches the account’s active custom ticket fields, and the list shows each field’s Zendesk type: Text, Multi-line, Checkbox, Date, Number, Decimal, Regex, Drop-down, Multi-select or Lookup relationship. Each added field gets a row with a value that fits its type:

• A number for Number and Decimal fields.
• Checked for a Checkbox field.
• A date for a Date field.
• For a Drop-down field, the option’s tag, as the field’s settings in Zendesk show it.
• For a Multi-select field, the options’ tags, separated by commas.
• Text for the other types.

The delete icon on a row removes the field from the step. The respondent is the ticket’s requester when their email is known. A retry finds the ticket it made, so it never makes a second one. During a workflow’s Test run, the Zendesk step creates a real ticket whose subject starts with “[Test]” when the test uses a real response. On a sample response, the step doesn’t contact Zendesk and reads Checked, nothing sent.

​

Productboard

The action Create a note has these settings: The respondent is linked only when their email is known. If Productboard refuses to create the user, Usertick creates the note without a customer. Each note carries a source record ID made from the response. Before a failed send goes out again, Usertick looks for that note, so a retry never makes a second note. During a workflow’s Test run, the Productboard step creates a real note whose title starts with “[Test]” when the test uses a real response. With Link the respondent as the customer on, the test can also create the respondent as a Productboard user. On a sample response, the step doesn’t contact Productboard and reads Checked, nothing sent.

​

Mailchimp

The action Update the contact has these settings: Who gets updated. Mailchimp needs the respondent’s email, and a response without one is skipped: “The response has no email address.” By default, Usertick updates only people who are already contacts in the audience. A person who isn’t a contact, or who is archived in the audience, is skipped: “This person isn’t a contact in the Mailchimp audience, and the step doesn’t add new contacts.” A skip isn’t a failure. New contacts. With Add new people as contacts on, the step also adds people the audience doesn’t have, and each new contact counts toward your Mailchimp bill. Usertick adds new people as transactional contacts, so they aren’t subscribed to your campaigns. Usertick never subscribes anyone, and an existing contact keeps their status. Merge fields. Until an audience is selected, the mapping says “Select the field above first.” Each row pairs a question with a Merge field. The lists show the audience’s text, number and date merge fields, and Usertick never creates a merge field. Each of the four value lists starts with Don’t write this value, which clears it. Selecting another audience clears the mapping and the four fields. Each value takes the shape of its field:

• A number field gets a number. An answer that isn’t a number is left out.
• A date field gets the date in the field’s own format: MM/DD/YYYY, DD/MM/YYYY or YYYY-MM-DD.
• A text field gets the text, cut at 255 characters.

An answer that doesn’t fit its field’s type is left out, and so is a merge field the audience no longer has. The rest of the contact is still updated. Tags. The tags go through Mailchimp’s own tags call, so they reach existing contacts too. The event. usertick_survey_response carries survey_id, survey_name, response_id, response_url and, when the survey has one, score, all as text. It carries the time the response arrived. Mailchimp keeps no dedupe ID for events, so Usertick never sends an event again after a send that got no answer. The run then says “Mailchimp did not answer in time. The event may have arrived, so it was not sent again.” Test. During a workflow’s Test run, the Mailchimp step never writes anything in Mailchimp. On a real response, it reads the audience, the contact and the merge fields, and the step reads Checked, nothing sent. If the person isn’t a contact and the step doesn’t add new contacts, the step is skipped with “This person isn’t a contact in the Mailchimp audience, and the step doesn’t add new contacts.” On a sample response, Usertick doesn’t contact Mailchimp.

​

BigQuery

The action Insert a row adds one row per response. The table needs these 10 columns, which the connection panel lists under Table columns: Usertick leaves survey_name and variant empty when a response has no value for them, so both columns need the NULLABLE mode. A response from a survey without variants has an empty variant. Usertick checks the table when the connection is made and refuses a table that is missing or lacks a column: “Usertick can’t use this BigQuery table. Check that the dataset and the table exist and that the table has every column listed under Table columns.” The error code is CON-001-008. The connection’s Test names the missing columns, such as “The test did not go through: The BigQuery table is missing these columns: survey_name, variant.” A workflow’s test run and its activity show the same list. The service account needs to read the table and add rows. The BigQuery Data Editor role on the dataset covers both. During a workflow’s Test run, the BigQuery step checks the table and its columns and adds no row.