CRM & Sales · Integration
Nimble
Add Nimble to your product for your customers, and give your AI agents governed access to it.
Embed a Nimble integration so your customers work their own relationship records inside your product rather than in a second tab. Nimble is a contact first CRM used heavily by small teams, so the records that matter are contacts and companies, deals, activities and tasks, and the tags and custom fields each team invents to keep track of its own segments. Each customer authorises their own Nimble account, so reads and writes are scoped to their tenant and field mapping is configuration, which is what makes onboarding a customer with an unusual setup a mapping change rather than a release. fastn owns the auth, token refresh, rate limits and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Nimble account so contacts, companies and deals appear inside your product with no per-customer code.
Create and update contact and deal records from your product so what a user does in your app is reflected in their CRM.
Log activities and tasks against the right contact automatically so follow-up does not depend on somebody remembering.
Read tags and custom fields per tenant so segments a team built themselves still work inside your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent pulls a contact's history and open deals before drafting a reply, reading only that tenant's Nimble account.
An agent creates a follow-up task on the right record within scoped permissions, with the write attributed.
An agent reports which deals have gone quiet for one customer, with every read audited.
Example prompt
Show this contact's Nimble history and open deals, then draft the follow-up and log it as a task.
Set up Nimble in 4 steps
- 01Enable the Nimble connector in your fastn dashboard.
- 02Have each customer authorise their own Nimble account so calls run under their credentials.
- 03Map the contact, company, deal and activity fields your product uses, including custom fields, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Nimble integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Nimble integration without building it. Your customers connect their own Nimble 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 Nimble update is not your on-call problem.
- One integration serves your product and your agents. The same governed Nimble 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
Copper
InsightlyOften used alongside
Tools the same teams tend to run next to Nimble, across other categories.
Slack
Mailchimp
Marketo
Google AdsNimble integration FAQ
How do I add a Nimble integration to my product?
Enable the Nimble connector in your fastn dashboard, then let each customer authenticate their own Nimble account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Nimble client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Nimble account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Nimble 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 Nimble 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 pulls a contact's history and open deals before drafting a reply, reading only that tenant's Nimble account.
Who maintains the Nimble integration?
fastn does. When Nimble 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 Nimble 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 Nimble schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Nimble, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Nimble do not drift apart.
What can I build with the Nimble integration?
A common starting point: let each customer connect their own Nimble account so contacts, companies and deals appear inside your product with no per-customer code. 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 Nimble integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Nimble does not change your per-connector cost. You can start free with 3 connected accounts.
Add Nimble to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.