Skip to main content
Usertick sends webhook events to an endpoint you host as they happen. Every delivery is signed the Standard Webhooks way, failed deliveries are retried, and Usertick keeps every attempt for 30 days. Webhooks are available on the Starter plan and above.

Events

The events an endpoint can receive and the body each one carries.

Verify signatures

Confirm that a delivery came from Usertick, in Node and Python.

Delivery and retries

Timeouts, retries, the delivery log, resending and failure alerts.

Rotate a secret

Switch to a new signing secret without missing a delivery.

​
Ways to receive events

An endpoint is a URL with a signing secret. Endpoints are listed under Settings → Developers → Webhooks, and responses reach them in three ways:
  1. Workflows. On the Workflows page, a workflow for one survey can include a Send to a webhook step that sends the survey’s responses to an endpoint. The workflow starts When a response is submitted, After AI analysis or When a response becomes urgent, and its Only if conditions and If / else steps can limit it to the responses that match.
  2. Survey events, from Settings. In an endpoint’s Survey events settings, Surveys set to All surveys, including new ones or Only selected surveys sends one event, such as After AI analysis or When it becomes urgent, from those surveys. It can be limited to some feedback types, urgencies and themes.
  3. From your code or an app. POST /webhooks/subscribe subscribes a URL to one of the response and AI events, from one survey or every survey, or to a workflow’s Zapier step, which receives the responses the workflow sends to it. Apps such as Zapier subscribe the same way when a Zap is turned on.
The dashboard steps are in Webhooks. An endpoint created in Settings can also receive optional account notifications, such as a member joining or a plan change. See Account notifications.

​
What a delivery contains

Every survey event is an envelope of four keys: These four keys stay the same within v1. A full payload is on the events page. Account notifications and test pings use their own bodies, described on the same page. To avoid timeouts, answer with any 2xx quickly and do the work afterward. Timeouts and retries are described in Delivery and retries.

​
Who can manage webhooks

Anyone whose role has the View surveys and results permission and opens all surveys can see endpoints and their delivery logs. A role with Only selected surveys doesn’t see them. Creating, changing, testing, resending and deleting require the Manage integrations permission.