CRM & Sales · Integration
Salesmate
Add Salesmate to your product for your customers, and give your AI agents governed access to it.
Salesmate is served from a per-tenant subdomain, so every request goes to the customer's own workspace host rather than a shared API domain, and authentication pairs an access token with that workspace name. Reads are not plain GETs: the v4 API retrieves and searches records through POST endpoints that take a JSON body describing the filter and the fields you want back. Those fields are referenced by numeric field ids rather than names, so any integration has to fetch the field metadata for the module first and cache the mapping, and that mapping differs per tenant because custom fields get their own ids. The main modules are contacts, companies, deals and activities, with deals bound to a pipeline and stage that must be referenced by id. fastn resolves each customer's workspace host and token on connect, keeps their field id maps separate, and handles reconnection when credentials change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Salesmate workspace so records are written to their host and pipeline
Discover the tenant's field ids once and map them to your internal schema for every later sync
Create or update contacts, companies and deals from events in your product without duplicating records
Read deal stage and value back into your dashboards so revenue signals sit next to product usage
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent update contact and deal fields on an approved list while stage changes need human approval
Have an agent search deals by filter and summarise pipeline for a named owner
Audit per tenant which modules an agent queried and every field id it wrote
Example prompt
What deals are open in Salesmate for this company, and what stage and value is each one at?
Set up Salesmate in 4 steps
- 01Enable the Salesmate connector from your fastn dashboard.
- 02Have each customer authorise their own Salesmate 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 Salesmate integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Salesmate integration without building it. Your customers connect their own Salesmate 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 Salesmate update is not your on-call problem.
- One integration serves your product and your agents. The same governed Salesmate 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 Salesmate, across other categories.
Slack
Mailchimp
Marketo
Google AdsSalesmate integration FAQ
How do I add a Salesmate integration to my product?
Enable the Salesmate connector in your fastn dashboard, then let each customer authenticate their own Salesmate account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Salesmate client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Salesmate account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Salesmate 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 Salesmate 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 contact and deal fields on an approved list while stage changes need human approval
Who maintains the Salesmate integration?
fastn does. When Salesmate 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 Salesmate 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 Salesmate schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Salesmate, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Salesmate do not drift apart.
What can I build with the Salesmate integration?
A common starting point: let a customer connect their own Salesmate workspace so records are written to their host and 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 Salesmate integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Salesmate does not change your per-connector cost. You can start free with 3 connected accounts.
Add Salesmate to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.