Server Details
Apollo->Salesforce Lead mapper. No LLM. Strict-fail required fields. PASS/REPAIR/FAIL verdict.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
1 toolapollo_to_salesforce_leadInspect
Maps an Apollo contact payload to a Salesforce Lead object. Accepts the full Apollo CSV export column set. Strict-fail if FirstName, LastName, or Phone cannot be resolved. All other Salesforce fields are populated when source data is present, silently omitted otherwise. Returns a Deterministic Receipt (task_id, verdict, confidence, diff[]) embedded in every non-FAIL response.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | Alternate ZIP key → PostalCode. | |
| cell | No | Primary phone (legacy key). Accepts E.164, 10-digit US, formatted strings. | |
| city | No | City → City. | |
| No | Contact email → Email. | ||
| phone | No | Apollo 'Phone' column — alternate primary phone key. | |
| state | No | State / province → State. | |
| title | No | Job title → Title. | |
| source | No | Apollo 'Source' column → LeadSource. | |
| street | No | Street address → Street. | |
| company | No | Company name → Company. | |
| country | No | Country → Country. | |
| website | No | Company website → Website. | |
| headline | No | LinkedIn headline captured by Apollo → Description. | |
| industry | No | Industry → Industry. | |
| keywords | No | Apollo keywords/tags → Description. | |
| No | Alternate LinkedIn key → LinkedIn__c. | ||
| employees | No | Alternate employees key. | |
| full_name | No | Full name — must have ≥2 whitespace-separated tokens. Use this OR provide first_name + last_name. Example: 'Jane Doe' | |
| job_title | No | Apollo 'Job Title' column → Title. | |
| last_name | No | Last name (Apollo split export). Use with first_name instead of full_name. | |
| prop_addr | No | Full property address string (legacy v1 key) → PropertyAddress. | |
| seniority | No | Apollo seniority level → Description. | |
| first_name | No | First name (Apollo split export). Use with last_name instead of full_name. | |
| work_phone | No | Apollo 'Work Phone' column — lowest-priority fallback. | |
| departments | No | Apollo departments string → Description. | |
| lead_source | No | Lead source string → LeadSource (mapped to Salesforce picklist values). | |
| person_city | No | Apollo 'Person City' column → City. | |
| postal_code | No | ZIP / postal code → PostalCode. | |
| twitter_url | No | Twitter/X URL → Twitter__c. | |
| account_name | No | Apollo 'Account Name' column → Company. | |
| linkedin_url | No | LinkedIn profile URL → LinkedIn__c. | |
| mobile_phone | No | Apollo 'Mobile Phone' column. Maps to MobilePhone if a primary phone exists. | |
| organization | No | Apollo 'Organization' column → Company. | |
| person_state | No | Apollo 'Person State' column → State. | |
| num_employees | No | Alternate employees key. | |
| annual_revenue | No | Annual revenue string, e.g. '$1.2M', '500000' → AnnualRevenue (number). | |
| person_country | No | Apollo 'Person Country' → Country. | |
| company_website | No | Apollo 'Company Website' → Website. | |
| person_postal_code | No | Apollo 'Person Postal Code' → PostalCode. | |
| number_of_employees | No | Employee count or range (e.g. '500-1000') → NumberOfEmployees. | |
| estimated_annual_revenue | No | Apollo estimated revenue → AnnualRevenue. |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!