|
19th November 2026
|
3 min read

Connecting Beacon CRM to your charity website: forms, donations and more

Beacon CRM is built for charities, and much of its value comes from what you connect to it. What a charity website can send to Beacon, from embedded forms to the API.

Beacon is a CRM built for charities, and much of its value comes from what you connect to it. If supporters give, join or book through your website, the cleanest setup sends each of those straight into Beacon, so nobody retypes a form into a spreadsheet.

We are connecting Beacon to the Rabbit Welfare Association & Fund's website at the moment, starting with its forms. This is what a charity website can do with Beacon, from the simplest option to the most bespoke.

The simplest route: Beacon's own forms on your site

Beacon has its own branded forms for donations, memberships and event tickets. Its WordPress integration lets you link to those forms or embed them in a page, and the same embed code works with Wix, Drupal and most other website builders.

Embedded forms keep everything in one system: the supporter's details, the payment and the Gift Aid declaration land in Beacon together. The trade-off is design control, since the form follows Beacon's styling more than your site's.

  • Donations, one-off and recurring, with Gift Aid built in
  • Memberships and renewals, including member numbers and an optional extra donation
  • Event tickets with capped availability, time slots and group tickets

Payments, Direct Debit and Gift Aid

Beacon takes card payments through Stripe and PayPal, and Direct Debit through GoCardless. Its Gift Aid integration submits claims to HMRC directly, which takes one of the most tedious jobs off a small charity's year.

If your website already takes payments through one of those providers, check how each payment will meet the supporter's record in Beacon before you rebuild anything.

Your own website forms, sent to Beacon

Some charities want forms that match the rest of their site: a volunteer application with their own questions, a contact form, a referral or a newsletter sign-up. Those can stay as website forms and pass their answers to Beacon.

There are two ways to do it. Zapier connects a form to Beacon without code and suits simple records at low volume; Beacon's REST API lets a developer create and update records directly, which suits anything that has to be reliable, matched to existing contacts or kept away from third-party services.

Four decisions before you connect a form

  • Which Beacon record each answer should create or update
  • How a returning supporter is matched, so you do not create duplicates
  • What consent wording the form shows, and where that consent is stored
  • Who on the team is told when a new record arrives

Fundraising platforms and the tools around them

Plenty of giving happens away from your website. Beacon imports donations and fundraisers from JustGiving, Enthuse and Fundraise Up, and takes CSV imports from Facebook Donate, CAF Donate and others.

For email it connects to Mailchimp and Dotdigital, and for finance to Xero, with exports for Sage and QuickBooks. Google Analytics can track how your Beacon forms perform.

Where the website and the CRM meet

The website is usually the front door, and Beacon is where the relationship is managed. Planning the two together means every form has a clear job, supporters are not asked for the same details twice, and staff stop copying data between systems.

For RWAF the first step is connecting its forms; what follows depends on what the team wants Beacon to hold. If you use Beacon, or are about to, and your website needs to work with it, see how we approach charity web design or book an intro call.

Join the newsletter

"*" indicates required fields

Latest updates

View all