Yes. Krokul CRM integrates with Lusha. A new contact in Krokul is matched in Lusha and receives job title, work email, direct phone and LinkedIn URL in the fields you map, and a new client company gets industry, headcount and revenue range. Lusha signals about a promotion or a move to another company open a task for the account manager. The Krokul app in Zapier, Make, n8n and Albato runs enrichment, and the Krokul API with webhooks carries the signals.
Automation platformsZapierMaken8nAlbato
A manager saves a contact with a name and a company domain, or only a work email. The connector sends it to Lusha Enrich Contacts and writes job title, email, direct phone and LinkedIn URL into the custom fields you chose. One contact is enriched once. A repeated save of the same card spends no second credit.
When a client company appears in Krokul, its domain goes to Lusha Enrich Companies. Industry, location, employee count and revenue range land in the company fields, so segment rules and pipeline filters work from the first day without manual research.
Krokul subscribes enriched contacts to Lusha signals. A promotion signal brings the new title and the date of the change. Krokul updates the job title on the contact and creates a task for the account manager to congratulate the person and check whether their buying role changed.
The companyChange signal reports that a known contact now works elsewhere, with the previous and current company. Krokul adds a comment to the old client company and opens a new deal for the new employer, assigned to the manager who knew the person.
| Lusha | Direction | Krokul | When |
|---|---|---|---|
| Contact (Enrich Contacts) | Lusha → Krokul | Custom fields of the contact | A contact is created or the manager asks for a refresh |
| Company (Enrich Companies) | Lusha → Krokul | Custom fields of the client company | A client company is created or refreshed |
Subscription (entityType contact) | Krokul → Lusha | Enriched contact | After the first enrichment |
Signal promotion | Lusha → Krokul | New job title and a task for the manager | Lusha detects a promotion |
Signal companyChange | Lusha → Krokul | Comment on the old company and a new deal for the new one | Lusha detects a job move |
| Company signals (headcount, hiring) | Lusha → Krokul | Comment in the client company feed | A subscribed company changes |
Yes. Krokul integrates with Lusha through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Contacts and client companies get Lusha data, and Lusha signals create tasks.
For contacts, promotion and companyChange. For client companies, Krokul can subscribe to company signals such as headcount growth or a surge in hiring and post them to the company feed.
No. Lusha charges a signal once, when it is first delivered, and Krokul skips repeated Krokul deliveries by x-crm-delivery before calling Lusha.
Only in the fields you allow. Lusha values go into mapped custom fields, and the name, email and phone your team entered stay unless you choose otherwise.
Lusha holds the data and the credit balance. Revealing emails and phone numbers spends Lusha credits, and a 402 response from Lusha means the balance is empty, so Krokul pauses enrichment until the account is topped up.
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.
Lusha is a trademark of Lusha Systems Inc. Krokul is not affiliated with Lusha.