ReachOut + Zapier

Connect ReachOut to anything Zapier supports — no code.

Why this matters

ReachOut's REST API makes it a clean Zapier action. Use a Webhooks (by Zapier) action with a bearer token to call the project API from any Zap: create contacts from form submissions, or update their custom fields when something changes upstream.

What you get

  • No native Zapier app required — the Webhooks (by Zapier) action calls the REST API directly.
  • The API key only reaches the projects it is granted.
  • Standard fields (email, firstName, lastName, company, role) and your custom fields map directly to Zapier inputs.
  • Contacts are not deduplicated on create; clean up retries with Contacts → Deduplicate.

Setup in 4 steps

  1. Pick a trigger.In Zapier, choose any trigger app (Typeform, Webflow, Airtable, etc.). Map the data fields you want to pass to ReachOut.
  2. Add a Webhooks (by Zapier) action.Action type: POST. URL: https://api.usereachout.com/api/projects/YOUR_PROJECT_ID/contacts (list project IDs with GET /api/projects). Add Authorization: Bearer YOUR_API_KEY header.
  3. Map fields.Body: { "email": "{{email}}", "firstName": "{{first}}", "lastName": "{{last}}" }. Custom fields go under "customFields" and must exist in Studio → Contacts → Schema first.
  4. Test and turn on.Run the test trigger; verify the contact appears in Studio → Contacts. Turn the Zap on.

Other integrations