Why this matters
ReachOut's REST API and webhook events make it a clean Zapier endpoint. Use a Webhooks (by Zapier) action with a bearer token to call any REST method, or use Webhooks triggers to fire Zaps when ReachOut events fire (campaign sent, contact created, segment resolved).
What you get
- No native Zapier app required — REST + webhooks cover every common workflow.
- Bearer-token auth scopes Zaps to a single ReachOut organization.
- Standard fields (email, firstName, lastName, custom attributes) map directly to Zapier inputs.
- Idempotency keys supported — duplicate Zap retries don't double-send.
Setup in 4 steps
- Pick a trigger. In Zapier, choose any trigger app (Typeform, Webflow, Airtable, etc.). Map the data fields you want to pass to ReachOut.
- Add a Webhooks (by Zapier) action. Action type: POST. URL: https://reachout-pulse-api.usereachout.com/api/contacts. Add Authorization: Bearer YOUR_API_KEY header.
- Map fields. Body: { "email": "{{email}}", "firstName": "{{first}}", "lastName": "{{last}}" }. Optional: add an Idempotency-Key header so Zap retries are safe.
- Test and turn on. Run the test trigger; verify the contact appears in Studio → Contacts. Turn the Zap on.