AeroLeads MCP integration for AI agents.
Connect AI agents to AeroLeads through 1 structured actions, including get details from linkedin url. Review authentication, inputs, workflows, and safety gu…
- ACTION CONTRACTS
- 1
- 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 AeroLeads integration exposes
The AeroLeads Agent App exposes 1 provider-backed actions for marketing and data work. Its current contract lets an authorized agent retrieve prospect details, emails, phone numbers, company, education, skills, and related profile data from a public linkedin profile url using aeroleads. 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 AeroLeads account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AeroLeads capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_details_from_linkedin_urlREADRetrieve prospect details, emails, phone numbers, company, education, skills, and related profile data from a public LinkedIn profile URL using AeroLeads.
INPUTS: linkedin_url
INPUT CONTRACTS
Know what the action needs before it runs.
get_details_from_linkedin_url
linkedin_urlREQUIRED- Public LinkedIn profile URL for the prospect, such as https://www.linkedin.com/in/example.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Details From Linkedin Url
Retrieve prospect details, emails, phone numbers, company, education, skills, and related profile data from a public LinkedIn profile URL using AeroLeads. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_details_from_linkedin_urlVerify with Get Details From Linkedin Url
Retrieve prospect details, emails, phone numbers, company, education, skills, and related profile data from a public LinkedIn profile URL using AeroLeads. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_details_from_linkedin_urlSAFETY BOUNDARY
Operate AeroLeads with explicit limits
- Authorize AeroLeads with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned AeroLeads 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 AeroLeads rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AeroLeads task completed successfully.
CONNECTION MODEL
API key
AeroLeads API key sent as the api_key query parameter for LinkedIn and email lookup APIs. Find it in AeroLeads Settings under API Key after signing in: https://aeroleads.com/users/settings#api_key.
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
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 AeroLeads.