How Conversion works with Zapier
Conversion connects to Zapier through the Conversion API, so any Zap can create or update contacts in Conversion. A Webhooks by Zapier Custom Request step posts to the contacts endpoint with your API key, mapping values from earlier steps onto contact fields and, if you choose, a marketing subscription status. Because it runs on the documented public API, there is no separate Zapier app to install or keep up to date.
What you can do
Contacts from any Zap
Whatever app starts the Zap, its last step can create or update a Conversion contact with values mapped from earlier steps.
Any contact field
The fields object accepts any contact field key in your workspace. Set Unflatten to Yes so Zapier sends it as a nested object.
Consent in the same request
Include subscriptionStatus to record whether the contact opted in to marketing email, or leave it out to keep their current status.
Workflows take it from there
New contacts can start workflows through the Contact is created trigger, and updated fields can fire Field is changed triggers.
What syncs
| Data | Direction | Details |
|---|---|---|
| Contacts | Into Conversion | Created or updated by email, with values for any contact field configured in your workspace. |
| Subscription status | Into Conversion | Optional. SUBSCRIBED, UNSUBSCRIBED, or NO_STATUS records the contact's marketing opt-in. |
How to connect Zapier
- 1 In Conversion, create an API key and name it after the Zap that uses it, such as Zapier + Lead Capture Form.
- 2 Add a Webhooks by Zapier action with the Custom Request event, method POST, and the URL https://pub-api.conversion.ai/api/v2/contacts.
- 3 Add the X-API-Key and Content-Type: application/json headers, and set Unflatten to Yes.
- 4 Paste a JSON body with email, fields, and an optional subscriptionStatus, then map values from earlier steps.
- 5 Run Zapier's test and confirm a 200 response that includes a cnvContactId.
