CRM & Sales · Integration
Vitally
Add Vitally to your product for your customers, and give your AI agents governed access to it.
Vitally is where a customer success team keeps the truth about its accounts: the account itself, the users inside it, the traits and product usage streamed in from elsewhere, and the health score computed on top of all of it. Tasks, playbooks and survey responses hang off the same records. This integration matters because your product is usually the source of the signal a health score depends on, so pushing traits and events in is often worth more than reading anything out. Every team defines its own traits, segments and scoring, so those are configuration per tenant rather than a shape you could pin down ahead of time. One thing to be clear about: the familiar CRM objects only half apply, since there are accounts and users but no opportunities and no pipeline stages. fastn keeps each workspace's credentials and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Vitally workspace so usage your product measures feeds the health scores their team relies on.
Push account and user traits from your product so the success team sees the signal without waiting on a data pipeline.
Read accounts with their health score and owner so your product can show who is at risk and who is looking after them.
Create a task or fire an event when your product notices something a success manager should act on.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which accounts dropped in health this month and which traits moved with them.
An agent opens a follow-up task against an account inside its granted permissions, and the write carries an attribution.
An agent answers who owns an account and what was last logged against it, reading only that workspace.
Example prompt
Which accounts fell in health score this month, and what changed in their usage traits?
Set up Vitally in 4 steps
- 01Enable the Vitally connector in your fastn dashboard.
- 02Have each customer authorise their own Vitally workspace so calls run under their credentials.
- 03Map the account, user, trait, task and health score fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Vitally integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Vitally integration without building it. Your customers connect their own Vitally 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 Vitally update is not your on-call problem.
- One integration serves your product and your agents. The same governed Vitally 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
Gainsight
HubSpotWorks well with
IntercomOften used alongside
Tools the same teams tend to run next to Vitally, across other categories.
Slack
Mailchimp
Marketo
Google AdsVitally integration FAQ
How do I add a Vitally integration to my product?
Enable the Vitally connector in your fastn dashboard, then let each customer authenticate their own Vitally account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Vitally client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Vitally account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Vitally 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 Vitally 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 reports which accounts dropped in health this month and which traits moved with them.
Who maintains the Vitally integration?
fastn does. When Vitally 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 Vitally 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 Vitally schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Vitally, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Vitally do not drift apart.
What can I build with the Vitally integration?
A common starting point: let each customer connect their own Vitally workspace so usage your product measures feeds the health scores their team relies on. 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 Vitally integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Vitally does not change your per-connector cost. You can start free with 3 connected accounts.
Add Vitally to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.