Salesforce · Raisely · Nonprofit Fundraising

How to Integrate Raisely with Salesforce for Nonprofits: MoveData, Zapier or API

Donations, regular gifts and peer-to-peer fundraisers start in Raisely, but your donor history, stewardship and board reporting live in Salesforce. Here are the three ways to connect them, where each record should land in NPSP or Agentforce Nonprofit, a step-by-step Zapier build, and the webhook details that decide whether the sync stays accurate.

Key Takeaways

  • Raisely does not build its own Salesforce connector. Its official options are the MoveData integration (a paid subscription) or Raisely's API and webhooks, and Zapier works for lighter, no-code needs.
  • MoveData supports both NPSP and Agentforce Nonprofit (formerly Nonprofit Cloud) and syncs one way, from Raisely into Salesforce, in real time.
  • In NPSP, Raisely donations become Opportunities and regular gifts become Recurring Donations. In Agentforce Nonprofit they become Gift Transactions and Gift Commitments.
  • Salesforce on Zapier is a Premium app, so the Zapier route needs a paid plan (Professional or above), My Domain, and a Salesforce edition with API access.
  • Raisely webhooks can arrive out of order and are retried, so any custom build must match records on Raisely's IDs to avoid duplicate donors and gifts.

What is a Raisely Salesforce integration? It is a connection that copies donations, regular gifts, donors, fundraisers and campaigns from Raisely, the online fundraising platform, into Salesforce, so the CRM holds a complete giving history without manual exports. Raisely offers two official routes: the MoveData integration for NPSP and Agentforce Nonprofit, or its own API and webhooks. Zapier is a third, no-code option for simpler needs.

We first published this guide in 2024 as a Zapier walkthrough. This version covers all three routes, the data model choice between NPSP and Agentforce Nonprofit, current Zapier and Salesforce prerequisites, and the Raisely webhook behaviour that custom builds must handle. Every product claim is checked against Raisely, MoveData, Zapier and Salesforce documentation as of November 2026. It is written for fundraising, operations and IT leads at nonprofits, from small charities to growing and mid-market organizations, and for the Salesforce admins who will build the connection.

Section 01 · Short Answer

What Are the Ways to Set Up a Raisely Salesforce Integration?

There are three: MoveData, Zapier, or a custom build on Raisely's API and webhooks. MoveData is the packaged option Raisely points nonprofits to, with real-time sync into NPSP or Agentforce Nonprofit. Zapier suits a few simple flows without developers. A custom build fits organizations with unusual data models, high volumes or an existing integration platform. All three move data from Raisely into Salesforce.

QuestionMoveDataZapierCustom API and webhooks
Who builds itMoveData sets it up during onboardingYour admin, no codeA Salesforce developer or integration partner
Salesforce data modelNPSP and Agentforce Nonprofit out of the boxWhatever objects you map, step by stepWhatever you design
Data coveredDonations, regular giving, fundraisers, teams, campaigns, events and ordersWhat the Raisely Zapier triggers or webhooks sendEverything in the Raisely API
Ongoing costMonthly subscription per organizationPaid Zapier plan plus tasks usedBuild cost, hosting or middleware, and maintenance
Best forMost nonprofits on NPSP or Agentforce NonprofitLow volume, one or two flowsComplex or high-volume programmes

Raisely's support article on integrating with Salesforce describes the first and third options. Zapier lists ready-made Raisely and Salesforce templates for the second.

Section 02 · Raisely

What Is Raisely, and What Data Does It Hold?

Raisely is an online fundraising platform for donation forms, appeals, regular giving, peer-to-peer and DIY fundraising, and ticketed events. It started in 2016, is registered in Australia, and is now part of Velora, alongside Aplos fund accounting and Keela donor management. Raisely has basic supporter management, but most nonprofits keep Salesforce as the system of record for relationships and reporting.

Raisely logo, the online fundraising platform that nonprofits integrate with Salesforce

