A-Leads MCP integration for AI agents.
Connect AI agents to A-Leads through 4 structured actions, including find email, verify email, and find personal email. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the A-Leads integration exposes
The A-Leads Agent App exposes 4 provider-backed actions for marketing and data work. Its current contract lets an authorized agent find a business email address from a person's name and company website or a-leads document id, verify an email address and return deliverability signals from a-leads, and find a personal email address from a linkedin username or profile url. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected A-Leads account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real A-Leads capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_emailREADFind a business email address from a person's name and company website or A-Leads document ID.
INPUTS: first_name / last_name / website / document_id / request_uuid
verify_emailREVIEWVerify an email address and return deliverability signals from A-Leads.
INPUTS: email
find_personal_emailREADFind a personal email address from a LinkedIn username or profile URL.
INPUTS: linkedin_username / request_uuid
find_phoneREADFind a phone number from a LinkedIn username or profile URL.
INPUTS: linkedin_username / request_uuid
INPUT CONTRACTS
Know what the action needs before it runs.
find_email
first_nameOPTIONAL- First name of the person.
last_nameOPTIONAL- Last name of the person.
websiteOPTIONAL- Company website or domain.
document_idOPTIONAL- Unique document ID from A-Leads advanced search results.
request_uuidOPTIONAL- A unique ID linked to the search request for tracking in A-Leads.
verify_email
emailREQUIRED- Email address to verify.
find_personal_email
linkedin_usernameREQUIRED- LinkedIn profile URL or username of the person.
request_uuidOPTIONAL- A unique ID linked to the search request for tracking in A-Leads.
find_phone
linkedin_usernameREQUIRED- LinkedIn profile URL or username of the person.
request_uuidOPTIONAL- A unique ID linked to the search request for tracking in A-Leads.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Email
Find a business email address from a person's name and company website or A-Leads document ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_emailVerify with Find Personal Email
Find a personal email address from a LinkedIn username or profile URL. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
find_personal_emailSAFETY BOUNDARY
Operate A-Leads with explicit limits
- Authorize A-Leads with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned A-Leads data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in A-Leads rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the A-Leads task completed successfully.
CONNECTION MODEL
API key
A-Leads API key sent with the x-api-key header. Create or view it in your A-Leads account, and see the API docs at https://docs.a-leads.co/docs.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by A-Leads.