# Connect Pollenate workflows to Zapier > Use Pollenate triggers and actions, or send events to a Catch Hook with explicit scope and privacy rules. Canonical URL: https://pollenate.dev/docs/integrations/zapier/ ## Two connection options If the Pollenate integration is available in your Zapier workspace, connect it using an organization API key. You can also use a Webhooks by Zapier Catch Hook as the target of a Pollenate [webhook automation](/docs/integrations/webhooks/). The integration supports new inbox feedback and new form-response triggers, feedback submission, feedback lookup and follow-up actions. The deployed app/version in your Zapier workspace determines which actions are available; the API contracts below are the underlying behavior. ## Select a credential Use an organization key, not a personal key or an MCP OAuth token. Requests to `https://api.pollenate.dev/zapier` authenticate with `X-Pollenate-Key`. Use `read` for reading data, `write` for creating webhook subscriptions and follow-up actions, and `collect` or `write` for submitting feedback. An organization `admin` key has broader access but is usually unnecessary. A trigger that installs a REST hook needs `write`, not just read access. ```bash curl https://api.pollenate.dev/zapier/auth/test \ -H "X-Pollenate-Key: $POLLENATE_ZAPIER_KEY" ``` If authentication fails, check the key's organization, expiry and revocation status before rebuilding the Zap. ## Underlying endpoints | Endpoint | Purpose | | --- | --- | | POST `/hooks` | Subscribe a hook URL to `feedback.created` or `page_response.created` | | DELETE `/hooks/HOOK_ID` | Remove a subscription | | GET `/feedback` | Read recent feedback with supported filters | | GET `/feedback/search?q=…` | Find matching feedback | | GET `/feedback/FEEDBACK_ID` | Read one event | | POST `/feedback` | Submit an event using `inboxId` or `inboxKey` | | PATCH `/feedback/FEEDBACK_ID` | Set external tracker fields | | POST `/feedback/FEEDBACK_ID/notes` | Add a follow-up note | | GET `/inboxes`, `/brands` | Populate setup choices | | GET `/pages`, `/page-responses` | Read eligible published pages and recent form responses | An optional inbox and filters narrow feedback hooks. Form-response hooks use organization scope and can filter by `pageId`. Private forms and their responses are excluded from organization-key page listings and automation fan-out. ## Catch Hook workflow 1. Create a Zap with a Catch Hook trigger and copy its URL. 2. Create a Pollenate webhook rule for the desired inbox/event. 3. Paste the Catch Hook URL as the target. 4. Use the rule's Test action to send a synthetic payload. 5. Map the fields in Zapier, then verify with an intentional submitted response. A test can trigger downstream actions; use sample destinations first. Match the event shape: inbox feedback has `feedbackId`, `type`, `score` and `comment`; a form response has `responseId` and per-question `answers`. Feedback “sentiment” filters are score-based thumbs shorthand, not model-generated sentiment. NPS category filters use the NPS score thresholds. Missing events may come from a paused rule, a scope mismatch, a filter that excludes the event, or private-form restrictions. For a critical workflow, monitor both the Pollenate delivery result and Zapier's task history. Do not assume a test payload proves every production event will be delivered or retried.