Raisely's pricing page describes a free Core plan funded by optional donor tips, or a flat 4% fee instead of tips, and a Pro plan at US$119 per month (or US$714 per year) for advanced features, including "some integrations". Raisely does not state which plan the Salesforce integration requires, so confirm it with Raisely before you budget.

The data a Salesforce integration usually needs from Raisely falls into six groups:

People

Donors, fundraisers and team members, with contact details and consent fields.

Donations

Online and offline gifts, with refunds, payment status and campaign attribution.

Regular giving

Subscriptions, their rebills, and failed, paused or cancelled payments.

Fundraisers and teams

Peer-to-peer profiles, team membership and running totals.

Campaigns

Each Raisely campaign, which maps naturally to a Salesforce Campaign.

Orders and events

Ticket and merchandise orders for fundraising events.

Section 03 · Data Model

Where Should Raisely Data Land: NPSP or Agentforce Nonprofit?

It depends on which nonprofit data model your Salesforce org runs, and the objects are different. NPSP, the long-standing free package, records gifts as Opportunities and regular gifts as Recurring Donations. Agentforce Nonprofit, which Salesforce renamed from Nonprofit Cloud in December 2025, records them as Gift Transactions and Gift Commitments on a native fundraising model. Decide this before you build, because the mapping follows it.

Raisely dataNPSPAgentforce Nonprofit (formerly Nonprofit Cloud)
Individual donorContact, with a household AccountPerson Account
Company giving on a donor's behalfAccountAccount
One-off donationOpportunity, with a PaymentGift Transaction
Regular giving subscriptionRecurring DonationGift Commitment, with its schedule
RefundRecorded against the Opportunity; agree the method in your mappingRefund on the Gift Transaction (full or partial)
Campaign and fundraiser pagesCampaign, with child Campaigns per pageCampaign hierarchy, with Campaign Members

The mapping above is the one MoveData documents for Raisely. Salesforce explains the new model in its Help pages on gift transactions and gift commitments, which support designations, soft credits and refunds.

Two points matter when you choose. First, Salesforce says NPSP will continue to be supported, but its new nonprofit features ship in Agentforce Nonprofit, so a nonprofit starting fresh should usually start there. Second, the Power of Us programme now donates 10 Enterprise Edition licences as a Nonprofit or a Sales and Service bundle. If you are weighing a move, our comparison of NPSP and Nonprofit Cloud covers the trade-offs, and it is far cheaper to settle the model before the integration than to remap it afterwards.

Section 04 · Prerequisites

What Do You Need Before You Connect Raisely to Salesforce?

Salesforce API access, an integration user, an agreed data model, and a clean donor database. API access comes with Enterprise, Unlimited, Performance and Developer editions. Professional Edition needs the Web Services API add-on, and Group and Essentials cannot get it. Nonprofits on donated Power of Us licences are on Enterprise Edition, so most already qualify.

  • API access confirmed. Check your edition against Salesforce's article on API access by edition. Zapier's own guide lists Essentials and Professional as compatible, but Salesforce's rules decide.
  • A dedicated integration user. Use a user with the API Enabled permission, ideally on a Salesforce Integration user licence, so syncs do not break when a staff member leaves.
  • Data model and mapping signed off. NPSP or Agentforce Nonprofit, which Raisely fields go where, and which record types and campaigns gifts attach to.
  • Matching rules agreed. How a Raisely donor is matched to an existing Salesforce record, usually by email and then name, and what happens on a conflict.
  • Existing duplicates cleaned. An integration that matches on email will attach gifts to the wrong record if your org already holds duplicates.
  • A sandbox to test in. Run test donations, refunds and failed regular gifts end to end before you switch on production.
Section 05 · MoveData

How Does the MoveData Raisely Integration Work?

MoveData receives Raisely events through an integration URL and writes them into Salesforce in real time, using Salesforce Flow. Raisely's own integration page says its Salesforce integration "is built and run by MoveData". It syncs donations, fundraisers, teams and regular donations, matches donors to existing records before creating new ones, and builds a campaign hierarchy so you can report on a whole campaign or a single fundraiser.

