CRM & Sales · Integration
LeadConnector
Add LeadConnector to your product for your customers, and give your AI agents governed access to it.
LeadConnector is the API behind HighLevel, which means the thing your customer connects is a sub-account rather than a company-wide tenant, and that distinction shapes everything downstream. An agency runs many sub-accounts, so a token is scoped to one location and your product has to know which one it is holding. Inside is a whole go-to-market stack rather than a CRM alone: contacts with tags, notes and tasks; opportunities moving through named pipeline stages; two-way conversations across SMS, email and chat; calendars and appointments; and payment records. Authorisation is OAuth through the marketplace where you are shipping an app to many customers, or a private integration token where a single business is wiring up its own account. fastn holds whichever one a customer uses and keeps the connection working as HighLevel versions its API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer authorise the sub-account they actually work in, so a contact your product creates lands in that location rather than an agency-wide pool.
Move an opportunity to a named pipeline stage when something changes in your product, using the stages that sub-account defines.
Send and read conversation messages so an SMS and an email thread with the same person stay in one place.
Book, reschedule or cancel an appointment against the calendar availability that customer already configured.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a contact with its opportunities and recent conversation before drafting a reply.
An agent advances an opportunity or adds a tag within scoped permissions, with the sub-account it acted in recorded.
An agent reports which opportunities have gone quiet and what the last inbound message said.
Example prompt
Which opportunities in this pipeline have had no inbound message for two weeks, and what was the last thing the contact said?
Set up LeadConnector in 4 steps
- 01Enable the LeadConnector connector in your fastn dashboard.
- 02Have each customer authorise the sub-account they work in, through the marketplace OAuth flow or a private integration token.
- 03Map that location's pipelines, stages, custom fields and calendars, then enable the actions and triggers you want.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the LeadConnector integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a LeadConnector integration without building it. Your customers connect their own LeadConnector account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a LeadConnector update is not your on-call problem.
- One integration serves your product and your agents. The same governed LeadConnector connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
HubSpot
Keap
Follow Up BossOften used alongside
Tools the same teams tend to run next to LeadConnector, across other categories.
Slack
Mailchimp
Marketo
Google AdsLeadConnector integration FAQ
How do I add a LeadConnector integration to my product?
Enable the LeadConnector connector in your fastn dashboard, then let each customer authenticate their own LeadConnector account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no LeadConnector client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own LeadConnector account?
Yes. Every connection is scoped to the individual customer, so each authorises their own LeadConnector account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this LeadConnector integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a contact with its opportunities and recent conversation before drafting a reply.
Who maintains the LeadConnector integration?
fastn does. When LeadConnector changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the LeadConnector integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual LeadConnector schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from LeadConnector, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in LeadConnector do not drift apart.
What can I build with the LeadConnector integration?
A common starting point: let each customer authorise the sub-account they actually work in, so a contact your product creates lands in that location rather than an agency-wide pool. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the LeadConnector integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding LeadConnector does not change your per-connector cost. You can start free with 3 connected accounts.
Add LeadConnector to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.