CRM & Sales · Integration
Salesflare
Add Salesflare to your product for your customers, and give your AI agents governed access to it.
Salesflare's API exposes accounts, contacts, opportunities, tasks and the logged interactions behind them, with the API key sent in the authorization header as a bare key rather than a bearer token. The thing that catches implementers is that Salesflare creates and enriches records automatically from connected email and calendar, matching accounts by email domain, so a naive create call frequently produces a duplicate of a record the product was about to build itself; checking by domain or email before writing matters more here than in most CRMs. Custom fields appear as their own properties on the record rather than in a nested bag, so field discovery is a first-class step. Opportunity stages belong to a pipeline, and moving a deal means referencing the stage id from that pipeline, not a stage name. fastn holds each customer's Salesflare key, keeps writes scoped to their own account, and handles credential upkeep for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Salesflare account so your product reads and writes in their pipeline
Create or match accounts by email domain before writing, so you never duplicate auto-created records
Push product usage or billing signals onto the account and opportunity as custom fields
Create follow-up tasks for the owner when a tracked event happens in your product
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent update opportunity fields and create tasks while stage changes require a human
Have an agent look up an account by domain and summarise recent interactions before an outbound touch
Audit per tenant which records an agent read and every field it changed
Example prompt
What is the latest activity on the Salesflare opportunity for this account, and which stage is it in?
Set up Salesflare in 4 steps
- 01Enable the Salesflare connector from your fastn dashboard.
- 02Have each customer authorise their own Salesflare account, so calls run under their credentials rather than a shared key.
- 03Decide which accounts, contacts and opportunities your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Salesflare integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Salesflare integration without building it. Your customers connect their own Salesflare 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 Salesflare update is not your on-call problem.
- One integration serves your product and your agents. The same governed Salesflare 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
Salesforce
HubSpot
PipedriveOften used alongside
Tools the same teams tend to run next to Salesflare, across other categories.
Slack
Mailchimp
Marketo
Google AdsSalesflare integration FAQ
How do I add a Salesflare integration to my product?
Enable the Salesflare connector in your fastn dashboard, then let each customer authenticate their own Salesflare account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Salesflare client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Salesflare account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Salesflare 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 Salesflare integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent update opportunity fields and create tasks while stage changes require a human
Who maintains the Salesflare integration?
fastn does. When Salesflare 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 Salesflare 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 Salesflare schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Salesflare, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Salesflare do not drift apart.
What can I build with the Salesflare integration?
A common starting point: let a customer connect their own Salesflare account so your product reads and writes in their pipeline. 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 Salesflare integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Salesflare does not change your per-connector cost. You can start free with 3 connected accounts.
Add Salesflare to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.