1. Install MoveData in Salesforce.
→ Install the package from its AppExchange listing and choose the NPSP or Agentforce Nonprofit configuration.
2. Create the Raisely integration in MoveData.
→ MoveData generates the integration URL that Raisely will send data to.
3. Register the URL in Raisely.
→ Add it as a webhook so Raisely pushes donations, profiles, subscriptions and orders as they happen.
4. Adjust the mapping with Flow.
→ Every mapping and business rule is a Flow you can open and change, so custom fields, custom objects and extra rules are added without Apex. MoveData helps with this during onboarding.
5. Test, then go live.
→ Run donations, refunds and a regular gift through a sandbox, then check matching and campaign attribution before switching on production.

What it costs. MoveData is a monthly subscription priced per organization, not per user. At the time of writing, the AppExchange listing shows US$179 per company per month for a single integration, while Raisely's integration page quotes A$249 per month. Confirm the current price with MoveData.

What it does not do. The sync runs one way, from Raisely into Salesforce. Changes made in Salesforce do not flow back to Raisely. MoveData does not publish its exact field list or matching rules, so ask for both during onboarding. Raisely's own UNICEF Australia story shows the typical starting point: exporting, transforming and importing Raisely data several times a week before the integration replaced it.

Section 06 · Zapier

How Do You Connect Raisely to Salesforce with Zapier?

Build a Zap that starts from a Raisely trigger or a Raisely webhook, finds the matching Salesforce record, and creates or updates it. It needs a paid Zapier plan, because Salesforce is a Premium app and webhooks and multi-step Zaps start on Professional. It suits low volumes and one or two flows, such as new donations or fundraiser totals, where a full integration would be more than you need.

Two ways to start the Zap. Zapier's Raisely app has ready triggers, including New Online Donation, New Person, New Profile and Profile Updated. It is the simplest start, but New Online Donation covers card and PayPal gifts only. If you also need offline donations, refunds or regular-giving events, use Webhooks by Zapier with Raisely webhooks instead, as below.

Before you build

  • A Zapier Professional, Team or Enterprise plan. Free plans allow only two-step Zaps and no premium apps (Zapier pricing).
  • My Domain enabled in Salesforce, and Zapier approved as an External Client App, as Zapier's Salesforce set-up guide describes.
  • The Salesforce object and fields you will write to. Our example updates a custom "Challenge Participant" object that holds each fundraiser's total.

Example: keep each fundraiser's total current in Salesforce

1. Create the Zap and catch the webhook.
→ In Zapier, create a Zap named, for example, "Raisely to Salesforce". For the trigger, choose Webhooks by Zapier and the Catch Hook event. Zapier gives you a custom webhook URL.
2. Add the webhook in Raisely.
→ In Raisely, open the campaign, then Settings > API & Webhooks, add a webhook, paste the Zapier URL and select the events you need. For fundraiser totals, choose profile.totalUpdated; for gifts, use the donation events in the next section.
3. Send a test and capture it.
→ Create a test offline donation in Raisely, then click Test Trigger in Zapier. It can take a minute or two before Zapier reports that it found a request.
4. Find the Salesforce record.
→ Add a Salesforce action with the Find Record by Query event, connect your Salesforce account, choose the object, and write a SOQL WHERE clause that matches on Raisely values, such as the profile name and campaign UUID.
Zapier action step set to the Salesforce app with the Find Record by Query action event
Step 4: the Salesforce "Find Record by Query" action in Zapier.
Zapier set-up for Find Record by Query on a Challenge Participant object, with a SOQL WHERE clause matching the participant full name and campaign UUID from the Raisely webhook, and success when nothing is found set to False
The WHERE clause matches the fundraiser's name and the Raisely campaign UUID. "Success when nothing is found" is set to False, so later steps are skipped if no record matches.
5. Continue only when a record was found.
→ Add a Filter step with the condition that the Salesforce record ID exists. Filter steps do not use Zapier tasks.
Zapier Filter step set to only continue if the Salesforce record ID from the previous step exists
Step 5: the Filter step stops the Zap when no Salesforce record matched.
6. Update the record.
→ Add a Salesforce action with the Update Record event, select the same object, use the ID from step 4 as the record to update, and map the Raisely fields, such as the profile total, to Salesforce fields.
Zapier action step set to the Salesforce app with the Update Record action event
Step 6: the Salesforce "Update Record" action writes the Raisely values to the matched record.
7. Test, then turn the Zap on.
→ Test each step, publish the Zap, then make offline and online test donations in Raisely, using Stripe's test card on the campaign's live site, and confirm the Salesforce record updates.

