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.
Automation platformsZapierMakeAlbato
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.
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.
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.
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.
| Clay | Direction | Krokul | When |
|---|---|---|---|
| Table row (webhook source) | Krokul → Clay | Client company | A client company is created |
| Table row (webhook source) | Krokul → Clay | Contact | A contact is created |
| Table row (webhook source) | Krokul → Clay | Won deal and its client company | A deal is won |
| HTTP API column | Clay → Krokul | Custom fields of the client company or contact | The column runs in the Clay table |
| HTTP API column on a people table | Clay → Krokul | Contact (created or merged) | The column runs in the Clay table |
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.
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.
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.
Client companies and contacts, through their custom fields, and new contacts through the import. Deals, documents and payments stay with your team.
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.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Clay is a trademark of its owner. Krokul is not affiliated with Clay.