# Clay + Krokul CRM

Yes. Krokul CRM integrates with Clay in both directions. Krokul posts new client companies, contacts and won deals into the Clay tables you choose, and a Clay HTTP API column writes the enriched values back into Krokul custom fields. The Krokul webhooks and API carry both sides, and the Krokul app in Zapier, Make or Albato adds the Clay record actions.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, Albato.

## What your team gets

### Every new client company becomes a Clay row

In the Clay card in Krokul you paste the URL of a table webhook source and tick the event, for example a new client company. Krokul then posts each company as flat JSON with its Krokul ID, name, website and owner, and Clay adds it as a row ready for the enrichment columns of that table.

### An HTTP API column writes results back

The Clay card gives you a ready request for the last column of the table, with the Krokul endpoint, the header with a scoped API key and a JSON body that takes the Krokul ID from the row. When the column runs, the enriched values land in the custom fields of the same client company or contact.

### A people table turns into Krokul contacts

For a table of people built in Clay, the HTTP API column sends each row to the Krokul contact import. Krokul merges it into an existing contact when the phone or e-mail matches and creates a new one otherwise, then reports created, merged and skipped rows to the column.

### Won deals mark the account in Clay

When a deal is won, Krokul posts the client company to a second table webhook source. Your Clay table can then split current clients from prospects and skip them in outbound lists.

## What moves between Clay and Krokul

| Clay | Krokul | Direction | When |
|---|---|---|---|
| Table row (webhook source) | Client company | Krokul → Clay | A client company is created |
| Table row (webhook source) | Contact | Krokul → Clay | A contact is created |
| Table row (webhook source) | Won deal and its client company | Krokul → Clay | A deal is won |
| HTTP API column | Custom fields of the client company or contact | Clay → Krokul | The column runs in the Clay table |
| HTTP API column on a people table | Contact (created or merged) | Clay → Krokul | The column runs in the Clay table |

## How to connect today

### Krokul app in Zapier, Make or Albato

1. Sign in to the Krokul app with a Krokul API key.
2. Start from a Krokul trigger such as Deal Won or Contact Created.
3. Use the Clay action Create Record in Table, or Find Row in Table and then Update Record in Table. Clay offers no triggers there, so the way back runs through an HTTP API column.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with write scopes for client companies and contacts.
2. In Clay, add a table with a webhook source, then register its URL in Krokul with webhook/api-upsert for clientCompany.created or contact.created. The x-crm-delivery header of each call lets a Clay column drop repeated rows.
3. In the last column of the table, set up an HTTP API request to clientCompany/api-update or contact/api-update with the Krokul ID from the row and the enriched values as custom fields.
4. For a people table built in Clay, point the column at contact/api-import instead, so matching rows merge into existing contacts.

**Actions:** Create Record in Table; Update Record in Table; Find Row in Table.

### For integrators

Krokul signs every webhook delivery with HMAC-SHA256 and adds `x-crm-delivery` as a deduplication key, which you can keep in a Clay column to drop repeated rows. For calls from Clay, the Krokul API answers too many requests with 429 and `Retry-After`, so set the request limit of the HTTP API column below your Krokul key limit. Custom field keys stay stable when a label is renamed, so a Clay column mapping does not break.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Clay?

Yes. Krokul integrates with Clay through the Krokul app in Zapier, Make and Albato, and through its API and webhooks. Krokul sends records into Clay tables through webhook sources, and Clay HTTP API columns write enriched values back.

### Do I need Zapier to connect Clay and Krokul?

No. Krokul webhooks fill the Clay table, and a Clay HTTP API column calls the Krokul API, so both directions work without a platform. Zapier and Make help when you want the Clay actions Find Row in Table or Update Record in Table in a custom flow.

### What happens after 50,000 webhook submissions?

Clay stops accepting data on that webhook source, even if you deleted rows. Create a new source and point the Krokul webhook at its URL. Clay documents an auto-delete option on Enterprise plans that lifts this limit.

### Which Krokul records can Clay update?

Client companies and contacts, through their custom fields, and new contacts through the import. Deals, documents and payments stay with your team.

## Limits

Enrichment providers, waterfalls and credits are configured in Clay. Each Clay webhook source accepts at most 50,000 submissions, even after rows are deleted, so a busy table needs a new source after that.

## Related services

- [Apollo.io](https://krokul.com/en/integrations/apollo-io/index.md)
- [ZoomInfo](https://krokul.com/en/integrations/zoominfo/index.md)
- [lemlist](https://krokul.com/en/integrations/lemlist/index.md)
- [Google Sheets](https://krokul.com/en/integrations/google-sheets/index.md)

[Data enrichment](https://krokul.com/en/integrations/category/data-enrichment/index.md)

Clay is a trademark of its owner. Krokul is not affiliated with Clay.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs