Find Email
find_emailCosts 1 Sliq credit per verified email; a BYO-Apollo key makes the Apollo
leg free. The default chain runs MoltSets first and fills its misses with
Apollo, so a contact that comes back {'error': ...} has been tried by both
providers and is final — report those gaps and move on rather than
re-running them.
When only one provider ran — a BYO-Apollo user's default, or an explicit 'apollo' pin — the other is still untried, and the result says so. That paid lookup is the user's call: in a background run with no one to answer, report how many were missed and stop; in an interactive chat, tell them the count and offer a MoltSets backfill (1 credit/hit), re-calling with provider='moltsets' on just those contacts only after they say yes.
A contact this user already resolved in the last 24h is served from a cache,
so re-calling does not look up or charge again.
One entry per input contact, in input order — either a hit dict
(email, email_status, name, title, linkedin_url) or an
{'error': ...} miss — followed by any warnings.
Each verified email is also written for you onto the person's canonical profile (the Email column on the Output tab) and onto their prospect row in your campaigns if it had none — you do not match or persist emails back onto rows yourself.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contacts | Yes | People to look up. Each must have name plus at least one of linkedin_url, company_name, or company_domain. | |
| provider | No | Leave unset (default) to let the chain pick — almost always right; don't pin a source the user didn't ask for. Set 'apollo' or 'moltsets' to pin a single source: 'apollo' runs Apollo alone (free with BYO Apollo, 1 credit/hit on Sliq's key); 'moltsets' runs MoltSets alone (1 credit per hit). Use 'moltsets' for the backfill the user approved after a run where only Apollo went out. Pinning skips the fallback, so coverage may be lower. |