Clay

Clay is the data-enrichment and prospecting tool many GTM teams use to source and qualify accounts before sales takes them. Sonora’s Clay integration is the bridge for the moment a Clay-managed account becomes a Sonora customer — typically when a deal closes — and post-sales takes over.

Unlike the read-only connectors, Clay sends data into Sonora over a webhook. You configure an HTTP action column in your Clay table that fires when an account is ready to hand off.

What gets created in Sonora

Each webhook payload creates or updates a Sonora customer with the fields you map. Standard mappings:

Sonora field	What it is
name	Company name (required)
websiteUrl	Company website (required)
owner	Account owner — resolves to a Sonora user by name
ownerEmail	Alternative owner field — resolves by email instead
stage	Customer stage in Sonora
arr	Annual recurring revenue
renewalDate	Renewal date

The same fields can be set during onboarding from your CRM. Clay is for the case where the account isn’t in your CRM yet — it lives in Clay and needs to be promoted into Sonora directly.

Setup

1. Generate a webhook URL and bearer token in Sonora

1. Settings → Integrations → Clay → Connect.
2. Click Connect. Sonora generates a webhook URL and a bearer token.
3. Copy the bearer token. This is the only time Sonora will display it — store it in Clay before closing the dialog.

2. Add an HTTP action column in Clay

In the Clay table that holds your accounts:

1. Add an HTTP action column.
2. Method: POST. URL: the Sonora webhook URL.
3. Add header: Authorization: Bearer <token> (using the token from step 1).
4. Body: a JSON payload mapping your column names to Sonora fields. Sonora’s setup dialog includes a copyable template — adjust the placeholders to match your column names:

   {
     "name": "{{Company Name}}",
     "websiteUrl": "{{Domain}}",
     "owner": "{{Account Owner}}",
     "stage": "{{Status}}",
     "arr": "{{ACV}}",
     "renewalDate": "{{Renewal Date}}"
   }

5. Configure the column’s trigger condition — typically something like Status = "Closed Won".

When the trigger fires, Clay sends one POST per row, and Sonora creates or updates the matching customer.

3. Test

Trigger the action on a single test row before turning it on for the table. Sonora returns a clear success or error response per request, which Clay surfaces in the action column.

Regenerating the token

Lost the original token? Open the Clay card in Sonora and click Regenerate token. The old token is invalidated immediately; update the bearer header in your Clay action column with the new value.

Disconnect

From Settings → Integrations, click Disconnect on the Clay card. The token is revoked; any further webhook requests return 401.

Troubleshooting

Clay action column shows 401 — Either the bearer token is wrong or it has been regenerated/revoked. Update the column header to use the current token.

Customer isn’t appearing in Sonora — Check the request body in Clay’s action column logs. Both name and websiteUrl are required; missing or empty values cause the request to be rejected with a 400.

Wrong owner assigned — owner resolves by display name. If two Sonora users share a name, switch to ownerEmail instead, which resolves uniquely.