CRM & Sales · Integration
Capsule CRM
Add Capsule CRM to your product for your customers, and give your AI agents governed access to it.
Embed a Capsule CRM integration so your customers can work their own contacts, opportunities, tasks, and pipelines from inside your product, and so your agents get governed access to the same records. Every CRM is customised, so custom fields, tags, and pipeline stages are mapped per customer as configuration rather than code, and records can sync both ways so your app and Capsule CRM do not drift apart. fastn handles per-customer OAuth and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync their own Capsule CRM contacts and organisations into your product, mapped to their fields and tags.
Read and write opportunities and pipeline stages so deals move without leaving your app.
Create and complete tasks against a contact or opportunity from inside your product.
Trigger your product when a contact is created or an opportunity changes stage.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
A sales copilot reads a contact's opportunity history before it answers.
An agent creates or updates a contact, opportunity, or task within governed permissions.
An agent reacts to a stage change and runs the next step of a workflow.
Example prompt
Show open opportunities with no activity in 14 days and list the owner for each.
Set up Capsule CRM in 4 steps
- 01Open the Capsule CRM connector from your fastn dashboard.
- 02Have each customer authenticate their Capsule CRM account with OAuth.
- 03Map the contact, opportunity, and pipeline fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Capsule CRM integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Capsule CRM integration without building it. Your customers connect their own Capsule CRM 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 Capsule CRM update is not your on-call problem.
- One integration serves your product and your agents. The same governed Capsule CRM 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
HubSpot
SalesforceWorks well with
SlackOften used alongside
Tools the same teams tend to run next to Capsule CRM, across other categories.
Mailchimp
Marketo
Google Ads
Microsoft TeamsCapsule CRM integration FAQ
How do I add a Capsule CRM integration to my product?
Enable the Capsule CRM connector in your fastn dashboard, then let each customer authenticate their own Capsule CRM account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Capsule CRM client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Capsule CRM account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Capsule CRM 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 Capsule CRM integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. A sales copilot reads a contact's opportunity history before it answers.
Who maintains the Capsule CRM integration?
fastn does. When Capsule CRM 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 Capsule CRM 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 Capsule CRM schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Capsule CRM, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Capsule CRM do not drift apart.
What can I build with the Capsule CRM integration?
A common starting point: sync their own Capsule CRM contacts and organisations into your product, mapped to their fields and tags. 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 Capsule CRM integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Capsule CRM does not change your per-connector cost. You can start free with 3 connected accounts.
Add Capsule CRM to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.