CRM & Sales · Integration
Freshsales
Add Freshsales to your product for your customers, and give your AI agents governed access to it.
Freshsales is the CRM inside the Freshworks family, so its records are contacts, sales accounts, deals moving along a pipeline, and the sales activities, tasks and appointments logged against them. Two things are worth knowing before you build. Freshsales is one product among several, and Freshdesk and Freshchat are separate systems reached through separate connectors, so a customer saying they run Freshworks has not told you which records you can actually get to. And the pipeline is theirs: deal stages, territories and the custom fields on a contact are defined per account, so a stage name written into your code will not exist in the next customer's instance. fastn holds each account's credentials per tenant and absorbs the API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Freshsales account so a contact your product captures appears under the right sales account.
Read that customer's own deal stages and pipelines instead of assuming the set Freshsales ships with.
Log sales activities, tasks and appointments so the CRM reflects work that happened inside your product.
React to a deal stage change or a new contact, and pair this with the separate Freshdesk connector when support history is needed too.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a sales account's open deals and the activities logged against them before it answers.
An agent creates a task or moves a deal inside the permissions granted, and the change is logged.
An agent surfaces deals with nothing logged against them lately, judged by that account's own stage definitions.
Example prompt
Show the open deals on this sales account and which have had no activity logged this month.
Set up Freshsales in 4 steps
- 01Open the Freshsales connector from your fastn dashboard.
- 02Have each customer authenticate their own Freshsales account.
- 03Map the contacts, accounts, deals, and custom fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Freshsales integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Freshsales integration without building it. Your customers connect their own Freshsales 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 Freshsales update is not your on-call problem.
- One integration serves your product and your agents. The same governed Freshsales 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
SalesforceWorks well with
FreshdeskOften used alongside
Tools the same teams tend to run next to Freshsales, across other categories.
Slack
Mailchimp
Marketo
Google AdsFreshsales integration FAQ
How do I add a Freshsales integration to my product?
Enable the Freshsales connector in your fastn dashboard, then let each customer authenticate their own Freshsales account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Freshsales client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Freshsales account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Freshsales 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 Freshsales 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 sales account's open deals and the activities logged against them before it answers.
Who maintains the Freshsales integration?
fastn does. When Freshsales 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 Freshsales 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 Freshsales schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Freshsales, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Freshsales do not drift apart.
What can I build with the Freshsales integration?
A common starting point: let each customer connect their own Freshsales account so a contact your product captures appears under the right sales account. 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 Freshsales integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Freshsales does not change your per-connector cost. You can start free with 3 connected accounts.
Add Freshsales to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.