· Vimal Hari · Business Automation (n8n) · 6 min read

How to Sync Online Donations into Raiser's Edge NXT

What it takes to record online gifts and Gift Aid declarations in Raiser's Edge NXT automatically, without duplicate donors or double entry, from a live build.

What it takes to record online gifts and Gift Aid declarations in Raiser's Edge NXT automatically, without duplicate donors or double entry, from a live build.

Many charities take donations on one platform and keep supporter records in Raiser’s Edge NXT, with a person in between keying each gift across. It works, but gifts reach the CRM late, Gift Aid declarations are typed by hand, and every so often a donor ends up with two records.

In October 2026 we replaced that step for a UK children’s charity, connecting its iRaiser donation platform to Raiser’s Edge NXT through the Blackbaud SKY API. Gifts now appear in the CRM within minutes. This guide sets out what such a sync has to do and the decisions that matter, whichever giving platform you use. The project itself is written up in our online donations sync case study.

What the sync has to do

For each donation it must:

  1. receive the donation from the giving platform and keep a record of it;
  2. find the right supporter, or create one;
  3. create the gift with the fund, campaign and appeal your team would have chosen;
  4. write a Gift Aid declaration if the donor opted in;
  5. tell a person about anything it could not decide.

Step 5 is what makes the rest trustworthy. An integration that always writes something will sooner or later write something wrong.

Capture first, process second

Keep receiving a donation separate from acting on it. In our build one workflow receives each delivery on an authenticated webhook, replies at once and stores the raw payload. A second workflow does the matching and the writing.

The split means a fault in processing, such as the CRM being unavailable, never loses a donation: the delivery is already logged and can be replayed. It also gives you a complete record of what the platform actually sent, which settles most later questions.

Two practical points when you set up the webhook:

  • Do not filter out automated senders. Some webhook tools reject requests that look like bots by default. A giving platform’s deliveries are automated by definition, and that setting will silently refuse them.
  • If you restrict by IP address, read the right one. Behind a content delivery network the sender appears as the network’s address. Use the forwarded client address instead.

Make it safe to repeat

Platforms resend. A delivery that timed out is sent again, and the same donation arrives twice. Keep a sync log keyed on something that identifies the donation itself, such as the event type plus the platform’s donation reference, and skip anything already marked as written. Do not key on a delivery ID: in our case it included the time of sending, so a resend would not have matched.

Check the CRM as well as your own log

Your log only knows what the integration wrote. During the changeover your team may still be keying gifts by hand, so the same gift can already be in Raiser’s Edge.

Before writing, we search the matched donor’s existing gifts for the payment provider’s transaction reference. If it is there, nothing is written and the gift is flagged. On our project this caught the first real test gift, which a member of the team had already entered by hand.

Match donors without guessing

The SKY API’s constituent search (GET /constituent/v1/constituents/search) takes free text, so matching is a rule you design:

  • match on email address first;
  • if that finds nobody, match on surname and postcode;
  • one match: use it;
  • no match: create a new constituent, with whatever code your team gives new online donors;
  • more than one possible match: stop, and ask a person.

The last rule is the important one. A wrong guess creates a problem that someone has to find later. A held gift costs a short delay.

Code the gift the way your team does

A gift is created with POST /gift/v1/gifts. The fields are simple; the values are not. Fund, campaign, appeal, gift subtype, payment method and reference all follow conventions that live in your team’s heads.

Read before you write. We pulled several months of hand-entered online gifts through the API and copied the pattern exactly: the same subtype, the payment provider’s transaction ID as the reference, the same acknowledgement status.

The appeal is the hard part. The giving form does not know which mailing prompted the donation. The dependable fix is to pass an appeal code from the form, which means every form and every link in an email has to carry one. Where a code is missing we fall back to the most recent appeal the donor received and flag the gift for review. We tested that fallback against gifts the team had coded by hand, and it agreed with their choice for only about six in ten, which is why it is always flagged and never trusted.

Gift Aid declarations

For UK environments Blackbaud provides a Gift Aid API, and a declaration is written against the donor with POST /gar-gfacr/v1/taxdeclarations/constituents/{constituent_id}. Write it in the same run as the gift, with the declaration source and method your team already uses for online gifts, so that a report run next year reads the same for automated and hand-entered declarations. Agree with your finance lead whether a new declaration is written for every opted-in gift or only when the donor has none.

Regular gifts and refunds

A monthly donation is two things: a recurring gift, created when the donor signs up, and a payment against it each month. Each payment must be linked to the existing recurring gift. If it is entered as a separate one-off donation, your regular giving reports will be wrong.

We do not edit the CRM automatically for refunds. A refund is flagged for a person, because the right correction depends on the circumstances, such as whether Gift Aid has already been claimed.

Expect bursts

Blackbaud allows 10 calls a second. One-off gifts never come near that. Monthly payments do, because the platform takes them in a batch. Our first monthly batch arrived as 15 payments in 11 seconds, and several calls were refused with a 429. Nothing was lost: the capture log held every delivery and the sync log showed which had not been written, so we replayed those. We then added a retry to every SKY API call that waits for the time given in the Retry-After header. Build that in from the start. Our guide to SKY API rate limits and quotas explains the limits.

Go live in stages

  1. Dry run. Process real donations and report what would be written, without writing.
  2. Compare. Put the dry run beside what your team entered for the same gifts. Differences are either bugs or conventions nobody had mentioned.
  3. Supervised go-live. Check the first live gifts together, and agree the moment from which nobody keys online gifts by hand.
  4. Daily exceptions email. One message listing only what needs a person, with record IDs and reasons and no donor personal data.

What it runs on

We built this with n8n, which suits a low-volume flow that people need to be able to inspect. The same design works in code. The application that talks to the SKY API has to be approved by your Raiser’s Edge administrator, who can withdraw that approval at any time.

If your team is still re-keying online gifts, see Raiser’s Edge NXT integration or tell us which platform you take donations on.

Back to Blog

Related Posts

View All Posts »