Yes. Krokul CRM integrates with Apollo.io for enrichment and for sequences. A new contact or client company in Krokul is matched in Apollo and receives job title, industry or headcount in its custom fields, and a contact from a lost or paused deal can be enrolled in an Apollo sequence from the card or by a rule. The Krokul app in Zapier, Make, n8n and Albato carries these flows, and the Krokul API with webhooks covers custom ones.
Automation platformsZapierMaken8nAlbato
A manager adds a client company with a corporate e-mail. The connector sends the domain to Apollo Organization Enrichment and writes industry, employee count and annual revenue into the custom fields you mapped. Apollo charges one credit per organization, and the connector calls it once per company, so a repeated save does not spend a second credit.
For a new contact, Krokul sends the e-mail and name to People Enrichment. Apollo returns the person with a match_confidence value, and the connector writes the job title and LinkedIn URL only for a high or medium match. When you ask for a phone number, Apollo reveals it later at a callback URL that the connector registers, and the number lands on the same contact.
When a deal closes as lost, a rule in Krokul takes its contact, finds or creates the matching Apollo contact and adds it to the sequence you picked, together with the sending mailbox. A comment on the deal records the sequence name, so the next manager knows the person is in an Apollo cadence.
The contact card has an action that enrolls the person in an Apollo sequence. Apollo enrolls only saved contacts, so the connector first saves the person there and stores its ID as an external key of the Krokul contact. Later enrollments reuse that ID.
| Apollo.io | Direction | Krokul | When |
|---|---|---|---|
| Organization (Organization Enrichment) | Apollo.io → Krokul | Custom fields of the client company | A client company is created or the manager asks for a refresh |
| Person (People Enrichment) | Apollo.io → Krokul | Custom fields of the contact | A contact is created or the manager asks for a refresh |
| Phone reveal (callback) | Apollo.io → Krokul | Phone of the contact | Apollo finishes the asynchronous phone lookup |
| Contact ID | Apollo.io → Krokul | External key of the contact | The Apollo contact is found or created |
| Sequence (add contact IDs) | Krokul → Apollo.io | Contact of a deal | A deal is lost, reaches a chosen stage, or the manager enrolls the contact |
Yes. Krokul integrates with Apollo.io through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Both paths cover enrichment and sequence enrollment.
Apollo documents 1 credit per organization for Organization Enrichment and 1 to 9 credits per person for People Enrichment, depending on whether a mobile phone is returned. A request that finds no paid data costs 0 credits.
No. Apollo documents no outbound webhooks for sequence activity, so replies and opens stay in Apollo. Krokul records the enrollment as a comment on the deal.
Only the fields you allow. Apollo data goes into the custom fields you mapped, and the name, e-mail and phone that your team entered stay as they are unless you choose otherwise.
Apollo.io sends the sequence e-mails, and its replies and opens stay in Apollo, because Apollo documents no outbound webhooks for sequence activity. Every enrichment call spends Apollo credits according to the Apollo pricing of your workspace.
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.
Apollo.io is a trademark of Apollo.io. Krokul is not affiliated with Apollo.io.