Zapier can connect AfterCheck to the systems that create customer follow-up opportunities or need feedback updates, such as CRM, POS, booking, helpdesk, email, and reporting tools.

What Zapier can do

Use Zapier when another system needs to:

• create a tracked feedback request after a customer experience
• list campaigns for a setup dropdown
• trigger from new feedback responses
• trigger from Needs attention feedback
• subscribe to AfterCheck webhook events

API key scopes

Create an AfterCheck API key from API Keys. For most Zapier setups, use these scopes:

```text campaigns:read responses:read requests:write webhooks:write ```

Add `requests:read` only if the Zap needs to list tracked requests. Add `actions:read` only if the Zap needs configured next-action links.

Zapier authentication test

Zapier should test the API key with:

```text GET /api/v1/me ```

This endpoint verifies the key and returns the connected organization without requiring a campaign or response to exist first.

Useful endpoints

Use `GET /api/v1/campaigns?status=active` for a campaign dropdown.

Use `POST /api/v1/feedback-requests` when a Zap creates a customer, order, job, ticket, appointment, or invoice-specific feedback link.

Use `GET /api/v1/zapier/responses?sample=true` for Zapier polling trigger setup samples. This endpoint returns a root JSON array, which is the shape Zapier expects for polling triggers.

Use `GET /api/v1/zapier/responses?sentiment=negative&created_after=...` for Needs attention-style polling triggers.

The general `GET /api/v1/responses` endpoint returns `{ data, total }`. If a custom Zapier code trigger calls it directly, return the `data` array to Zapier rather than the whole response object.

Use `POST /api/v1/zapier/subscriptions` and `DELETE /api/v1/zapier/subscriptions/{subscriptionId}` for REST Hook subscribe and unsubscribe.

Webhook events

Zapier REST Hooks can subscribe to the same customer webhook events as the AfterCheck webhook endpoint surface:

• `response.created`
• `response.needs_attention`
• `response.sentiment_changed`
• `response.status_changed`
• `feedback_request.created`
• `feedback_request.responded`
• `feedback_request.expired`
• `action_destination.clicked`

AfterCheck keeps all customer feedback private inside the workspace and any systems you connect. Public review links are not routed by sentiment.