CRM & Sales · Integration
Classy
Add Classy to your product for your customers, and give your AI agents governed access to it.
Embed a Classy integration so your customers can read fundraising campaigns, donations, and supporter records from inside your product, with governed agent access to the same data. This is a read surface: the connector follows what Classy reports rather than writing into it, and every call is logged per tenant so a figure in your product can be reconciled against the campaign that produced it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read donations and recurring gifts into your product.
Read campaign performance so fundraising progress is visible where teams work.
Read supporter records so acknowledgement and stewardship can be automated.
Trigger your product when a donation is received or a recurring gift fails.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a supporter's giving history before drafting an acknowledgement.
An agent summarises campaign performance within governed permissions.
An agent reacts to a failed recurring gift and starts the recovery workflow.
Example prompt
List recurring gifts that failed this month and the total value at risk.
Set up Classy in 4 steps
- 01Open the Classy connector from your fastn dashboard.
- 02Have each customer authenticate their Classy account.
- 03Map the campaign, donation, and supporter 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 Classy integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Classy integration without building it. Your customers connect their own Classy 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 Classy update is not your on-call problem.
- One integration serves your product and your agents. The same governed Classy 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
SalesforceWorks well with
Stripe
MailchimpOften used alongside
Tools the same teams tend to run next to Classy, across other categories.
Slack
Marketo
Google Ads
Microsoft TeamsClassy integration FAQ
How do I add a Classy integration to my product?
Enable the Classy connector in your fastn dashboard, then let each customer authenticate their own Classy account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Classy client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Classy account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Classy 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 Classy 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 supporter's giving history before drafting an acknowledgement.
Who maintains the Classy integration?
fastn does. When Classy 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 Classy integration support custom fields and custom objects?
Yes for reading. Classy campaigns carry custom questions and fields per organisation, and those are mapped per tenant rather than hard-coded, so an unusual campaign setup does not need a deploy on your side.
Can records sync both ways?
This is a read surface. Your product reads campaigns, donations and supporters and reacts to donation events, but the record of a gift stays where it was made. That is the honest shape: a donation is not a row you edit from elsewhere.
What can I build with the Classy integration?
A common starting point: read donations and recurring gifts into 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 Classy integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Classy does not change your per-connector cost. You can start free with 3 connected accounts.
Add Classy to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.