I’m building a B2B lead-generation workflow in n8n and I’m looking for an alternative to Apollo for people enrichment.
What I’m trying to do is provide basic information such as a person’s name, company/domain, or LinkedIn profile and get back their professional/work email and other available B2B information through an API.
I’m specifically looking for a tool that:
Offers free API credits for testing
Doesn’t require a corporate/work email just to access the API
Can enrich people and find verified work emails
Has a straightforward REST API that I can connect to n8n using the HTTP Request node
Is suitable for a small personal/learning project
I’ve looked at a few Apollo alternatives, but I’d really appreciate recommendations from people who have actually used these APIs with n8n.
What free or free-credit tools would you recommend for this use case?
Naming one without a hands on comparison would be guesswork. Use the free credits to run the same test against each API before letting any returned address enter the rest of the workflow.
Build a labelled set of 20 to 30 cases whose expected outcome you already know and are allowed to use. Include people with known current work addresses, cases where no current work email should be found, catch all domains, and incomplete inputs. Send the same inputs to every API and keep each raw response.
Score precision and coverage separately. Precision is the share of returned addresses that are correct. Coverage is the share of the whole test set that produced a correct address. Also count wrong addresses, no results, request errors, rate limits, and credits used per correct result. This is a pilot, not proof of general accuracy.
In n8n, put an Edit Fields node after the HTTP Request node and map every response into fields you control: email, result_status, source_status, verification_method, checked_at, and error. Store unknown when the API omits a detail. Then use a Switch node to route verified to review, uncertain and catch_all to separate validation, not_found to stop, and request_error or rate_limited to the failure path.
Do not send directly from a result labelled verified. That label can mean different checks, and a mailbox that accepts mail may still belong to the wrong person. Repeated invalid addresses can create hard bounces and hurt deliverability.
Keep no result as an explicit status instead of an empty field, and do not turn an API error into not_found. Once every API maps into the same fields, you can change the enrichment step without rebuilding the rest of the workflow.