Skip to main content
Human guide: work with your agent → Inspect one Findymail action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use Findymail for verified B2B email lookup, email verification, phone lookup, company enrichment, similar-company discovery, technology lookup, and Intellimatch lead-list workflows.
  • Prefer findymail_find_from_name when you have a person name plus company domain.
  • Prefer findymail_find_from_business_profile or findymail_reverse_email_lookup when the input is a LinkedIn/profile URL or an existing email.
  • Use findymail_search_technologies before findymail_lookup_technologies_by_domain when the caller wants to filter by a technology name.
  • Intellimatch is asynchronous: call findymail_search_leads, poll findymail_get_export_status, then retrieve rows with findymail_get_results.
  • Mutating list, exclusion-list, and signal-monitor operations require the caller’s own Findymail credential so agents do not mutate the shared provider account.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.