TLDR
Classy gives you the campaign page and peer-to-peer fundraising infrastructure — GrantPipe gives you the donor-lifetime view across every campaign. The integration pulls Classy donations via API, deduplicates donors, maps fundraising page owners to GrantPipe contacts, and surfaces the full giving history in a single record regardless of how many Classy campaigns a donor has participated in.
Classy is where many mid-sized nonprofits run their campaign fundraising and peer-to-peer events. The data it generates — supporter records, donation history, recurring plans — lives inside Classy’s platform until you deliberately export it. GrantPipe’s Classy integration closes that gap, pulling campaigns and donor history into a unified CRM record where retention, lifetime value, and fund attribution are tracked alongside every other gift source.
What the integration does
GrantPipe connects to Classy via OAuth 2.0, requesting read access to donations, supporters, campaigns, fundraising pages, and recurring plans. Authentication uses standard OAuth credentials — no Classy password is stored.
On first connect, GrantPipe runs a deduplication pass across your Classy supporter list and your existing GrantPipe donors. Email is the primary key. Exact matches are linked; ambiguous matches are reviewed manually; unmatched Classy supporters become new donor records. Historical donations are imported from a configurable cutoff date.
Ongoing sync is nightly. New donations processed in Classy the previous day appear in GrantPipe the next morning, attributed to the fund mapped for that campaign.
Peer-to-peer fundraiser pages are treated as campaign records. The fundraiser who owns the page is a donor record; gifts made through their page carry a soft credit linking the fundraiser’s influence to the donation total.
Roadmap status
This integration is on the GrantPipe roadmap. The Classy API architecture and OAuth 2.0 flow are documented and planned. Given Classy’s prevalence among mid-market nonprofits running campaign and peer-to-peer fundraising, this integration is prioritized in the payments cluster. Contact the team for timeline estimates.
Data flows
- Classy supporters → GrantPipe donors (with deduplication, historical import + nightly)
- Classy donations → GrantPipe donations (historical import + nightly, one-way)
- Classy campaigns → GrantPipe campaign records (nightly)
- Classy fundraising pages → GrantPipe campaign + soft credit links (nightly)
- Classy recurring plans → GrantPipe recurring gift series (nightly)
Setup steps
- Connect via OAuth from Settings → Integrations → Classy
- Select the correct Classy organization
- Review and resolve the deduplication match report
- Map campaigns to GrantPipe restricted funds
- Configure peer-to-peer fundraiser import settings
- Set the historical import cutoff date
- Enable nightly ongoing sync
Common use cases
A nonprofit runs two major Classy campaigns annually — a year-end giving campaign and a spring gala peer-to-peer drive. After the GrantPipe integration, every gift from both campaigns appears on the donor’s unified record. The development director can filter donors who gave to last year’s peer-to-peer campaign and segment them for a major gift ask — something impossible from Classy’s reports alone.
The finance team maps each campaign to a restricted fund. When the annual report pulls, restricted fund revenue from Classy flows automatically into the GrantPipe fund ledger alongside gifts from other sources.
Limitations and gotchas
Classy’s API does not support real-time webhooks for all event types. Sync is nightly, meaning a same-day gift will not appear in GrantPipe until the next morning. For high-volume event days, a manual sync can be triggered from Settings.
GoFundMe Charity campaigns, which use a different platform architecture from Classy, are not covered in the initial integration. If your organization uses both platforms, GoFundMe Charity data will need a separate import.
Soft credits for peer-to-peer fundraisers are created automatically, but they require the fundraiser to have a GrantPipe donor record. Fundraisers who are themselves donors are matched by email; fundraisers with no prior giving history create new donor records.
Pricing implications
Classy charges a platform fee on donations in addition to Stripe’s processing fee. GrantPipe records the gross donation amount as the donor’s gift and separately tracks the platform fee as a cost line — consistent with how most nonprofits record fundraising expenses under FASB ASC 958. GrantPipe’s own subscription pricing is not affected by Classy volume.
Start a free trial
Free resource
Get the Nonprofit Grant Compliance Checklist
A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.
Source: Classy Pricing Overview
Q&A
How does GrantPipe handle donors who give through multiple Classy campaigns?
Each Classy donation is linked to the donor record matched by email. If a donor gives to three different Classy campaigns over three years, all three donations appear on a single GrantPipe donor record. Campaign attribution is preserved as a tag on each donation.
Q&A
What about the fundraiser's soft credit for peer-to-peer gifts?
Peer-to-peer gifts are hard-credited to the actual donor (the person who gave). The fundraiser page owner receives a soft credit for gifts made through their page. GrantPipe's soft-credit tracking records this relationship so the fundraiser's influence on total giving is visible in reporting.
Q&A
Can I use the Classy integration alongside a direct Stripe integration?
Yes. Some organizations use Classy for campaign fundraising and Stripe directly for recurring gifts and major gifts. GrantPipe deduplicates across both sources using email as the primary key, so a donor who gives through both channels has one record with both gifts.
Frequently asked