# Hunter + Krokul CRM

Yes. Krokul CRM integrates with Hunter. Krokul checks every new contact address with the Hunter Email Verifier, fills job and company data from Hunter enrichment, and lets a manager find the right people at a client company by its domain. Contacts from lost deals can join a Hunter sequence, and replies come back to the deal. The link runs through the Krokul app in Zapier, Make or n8n, or through the Krokul API and webhooks.

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

## What your team gets

### A verified address on every new contact

A manager adds a contact with an e-mail address. Krokul sends it to the Hunter Email Verifier and writes the result on the contact as valid, invalid, accept_all, webmail, disposable or unknown. An invalid address opens a task to correct it before the next quote goes out. Some checks take longer. When Hunter answers 202 because the check is still running, Krokul asks again a little later.

### Company data for a new client company

When a client company with a website is created, Krokul calls Hunter Company Enrichment with the domain. Industry, employee range, founding year and location go into the custom fields you mapped. Your team keeps what it typed.

### The right people at an account

A deal stalls because the buyer went quiet. From the client company card the manager runs Hunter Domain Search on its domain and sees the addresses Hunter knows, each with position, department, seniority and a confidence score. Chosen people become Krokul contacts on the same company. If the manager knows a name, Email Finder returns the most likely address with its score.

### Lost deals go into a Hunter sequence

A deal closed as lost hands its contact to the Hunter sequence you picked for win-back mail. Hunter webhooks for message.replied and message.clicked come back to Krokul and land as activities on that deal. The manager reopens it from the reply.

## What moves between Hunter and Krokul

| Hunter | Krokul | Direction | When |
|---|---|---|---|
| Email Verifier result | Verification status of the contact e-mail | Hunter → Krokul | A contact is created or its e-mail changes |
| Company Enrichment (industry, employees, location) | Custom fields of the client company | Hunter → Krokul | A client company with a domain is created |
| Email Enrichment (job title, seniority) | Custom fields of the contact | Hunter → Krokul | A contact is created |
| Domain Search and Email Finder results | New contacts on the client company | Hunter → Krokul | The manager searches from the card |
| Sequence recipients | Contact of a lost deal | Krokul → Hunter | A deal is lost |
| Webhooks message.replied, message.clicked | Activity on the deal | Hunter → Krokul | The recipient replies or clicks |

## How to connect today

### Krokul app in Zapier, Make or n8n

1. Connect the Krokul app with a Krokul API key and start from Contact Created or Company Created.
2. Add a Hunter step. In Zapier use the searches Verify Email or Find Email, in Make use Find an Email, and in n8n use the Hunter node for domain search, e-mail finder or verifier.
3. Finish with the Krokul actions Update Contact or Update Company.
4. For sequences, start from the Krokul trigger Deal Lost with Create Recipient in Zapier or Add Recipients in Make, and send Email Replied back to the Krokul action Add Activity.

### Custom flow through the Krokul API and webhooks

1. Copy your Hunter API key and create a Krokul API key scoped to contacts, client companies and activities.
2. Subscribe a Krokul webhook to contact.created and clientCompany.created, check x-crm-signature and use x-crm-delivery so a retried delivery spends no second lookup.
3. Call the Hunter Email Verifier or Company Enrichment and write the result with contact/api-update or clientCompany/api-update.
4. Register a Hunter webhook for message.replied with a long random token in its URL path, then record each reply with activity/api-create.

**Triggers:** Email Read; Email Replied; New Campaign; New Lead; Watch Campaigns.

**Actions:** Create Recipient; Create Lead; Find Email; Verify Email; Count Email; Add Recipients; Find an Email.

### For integrators

Hunter accepts the key as an api_key parameter, an X-API-KEY header or a bearer token, and the value test-api-key returns sample answers for Domain Search, Email Finder and Email Verifier. Webhook requests from Hunter carry no signature. A secret token in the target URL does that job. Krokul brings a REST API, signed webhooks with a delivery log, external keys and a sandbox company for mapping tests.

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

## Questions and answers

### Does Krokul integrate with Hunter.io?

Yes. Krokul integrates with Hunter through the Krokul app in Zapier, Make and n8n and through its API and webhooks, for e-mail verification, enrichment, people search and sequences.

### Does a failed search cost Hunter credits?

Hunter charges no credit when Email Finder finds no address, and it counts a Domain Search only when at least one result comes back.

### Which verification statuses does Krokul store?

The six statuses Hunter returns, which are valid, invalid, accept_all, webmail, disposable and unknown. Krokul keeps the status and the check date on the contact.

### Do Hunter sequence replies reach Krokul?

Yes. Hunter sends webhooks for message.sent, message.read, message.clicked and message.replied, and Krokul records them as activities on the deal of that contact.

## Limits

Hunter sends sequence e-mails from the mailbox connected in Hunter, and the message history stays there. Each lookup draws on the Hunter quota of your plan, and Hunter limits Domain Search and Email Finder to 15 requests per second and 500 per minute.

## Related services

- [Apollo.io](https://krokul.com/en/integrations/apollo-io/index.md)
- [Lusha](https://krokul.com/en/integrations/lusha/index.md)
- [Clay](https://krokul.com/en/integrations/clay/index.md)
- [ZoomInfo](https://krokul.com/en/integrations/zoominfo/index.md)
- [lemlist](https://krokul.com/en/integrations/lemlist/index.md)

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

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

Updated: 2026-10-15

---

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