CRM & Sales · Integration
DonorPerfect
Add DonorPerfect to your product for your customers, and give your AI agents governed access to it.
DonorPerfect is a fundraising CRM, so the records that matter are constituents, gifts, pledges, recurring gifts, soft credits, tributes and the campaigns and solicitation codes a gift is attributed to. An embedded DonorPerfect integration puts a nonprofit's own database behind your product, whether you run events, peer-to-peer fundraising, payments or supporter communications. Two things make it particular. Nearly every organisation adds user-defined fields of its own, so no two databases carry the same shape. And attribution is the entire point of a gift record, because campaign, solicitation and general ledger codes decide how the money is reported, so a write that guesses them creates work for the development team. fastn maps those fields per tenant and owns credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each nonprofit connect their own DonorPerfect database so a donation taken in your product is recorded as a gift on the right constituent.
Create and update constituent records without duplicating a donor or household that already exists.
Write pledges and recurring gifts, then read the payments against them so a development team can see who has lapsed.
Map the user-defined fields an organisation added itself, so an unusual database is configuration rather than a release.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reviews a donor's giving history, soft credits included, before a major gift conversation.
An agent reports a campaign's totals and which appeals brought them in, reading one organisation's data only.
An agent records a gift with the campaign and solicitation codes it was given, and the write is logged.
Example prompt
Show this constituent's gifts over the last three years with soft credits, and whether their pledge is current.
Set up DonorPerfect in 4 steps
- 01Enable the DonorPerfect connector from your fastn dashboard.
- 02Have each customer authorise their own DonorPerfect 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 DonorPerfect integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a DonorPerfect integration without building it. Your customers connect their own DonorPerfect 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 DonorPerfect update is not your on-call problem.
- One integration serves your product and your agents. The same governed DonorPerfect 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
Raiser's Edge NXT
Little Green LightOften used alongside
Tools the same teams tend to run next to DonorPerfect, across other categories.
Slack
Mailchimp
Marketo
Google AdsDonorPerfect integration FAQ
How do I add a DonorPerfect integration to my product?
Enable the DonorPerfect connector in your fastn dashboard, then let each customer authenticate their own DonorPerfect account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no DonorPerfect client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own DonorPerfect account?
Yes. Every connection is scoped to the individual customer, so each authorises their own DonorPerfect 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 DonorPerfect 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 reviews a donor's giving history, soft credits included, before a major gift conversation.
Who maintains the DonorPerfect integration?
fastn does. When DonorPerfect 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 DonorPerfect 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 DonorPerfect schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from DonorPerfect, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in DonorPerfect do not drift apart.
What can I build with the DonorPerfect integration?
A common starting point: let each nonprofit connect their own DonorPerfect database so a donation taken in your product is recorded as a gift on the right constituent. 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 DonorPerfect integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding DonorPerfect does not change your per-connector cost. You can start free with 3 connected accounts.
Add DonorPerfect to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.