CRM & Sales · Integration
Senses
Add Senses to your product for your customers, and give your AI agents governed access to it.
Senses is the sales force automation and CRM product from Mazrica, now sold under the name Mazrica Sales, and it is built around a board rather than a list: deals sit in stages you can see at a glance, and the activity logged against each one is what moves it along. An embedded Senses integration reads and writes the companies, contacts and deals a team works with, adds the activity your product already knows about, and reacts when a deal changes stage. As with any CRM, the instance is customised, so which fields exist on a deal and what the stages are called belong to that team and are mapped per customer as configuration rather than compiled into your product. Each customer authorises their own account, so one team's pipeline never appears in another's. fastn holds the credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Senses account so companies, contacts and deals are readable and writable inside your product.
Log the activity your product already captured against the right deal, so the board reflects what actually happened.
React when a deal changes stage, so the steps your product owns follow the pipeline rather than a weekly review.
Map each team's own deal fields and stage names as configuration, since no two instances are set up alike.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a deal with its recent activity before answering where things stand, reading only that customer's account.
An agent updates a deal or logs an activity within governed permissions, with every write attributed.
An agent reports which deals have not moved stage recently and what was last logged against them.
Example prompt
Which deals on this board have had no activity logged in two weeks, and which stage is each sitting in?
Set up Senses in 4 steps
- 01Enable the Senses connector in your fastn dashboard.
- 02Have each customer authorise their own Senses or Mazrica Sales account.
- 03Map the company, contact and deal fields that team uses, including their own stage names, then enable actions and triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Senses integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Senses integration without building it. Your customers connect their own Senses 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 Senses update is not your on-call problem.
- One integration serves your product and your agents. The same governed Senses 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
HubSpotWorks well with
SansanOften used alongside
Tools the same teams tend to run next to Senses, across other categories.
Slack
Mailchimp
Marketo
Google AdsSenses integration FAQ
How do I add a Senses integration to my product?
Enable the Senses connector in your fastn dashboard, then let each customer authenticate their own Senses account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Senses client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Senses account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Senses 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 Senses 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 deal with its recent activity before answering where things stand, reading only that customer's account.
Who maintains the Senses integration?
fastn does. When Senses 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 Senses 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 Senses schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Senses, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Senses do not drift apart.
What can I build with the Senses integration?
A common starting point: let each customer connect their own Senses account so companies, contacts and deals are readable and writable inside your product. 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 Senses integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Senses does not change your per-connector cost. You can start free with 3 connected accounts.
Add Senses to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.