How Conversion works with Clay
Conversion connects to Clay through webhooks and the Conversion API, so any workflow can send contacts to Clay and get enriched data back. An HTTP Request step posts each contact to a Clay webhook table, and once Clay's enrichments finish, an HTTP API call in Clay writes the results onto Conversion contact and company fields through the Upsert Contact endpoint. It is a documented recipe built on the same public API your own systems use, so you decide exactly which fields go out and which come back.
What you can do
Enrichment from any workflow
Add the HTTP Request step wherever enrichment belongs, and the workflow's trigger decides who goes to Clay, such as new form submissions or members of an audience.
Only the fields Clay needs
The request body is JSON with Liquid variables you write, so nothing leaves Conversion unless you list it.
Write-back that respects your data
Set preserveExistingFields to true and Clay fills empty fields without replacing values your team already trusts.
Built on the public API
Results arrive through the same Upsert Contact endpoint your own systems can call, authenticated with a Conversion API key stored in a Clay header account.
What syncs
| Data | Direction | Details |
|---|---|---|
| Contacts sent to Clay | Out of Conversion | An HTTP Request step or saved webhook posts the fields you choose, such as email and name, to a Clay webhook as JSON. |
| Enrichment results | Into Conversion | Clay calls the Upsert Contact endpoint with contact fields and company fields keyed to your Conversion field keys. |
How to connect Clay
- 1 In a Clay workbook, add a Monitor webhook source and copy the URL it generates.
- 2 In Conversion, add an HTTP Request step to a workflow, set the method to Post, and send the contact fields Clay needs in the JSON body.
- 3 As a Conversion Administrator, create an API key under Settings > Integrations and save it in Clay as an HTTP header account with the key X-API-Key.
- 4 Add an HTTP API enrichment in Clay that posts to https://pub-api.conversion.ai/api/v2/contacts, mapping Clay columns to your Conversion field keys.
- 5 Test with one contact end to end, then widen the workflow trigger to the contacts you want to enrich.