Watch for duplicate runs. For a fundraiser on a team, profile.totalUpdated fires for both the individual profile and the team or campaign profile, so one donation can produce two Zap runs. Add a Filter step before the search that only lets the profile type you want through.

Creating new records instead. To record each donation, rather than update a total, use Salesforce's Find or Create Record action for the donor and then Create Record for the Opportunity or Gift Transaction. Zapier's template "Create Salesforce records from new Raisely donations" is a starting point. In our example, the trigger and Filter steps use no tasks and the search and update use one each, so plan on about two tasks per donation (how Zapier counts tasks). Twopir Consulting builds and hardens Zapier automations like this through our Zapier integration services.

Section 07 · API and Webhooks

When Should You Build a Custom Raisely API and Webhook Integration?

When the packaged route does not fit your data model, your volumes, or your integration standards. Typical reasons are a heavily customized Salesforce org, several fundraising platforms that must share one matching engine, an existing MuleSoft or Workato platform, or a need for reconciliation and error logging you control. Raisely's API gives full access to profiles, registrations, donations, regular donations and people.

A custom build has two halves. On the Raisely side, webhooks push events and the Raisely API (base URL https://api.raisely.com/v3) fills gaps and back-loads history. On the Salesforce side, a receiver turns each event into records. Because Raisely authenticates a webhook with a shared secret rather than a Salesforce login, most builds put a receiver in front of Salesforce, such as integration middleware or a small hosted function, which checks the secret and then writes to Salesforce as the integration user. Salesforce's Apex REST services and Platform Events are the usual landing points.

Raisely rules

What Raisely's webhooks guarantee, and what they do not

The URL must answer a blank POST with HTTP 200 before Raisely saves it. An optional shared secret arrives as an Authorization: Bearer header. Any response other than 2xx counts as a failure, redirects are not followed, a failed delivery is retried four more times at hourly intervals, and a webhook that keeps failing is disabled. Events are not guaranteed to arrive in order, so donation.succeeded can arrive before donation.created.

Your rules

What the receiver must do as a result

Store Raisely's unique ID on every Salesforce record and upsert on it, so retries and out-of-order events update one record instead of creating two. Reply quickly and process in the background, so slow Salesforce writes do not trigger retries. Log every failure on a record admins can see, and run a scheduled reconciliation against the Raisely API to catch anything a disabled webhook missed.

Scope

Campaign-level or account-level webhooks

Webhooks added in the Raisely admin belong to one campaign. A webhook created through the API (POST /v3/webhooks) fires for every campaign in the account unless you pass a campaign UUID, which is usually what an organization-wide integration wants.

This is the pattern Twopir Consulting used for a nonprofit's Classy and Salesforce integration: webhooks for real-time donations, Apex matching on email and name before any contact is created, and nightly scheduled reconciliation with an error log. The same design carries over to Raisely.

Section 08 · Events

Which Raisely Webhook Events Should a Salesforce Integration Use?

Use donation.succeeded for completed online gifts, donation.created for offline gifts, and donation.refunded for refunds, plus the subscription events if you run regular giving. Raisely publishes 33 events. Most integrations need about a dozen, and choosing the right ones decides whether Salesforce holds only real, charged gifts.

Raisely eventWhen it firesWhat to do in Salesforce
donation.createdA donation is ready to charge, or an offline donation is addedCreate offline gifts; for online gifts, wait for success
donation.succeededAn online donation is chargedCreate or close the gift as received
donation.refundedA donation is refunded, fully or partlyRecord the refund against the gift
donation.updated / donation.deletedA donation changes, or an offline donation is deletedUpdate or remove the gift
subscription.created / .succeededA regular gift is set up, and its first payment succeedsCreate the Recurring Donation or Gift Commitment
subscription.rebilledA later instalment is collectedRecord the instalment
subscription.failing / .failedA rebill attempt fails, then the subscription failsFlag the donor for follow-up; update status
subscription.paused / .resumed / .cancelledThe donor changes the regular giftUpdate the commitment status
profile.created / profile.totalUpdated / profile.joinedTeamA fundraiser page is created, its total changes, or it joins a teamCreate the fundraiser campaign record and keep totals current
order.succeededA ticket or merchandise order is paidRecord event registration or purchase

Source: Raisely's list of available webhook events. Update events fire only when data actually changes. Leaving the event list blank subscribes to every event, which mostly adds noise and Zapier task usage.

Section 09 · Security

Does Payment Data Reach Salesforce, and Is the Integration Secure?

Card data never reaches Salesforce: Raisely itself never receives it. Raisely says card details go directly to Stripe through embedded fields, which lets it report under PCI SAQ-A. It stores data on Google Cloud in the United States and uses TLS 1.2 for all traffic, including the API. What flows into Salesforce is donor and gift data, which still needs careful handling.

  • Never map payment details. Sync amounts, dates, payment status and Raisely IDs, not card or bank data.
  • Protect the webhook. Set a shared secret and reject requests without it. Keep webhook URLs out of shared documents.
  • Limit the integration user. Grant only the objects and fields the sync writes, and review it at each release.
  • Respect consent. Map Raisely's communication preferences to Salesforce fields that your email tools honour.
  • Keep receipting where it is. Raisely issues automatic receipts and supports UK Gift Aid. NPSP has no native Gift Aid, so decide which system owns receipts and Gift Aid claims before you sync.

Sources: Raisely's security overview and the NPSP FAQ.

Section 10 · Pitfalls

Where Do Raisely and Salesforce Integrations Usually Go Wrong?

Most failures come from matching, event choice and silent errors, not from the connection itself. A sync that works on the first test donation can still create duplicate donors, count pending gifts as income, or stop without anyone noticing. Check these points before go-live and again after every Raisely campaign launch or Salesforce release.

Duplicate donors. Creating a contact for every gift, without matching on email first, splits giving history. Clean existing duplicates and agree matching rules before launch.
Pending gifts counted as income. Writing online gifts on donation.created records donations that may never be charged. Use donation.succeeded for online gifts.
Retries that create a second record. Raisely retries failed deliveries and does not guarantee order. Upsert on the Raisely ID so a repeat updates the same record.
A webhook disabled without anyone knowing. After repeated failures Raisely disables the webhook. Monitor errors and reconcile against the API on a schedule.
Regular giving left out. Syncing one-off donations only leaves failed and cancelled regular gifts invisible to the team that should follow them up.
No campaign hierarchy. Attaching every peer-to-peer gift to the parent campaign hides which fundraisers and teams raised it. Use child campaigns per fundraiser page.
Section 11 · Choose

Which Raisely to Salesforce Route Should Your Nonprofit Choose?

Start with MoveData if you run standard NPSP or Agentforce Nonprofit and want every Raisely gift in Salesforce. Choose Zapier for one or two light flows. Build on the API when your data model, volumes or standards go beyond both. Answer the questions below in order; the first "yes" usually points to the route.

1. Do you only need one or two simple flows, at low volume?
→ Zapier, using the Raisely triggers or webhooks, with matching and filters as above.
2. Are you on NPSP or Agentforce Nonprofit with a largely standard data model?
→ MoveData, extended with Flow for your custom fields.
3. Do several giving platforms, a custom data model or an existing integration platform need to share one design?
→ A custom build on the Raisely API and webhooks, through your middleware.

Ready to integrate. Your Salesforce edition has API access. You have chosen NPSP or Agentforce Nonprofit. Donor duplicates are under control. Someone owns the mapping and will check the error log after go-live.

Fix this first. You are on Essentials or Professional without API access. A move from NPSP to Agentforce Nonprofit is planned but not done. The org holds many duplicate donors. Nobody has decided which system owns receipts and Gift Aid.

Section 12 · Bottom Line

The Bottom Line

A Raisely Salesforce integration ends manual exports and gives fundraising, finance and leadership one giving history. The route matters less than the groundwork: the right data model, clean donors, the right events, and matching on Raisely's IDs. Twopir Consulting builds donation-platform integrations for nonprofits, including Raisely, Classy and NPSP to Nonprofit Cloud work, as our Salesforce for nonprofits page describes.

  1. 1

    Choose NPSP or Agentforce Nonprofit before you map a single field.

  2. 2

    Confirm API access and create a dedicated integration user.

  3. 3

    Pick the route: MoveData for most, Zapier for light flows, a custom build for complex needs.

  4. 4

    Subscribe to the events you need, write online gifts on success, and upsert on Raisely IDs.

  5. 5

    Test refunds and failed regular gifts in a sandbox, then monitor errors after go-live.

Ready to Start

Get Every Raisely Gift into Salesforce, Accurately

Tell us how your Raisely campaigns and Salesforce org are set up today. We will recommend the route, the data mapping and the matching rules your nonprofit needs.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Raisely does not build its own Salesforce connector. Its official Salesforce integration is built and run by MoveData, a partner app on AppExchange that syncs Raisely data into NPSP or Agentforce Nonprofit in real time. The alternatives are Raisely's API and webhooks for a custom build, or Zapier for simpler, no-code flows.

MoveData is a monthly subscription priced per organization. At the time of writing, its AppExchange listing shows US$179 per company per month, while Raisely's page quotes A$249 per month, so confirm with MoveData. The Zapier route needs a paid Zapier plan, from US$19.99 per month, and a custom build has build and maintenance costs.

Yes. MoveData supports both. In NPSP, Raisely donations become Opportunities and regular gifts become Recurring Donations. In Agentforce Nonprofit, formerly Nonprofit Cloud, they become Gift Transactions and Gift Commitments, and donors become Person Accounts. Zapier and custom builds work with either model, but you design the mapping yourself.

No. MoveData processes data from Raisely into Salesforce, and changes made in Salesforce do not flow back to Raisely. Zapier can write to Raisely through actions such as Create or Update a Person or Add a Tag, and a custom build can call the Raisely API, but most nonprofits treat Salesforce as the downstream system of record.

Professional or above. Salesforce is a Premium app on Zapier, and webhooks and multi-step Zaps also start on the Professional plan. The free plan allows only two-step Zaps without premium apps. Salesforce also needs My Domain enabled and Zapier approved as an External Client App before the connection works.

Use donation.succeeded for online gifts, because it fires only when the payment is charged, and donation.created for offline gifts. Add donation.refunded for refunds and the subscription events for regular giving. Raisely does not guarantee the order of events, so match records on Raisely's IDs to avoid duplicates.

Any edition with API access: Enterprise, Unlimited, Performance and Developer include it, and Professional needs the Web Services API add-on. Group and Essentials cannot get API access. Nonprofits using Power of Us donated licences are on Enterprise Edition, so they meet this requirement.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies, and the nonprofits that serve their communities, solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including NPSP, Nonprofit Cloud and fundraising-platform integrations, for 500+ clients over 12+ years.