> ## Documentation Index > Fetch the complete documentation index at: https://docs.usertick.com/llms.txt > Use this file to discover all available pages before exploring further. # Zapier > Zaps start from new and analyzed responses, status changes, urgent feedback and workflow steps, and can find, comment on and update responses. In early access, by invite. > [!NOTE] > > The Usertick app for Zapier is in early access and isn't listed in Zapier's app directory yet, so joining requires an invite link. The link is in **Settings → Integrations → Zapier**. Until the link is available, that panel says "The invite link isn't available yet." With the Usertick app, a Zap can start when a response arrives, after Usertick AI analyzes it, when its status changes, when it becomes urgent or when a Usertick workflow reaches the Zap's step. A Zap can also find a response, add a comment to it, or change its status, type or urgency. Zapier requires the Starter plan or higher. ## What the app offers | Kind | Name | What it does | | - | - | - | | Trigger | **New Response** | Starts when someone answers a survey. **Survey** limits it to one survey; left empty, it covers every survey. Instant | | Trigger | **Response Analyzed** | Starts when Usertick AI has analyzed a response. **Feedback types** (bug, idea, complaint, question, praise) and **Urgency** (high, medium, low) can limit it. Instant | | Trigger | **Response Status Changed** | Starts when a response's status changes, whether a teammate moved it in the inbox, a linked Jira or Linear issue moved it, or the API changed it. **Survey** limits it to one survey. Instant | | Trigger | **Urgent Feedback** | Starts once per response when it becomes urgent, because Usertick AI rated it high urgency or a teammate set it to high. **Feedback types** can limit it. Instant | | Trigger | **Workflow Step** | Starts when a Usertick workflow reaches its Zapier step, so the workflow's conditions decide which responses arrive. **Workflow step** selects the step, listed by the workflow's name and the tool. See [Tools with Zapier](https://docs.usertick.com/integrations/with-zapier.md#send-responses-from-a-workflow). Instant | | Action | **Add Comment to Response** | Adds a comment to a response in your inbox. Your team sees the comment, and the respondent doesn't | | Action | **Update Response** | Changes a response's status, feedback type or urgency. A field left empty keeps its value. For type, **No type** removes the type, and the AI's analysis doesn't set one again. For type and urgency, **Back to AI** undoes a change made by hand, so the AI's analysis applies again | | Search | **Find Response** | Finds the newest response from a respondent's email, optionally in one survey, or a response by its ID. When nothing matches, the Zap can continue on a "nothing found" path | ## Connect **1. Accept the invite** Open the invite link from **Settings → Integrations → Zapier** and accept the invite on Zapier. **2. Select Usertick in a Zap** In the Zap editor, select Usertick as the trigger or action app and sign in, and Zapier opens Usertick in a new window. **3. Allow access in Usertick** Sign in if asked, select the **Organization** and select **Allow access**. **4. Set up the trigger** Select the survey to watch, or for **Workflow Step** the workflow step, then test the trigger, and Zapier shows your latest responses as samples. The organization's owner, or a member whose role has the **Manage integrations** permission, can allow access. The organization must be on the Starter plan or higher, and on the Free plan the page asks for an upgrade first. Zapier then acts with that person's permissions. A step that changes a response or adds a note to it also needs **Manage responses**, and the **Workflow Step** trigger also needs **Manage workflows**. The app can ask only for these permissions: * See your surveys and their questions * See your responses and their AI analysis * Add comments and change status, type and urgency * Send new responses to addresses Zapier sets up In Zapier, the connection is labeled with the organization's name and your email. ## What you can map Every trigger, **Update Response** and **Find Response** return the same response fields. They follow the API's [Response resource](https://docs.usertick.com/developers/api/response-object.md). | Fields | What they hold | | - | - | | **Response ID**, **Response link** | The response, and a link that opens it in your inbox | | **Created at**, **Updated at** | When it arrived, and when it last changed | | **Survey ID**, **Survey name**, **Site** | Where it came from | | **Source**, **Language**, **Country**, **Page URL** | How and where it was given | | **Device type**, **Browser**, **Operating system** | The respondent's device | | **Variant**, **Variant ID** | The name and the ID of the survey variant the respondent saw. Both are empty when the respondent saw no variant | | **Respondent email** | The respondent's email, when there is one | | **Status**, **Assignees: name**, **Assignees: email**, **Comments** | Where it stands in your inbox. **Comments** is the number of comments | | **Answers: question**, **Answers: answer** and more | Every answer as a line item | Files the respondent added, such as screenshots and signatures, aren't included, because a Zap couldn't open their links. **Response link** opens the response, with its files, in your inbox. When a trigger has a survey selected, each of the survey's questions also becomes its own field, numbered and labeled with the question, such as **Q1: How likely are you to recommend us?**. A field keeps its mapping when the question is reworded later. For **Workflow Step**, the questions come from the survey of the step's workflow. The triggers add **Event**: `response.created`, `response.analyzed`, `response.status_changed` or `response.urgent`. For **Workflow Step**, **Event** is the event that started the workflow: `response.created`, `response.analyzed` or `response.urgent`. **Response Status Changed** also returns the change: | Field | What it holds | | - | - | | **Previous status**, **New status** | The status before and after: `open`, `planned`, `in_progress`, `resolved` or `archived` | | **Changed by: kind** | Who changed it: `member` (a teammate), `api_key`, `app` or `integration` (Jira or Linear) | | **Changed by: name**, **Changed by: ID** | The teammate's name and member ID, the key or app, or `jira` or `linear` | A status that Jira or Linear applies starts the Zap. Setting a response to the status it already has starts nothing. **Response Analyzed**, **Response Status Changed**, **Urgent Feedback**, **Workflow Step**, **Update Response** and **Find Response** also return the AI analysis: **AI type**, **AI urgency**, **AI theme**, **AI category**, **AI sentiment**, and **AI values changed by a person**, which is true when a teammate corrected the AI. **Add Comment to Response** returns the comment: its ID, the response ID, the text, when it was written and its author. ## Turn a Zap off Turning a Zap on subscribes it to Usertick, and turning it off removes that subscription. While a Zap is on, its subscription appears in **Settings → Developers → Webhooks**, marked **Added by an app**, with its deliveries. Deleting the subscription there stops the Zap's trigger. When the survey a Zap's trigger watches is deleted, Usertick ends the Zap's subscription, and the Zap stays on in Zapier without starting again. Turning the Zap off and on doesn't bring it back, because Usertick refuses a subscription to a survey it no longer has. To use the Zap again, select another survey in its trigger and publish the Zap. A **Workflow Step** Zap's subscription reads "A workflow's Zapier step" in that list, and its panel links to the workflow with **Open the workflow**. One workflow step sends to one Zap at a time. When the workflow is deleted, Usertick removes the subscription, and the Zap stays on in Zapier without starting again. ## Disconnect Zapier To disconnect Zapier, open **Settings → Integrations → Zapier**, select **Revoke access** on the connection's line under **Connections** and confirm. Zapier loses access immediately, the triggers it added stop, and Zaps that use the connection ask to reconnect. **Connections** lists each connection with the person who connected it, when it was connected, when Zapier last used it and the access it has. Members whose role has the **Manage integrations** or **Manage developer settings** permission can see the list and revoke access. The connection also stops working when the person who connected Zapier leaves the organization or loses the **Manage integrations** permission. Usertick revokes a connection automatically when Zapier doesn't finish connecting within 1 day of the approval, and when the connection hasn't been used for 90 days and has no refresh token that still works. A revoked connection's triggers stop. ## When a step fails | Zapier shows | What it means | | - | - | | "Usertick could not find this survey. It may have been deleted, or it belongs to another organization." | The step names a survey that Usertick doesn't have. Select the survey again | | "This Usertick connection or organization has reached its limit of webhook subscriptions. Turn off a Zap you no longer use, then try again." | Turning a Zap on needs a free subscription. A connection and an organization can each hold 100 subscriptions. Turn off the Zaps that are no longer used | | "Your Usertick plan does not include Zapier. Upgrade to Starter or higher in Usertick, then try again." | The organization's plan doesn't include Zapier, for example after a move to the Free plan. Upgrade to the Starter plan or higher | | "Usertick did not allow this. Reconnect Usertick in Zapier, approve every permission, and check that you can still manage integrations in that organization." | The connection lacks a permission the step needs, or the role of the person who connected it lacks the permission for that step. Reconnect in Zapier and approve every permission, or connect as a member whose role allows the step | | "Your Usertick connection has expired or was removed. Reconnect your Usertick account in Zapier." | The connection was revoked, or the person who connected it left the organization or lost the **Manage integrations** permission. Reconnect in Zapier | | "Usertick did not allow this. Check that you can manage workflows in that organization, or reconnect Usertick in Zapier and approve every permission." | The **Workflow Step** trigger needs the **Manage workflows** permission, and the role of the person who connected Usertick lacks it, or the connection lacks a permission. Connect as a member whose role can manage workflows, or reconnect and approve every permission | | "Usertick needs a workflow step for this trigger. Pick one in the Workflow step field, then try again." | The **Workflow step** field is empty. Select a step | | "Usertick could not find this workflow step. It may have been removed from its workflow, or the workflow was deleted. Pick another step, or add a Zapier step to the workflow in Usertick." | The step is no longer in its workflow, or the workflow was deleted. Select another step, or add the tool's step to the workflow again | | "This Usertick workflow step already sends to another Zap. Turn that Zap off, then turn this one on." | Another Zap is on for the same workflow step. Turn that Zap off, or add a second step to the workflow for this Zap | ## Other tools with Zapier For 62 tools that Usertick doesn't connect to natively, such as Salesforce, Pipedrive and Notion, a workflow can include the tool as a step under **With Zapier**, and the step's **Create the Zap in Zapier** button opens a Zap with the **Workflow Step** trigger and the tool's action already selected. Each tool also has a tile under **With Zapier** in **Settings → Integrations**, whose button opens a Zap with the **New Response** trigger instead. See [Tools with Zapier](https://docs.usertick.com/integrations/with-zapier.md). ## Zapier or a webhook * Zapier fits when the destination is one of the apps Zapier connects to and no code is wanted. * A [webhook](https://docs.usertick.com/integrations/webhooks.md) fits when the destination is your own system, with signed requests, retries and a delivery log. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.