CRM & Sales · Integration
Funraise
Add Funraise to your product for your customers, and give your AI agents governed access to it.
Embed a Funraise integration so your nonprofit customers can work their own donations, donors, campaigns, and recurring giving from inside your product. Writes are idempotent, so a retry after a timeout cannot record the same gift twice, and every call is logged per tenant so a donation can be reconciled against the event that created it. fastn handles per-customer authorisation and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own donations and donor records into your product, mapped to their fields.
Show campaign totals and recurring giving next to the constituent data your product holds.
Create or update donor records from activity in your product so their fundraising system stays current.
Trigger your product when a donation is recorded, refunded, or a recurring plan changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a donor's giving history before drafting a thank-you or a stewardship next step.
An agent updates a donor record within governed permissions, with the action logged.
An agent reacts to a new donation and runs the next acknowledgement step.
Example prompt
List donors who gave last year but not this year, with the amount and date of their most recent gift.
Set up Funraise in 4 steps
- 01Open the Funraise connector from your fastn dashboard.
- 02Have each customer authenticate their own Funraise account.
- 03Map the donation, donor, and campaign 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 Funraise integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Funraise integration without building it. Your customers connect their own Funraise 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 Funraise update is not your on-call problem.
- One integration serves your product and your agents. The same governed Funraise 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
Classy
DonorPerfectWorks well with
StripeOften used alongside
Tools the same teams tend to run next to Funraise, across other categories.
Slack
Mailchimp
Marketo
Google AdsFunraise integration FAQ
How do I add a Funraise integration to my product?
Enable the Funraise connector in your fastn dashboard, then let each customer authenticate their own Funraise account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Funraise client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Funraise account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Funraise 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 Funraise 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 donor's giving history before drafting a thank-you or a stewardship next step.
Who maintains the Funraise integration?
fastn does. When Funraise 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 Funraise 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 Funraise schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Funraise, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Funraise do not drift apart.
What can I build with the Funraise integration?
A common starting point: read their own donations and donor records into your product, mapped to their fields. 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 Funraise integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Funraise does not change your per-connector cost. You can start free with 3 connected accounts.
Add Funraise to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.