Overview
Add Icypeas to any ModuleX agent or workflow. Find and verify professional email addresses against the Icypeas REST API (app.icypeas.com). Resolve a likely professional email from a person’s name and company domain, or check whether an existing address is valid and deliverable. Both operations run asynchronously: a job is submitted, then the result is fetched by polling.
Categories: Sales · Enrichment · Sales Engagement · Auth: API Key · Actions: 2
Authentication
API Key Authentication
Authenticate using your Icypeas API keyStep 1
Go to https://app.icypeas.com and sign up or log in
Required Credentials
| Field | Description | Required | Format |
|---|---|---|---|
| Icypeas API Key | Your Icypeas API key from app.icypeas.com | Yes | - |
Available Actions
find_email — Find a professional email address from a first name, last name, and company domain or name. Submits the search and polls until a result is available.
find_email — Find a professional email address from a first name, last name, and company domain or name. Submits the search and polls until a result is available.
verify_email — Verify whether an email address is valid and deliverable. Submits the verification and polls until a result is available.
verify_email — Verify whether an email address is valid and deliverable. Submits the verification and polls until a result is available.
Limits & Quotas
- Async polling: each call submits a job, then polls the read
endpoint roughly every 3 seconds for up to 120 seconds. If the job
does not reach a terminal status in that window, the call returns
success=Falsewith an explanatory error. - Terminal statuses:
FOUND,DEBITED,NOT_FOUND,DEBITED_NOT_FOUND,BAD_INPUT,INSUFFICIENT_FUNDS,ABORTED. A clean no-match (NOT_FOUND) is still a successful run —emailis simplynulland, for verification,validisfalse. - Rate limits: approximately 60 requests/minute.
- Pricing (approx., per vendor pricing page): email finding ~1 credit per found email; email verification ~0.1 credit per check.
- Error model: non-2xx responses and timeouts are caught and
returned as
success=False+errorrather than raising. Plan for retries on the agent side based on the error string.