CRM & Sales · Integration
Nutshell
Add Nutshell to your product for your customers, and give your AI agents governed access to it.
Nutshell is built for small sales teams and its object model reflects that: leads move along a pipeline, people and companies sit behind them, and activities and notes record what happened. There is very little ceremony to any of it, which is exactly why offering an embedded Nutshell integration pays off. The teams who use it rarely have anyone on staff to build integrations for them, so a connector inside your product is often the only way their CRM and their other tools ever meet. The flat structure keeps mapping straightforward, though lead stage naming is customised per account and is the one thing worth reading rather than assuming. fastn stores each account's credentials and keeps the API surface maintained.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a small team connect their own Nutshell account and see their leads inside your product with no setup work.
Create a lead from a signup or enquiry your product captured, attached to the right person and company.
Log notes and activities so the record of a conversation lives in the CRM the team actually opens.
Read each account's own pipeline stage names so your product's labels match what the team says out loud.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises which leads have gone quiet, reading a single team's account.
An agent adds a note or advances a lead within the permissions granted, and the action is attributed.
An agent looks up a person's history with the company before a call.
Example prompt
Which leads in this pipeline have not been touched in two weeks, and who owns them?
Set up Nutshell in 4 steps
- 01Enable the Nutshell connector from your fastn dashboard.
- 02Have each customer authorise their own Nutshell 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 Nutshell integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Nutshell integration without building it. Your customers connect their own Nutshell 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 Nutshell update is not your on-call problem.
- One integration serves your product and your agents. The same governed Nutshell 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
Pipedrive
Capsule CRM
CloseOften used alongside
Tools the same teams tend to run next to Nutshell, across other categories.
Slack
Mailchimp
Marketo
Google AdsNutshell integration FAQ
How do I add a Nutshell integration to my product?
Enable the Nutshell connector in your fastn dashboard, then let each customer authenticate their own Nutshell account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Nutshell client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Nutshell account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Nutshell 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 Nutshell 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 summarises which leads have gone quiet, reading a single team's account.
Who maintains the Nutshell integration?
fastn does. When Nutshell 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 Nutshell 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 Nutshell schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Nutshell, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Nutshell do not drift apart.
What can I build with the Nutshell integration?
A common starting point: let a small team connect their own Nutshell account and see their leads inside your product with no setup work. 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 Nutshell integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Nutshell does not change your per-connector cost. You can start free with 3 connected accounts.
Add Nutshell to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.