Use Cases
Some concrete examples of Bridgit automations across fundraising, marketing, CRM and finance workflows. These example use cases really only scratch the surface, Bridgit is powerful and versatile and can support many, many more.
Automating appeal coding with AI
How Wales Air Ambulance automated GoFundMe appeal coding with 98% accuracy Wales Air Ambulance now codes its GoFundMe fundraising pages to the right appeal and campaign automatically, with around 98% accuracy, using rules it wrote in plain English with Bridgit's AI Transformation Builder. CharityWales Air Ambulance Charity Platforms connected to BridgitGoFundMe, JustGiving, Enthuse, MuchLoved and Raisely CRMRaiser's Edge NXT FocusAutomatic appeal and campaign coding for GoFundMe ResultAround 98% coding accuracy About Wales Air Ambulance Wales Air Ambulance is the only air ambulance charity dedicated to the people of Wales, bringing advanced critical care to patients across the whole country 24 hours a day by helicopter and rapid response vehicle. It is funded entirely by donations, raising £13 million every year to keep the service running. With a team of around 100 staff and no in-house developers, the charity relies on tools its fundraising and data teams can run themselves. The challenge GoFundMe is one of the most popular ways for supporters to raise money for Wales Air Ambulance. People use it to tell their own story: a sponsored run, a birthday, a tribute to someone they've lost, or a thank you to the crew who saved a loved one. That variety is exactly what made the data hard to handle. Gifts from a single platform could belong to many different appeals. Coding each one correctly needed someone who knew every appeal, every campaign and all their nuances. For years the team monitored new pages, created supporter records by hand in Raiser's Edge and kept fundraising totals in notes on the record. That worked, until the charity wanted to introduce propensity modelling, with our friends at Dataro, and a new suite of digital marketing tools. Supporters fundraising on third-party platforms sat outside the reach of both. As Laura Coyne, Fundraising Operations Manager at Wales Air Ambulance, explains: "Getting third-party data into Raiser's Edge properly took about half a day of specialist setup per platform, and only one (superstar) on the team had those skills. So platforms like GoFundMe, where gifts land in lots of different appeals, stayed manual." The solution Wales Air Ambulance connected GoFundMe to Bridgit, alongside JustGiving, Enthuse, MuchLoved and Raisely. The breakthrough came from Bridgit's AI Transformation Builder. Laura already had the knowledge written down: a 12-page document setting out how the charity codes third-party fundraising pages, with nine rules evaluated in priority order. She explained those rules to Bridgit's AI in plain language, much as she would brief a new colleague. Bridgit's AI turned them into a precise, sophisticated rule that reads each page's title and description and returns the right appeal and campaign. Laura describes it simply: "I spoke to Bridgit's AI like a colleague I was training, explaining the rules for each appeal. No coding required, because I cannot code." The rules handle the nuances that defeat simple keyword matching: What the fundraiser writesHow it's codedWhy "Donations in memory of Mum instead of flowers"In Memory DonationsPassive giving in someone's memory "We're running in memory of Dad"In aid ofA sponsored activity beats in-memory language "Donations instead of presents for my birthday"CelebrationGifts marking an occasion "For my 50th birthday I'm climbing Snowdon"In aid ofAn activity beats a birthday "We're holding a party for Mum's birthday"CelebrationParties stay Celebration, even though they're events "I'm running the Cardiff Half"Cardiff HalfA named event always comes first Good to know: Bridgit's AI Transformation Builder never reads your supporter records. You describe your rules in plain English and the AI turns them into a sophisticated piece of logic. From then on, Bridgit's own system applies that logic to every record in exactly the same way, so results are consistent and predictable, supporter data stays private and running costs stay low. Bridgit's AI gave Laura a working first draft, so she never had to start from a blank canvas. She tested it, adjusted it where it got things wrong and added key Welsh words for supporters who write in Welsh. She also set a fallback appeal for each platform, so nothing is left uncoded. As Laura puts it: "Bridgit's AI drafted the appeal coding rules and I refined them, rather than having to start from scratch." Going further: identifying service users Many GoFundMe pages exist because Wales Air Ambulance cared for the fundraiser or someone close to them. There's no checkbox for that, but it's often in the story. Laura created a second field that looks for phrases such as "I was rescued by" and flags the supporter as a likely service user, meaning someone the charity's crews have cared for or their family. That way the charity can make sure its communications are appropriate and sensitive. In Laura's words: "People use GoFundMe to tell their story in their own words. With Bridgit, I can have a field read a fundraising page's description, look for phrases like 'I was rescued by' [one of our helicopter crews] and identify them as a service user. This important context just wasn't findable before Bridgit." The results The GoFundMe bridge runs on a schedule. When it does, the team downloads a CRM-ready spreadsheet from Bridgit, with every field formatted and every appeal and campaign coded, and imports it into Raiser's Edge NXT. Around 98% of pages coded to the correct appeal and campaign GoFundMe data checked against the PayPal Giving Fund payout before going live, and "it all tallied wonderfully!" according to Laura GoFundMe supporters are now within reach of the charity's propensity modelling and digital marketing tools Supporters who were cared for by the charity, or whose families were, can be recognised and treated with care For Laura, it's a big step forward: "We're finally at a place where we might achieve what fundraisers call the golden record: a 360 view of a supporter's interests, motivations, activity and giving history." What's next: straight into Raiser's Edge NXT Data from Raisely already flows directly into Raiser's Edge NXT through Bridgit, with no spreadsheet step at all. The next stage is to bring GoFundMe and the charity's other platforms onto the same direct route, so coded data lands in the CRM automatically. Laura sums up the reaction inside the charity: "Honestly, you are the saviour of the charity. Everyone's asking how we've suddenly solved this, and I just say: 'Bridgit'." Book a call to see how Bridgit can automate appeal coding for your charity.
Automating event fundraising data into supporter nurture campaigns
Charities running mass participation events need supporter data to move quickly from fundraising platforms into their email and journey tools. This use case shows how Bridgit automates that flow so supporters are added to the right nurture campaigns without manual exports, uploads or delays. Real Life Example: How The Myton Hospices automated event sign-ups into Dotdigital to power timely supporter journeys Before Bridgit At The Myton Hospices, the digital marketing team used Funraisin to manage event fundraising and Dotdigital to run supporter journeys and nurture campaigns. To make this work, event sign-up data needed to be moved from Funraisin into Dotdigital quickly and accurately so supporters could receive timely, event-specific communications. Doing this manually meant regularly exporting data, cleaning it, uploading it into the correct Dotdigital lists and context-switching between platforms while events were live and sign-ups ongoing. This created friction for the team and introduced the risk of delays or human error at critical moments in the supporter journey. Life with Bridgit Using Bridgit, Myton set up automated bridges that flow data directly from Funraisin fundraising campaigns into the appropriate Dotdigital lists. For their Moonlight Walk event, this meant supporter sign-ups were automatically routed into an event-specific list in Dotdigital, triggering the correct nurture and engagement campaigns without manual intervention. With full control over data transformations, the team can format names, standardise date types and combine fields where needed so data arrives in Dotdigital clean, consistent and ready to use. As new events are launched, additional bridges can be configured so supporter data is automatically routed to the correct Dotdigital lists each time. Impact Faster, more reliable delivery of event sign-up data into Dotdigital Reduced manual data handling during live campaigns Lower risk of errors and missed communications Less context switching for the digital and fundraising teams A scalable setup that supports multiple events using unlimited bridges on the Bridgit Connect plan It’s like having a small team of API developers at your fingertips without the very costly agency fees or contractor fees. Bridgit is saving our supporter care team hours already. - Dan Brown, Digital Marketing Manager, The Myton Hospices
Automating MuchLoved income processing for Donorflex CRM
Charities using MuchLoved often spend days each month cleaning, coding and reformatting donation data before it can be imported into Donorflex (or whichever CRM they are using). This use case shows how Bridgit reduces that workload by automating the bulk of income processing and delivering a Donorflex-ready import file. Real Life Example: How Rowans Hospice reduced MuchLoved income processing time by over 75% (with further reductions expected) Before Bridgit At Rowans Hospice, processing income from MuchLoved was one of the most time-consuming admin tasks in the fundraising calendar. Once per month, following the MuchLoved payout around the 15th, the Individual Giving and Legacy Fundraising Manager would spend around 2 full days manually preparing and importing donation data into Donorflex. The work was detailed and unforgiving. It included: Cleaning and standardising first and last name casing Applying salutations Removing email addresses where no communications consent was given Adding mandatory CRM and finance data such as donor type codes, category numbers, audit codes, income stream codes, account IDs and soft credit information Handling Gift Aid income separately, with additional codes applied in different rows All of this had to be done across hundreds of rows for each payout. Once cleaned, the data then needed to be transferred into Donorflex’s import template, a spreadsheet 130 columns wide, before finally being uploaded into the CRM. It was slow, repetitive and carried a constant risk of error. Life with Bridgit Bridgit automated all of the tasks above using custom, charity-specific rules. Rowans Hospice now has a scheduled bridge that runs automatically once per month, aligned with MuchLoved payouts. The bridge applies almost all of the required data cleaning, transformations and coding, then delivers a Donorflex CRM-ready spreadsheet. The Fundraising Manager receives a Donorflex-ready import file, then completes a short final check and a handful of tweaks that Bridgit cannot yet automate. After that, it’s ready to upload into Donorflex. Impact 12 hours saved every month (reduced from 16 hours to around 4) Further reductions expected, with upcoming automations likely to bring this down to under 3 Cleaner, more consistent data Lower risk of errors A happier, less overloaded fundraising team So the process used to take me a day and a half to two days to complete… I just did it in a maximum of 4 hours. AMAZING!!! - Alexis Trowbridge, Individual Giving and Legacy Fundraising Manager, Rowans Hospice
Keeping supporter communication preferences accurate and up to date
Charities collecting donations through fundraising platforms need to ensure supporter details and communication preferences are accurately reflected in their CRM. This use case shows how Bridgit helps charities keep donor records clean, consistent and GDPR-compliant by automatically mapping consent data from MuchLoved into Donorflex. Real Life Example: How The Myton Hospices keeps supporter communication preferences in sync between MuchLoved and Donorflex Before Bridgit At The Myton Hospices, donations made through MuchLoved captured up-to-date supporter details and communication preferences. However, getting that information into Donorflex accurately required manual handling. Donorflex relies on specific internal codes to represent communication preferences, meaning data exported from MuchLoved had to be carefully transformed before import. This included ensuring consent-related fields were populated correctly, columns were ordered to match Donorflex’s import requirements and values aligned with existing CRM standards. Manually managing this process increased the risk of inconsistencies, outdated preferences and errors, particularly as supporter data changed over time. Life with Bridgit Using Bridgit, Myton set up a bridge that automatically transforms MuchLoved donation data into a Donorflex-ready format with communication preferences correctly applied. Custom rules and transformations map MuchLoved consent data into the appropriate coded fields in Donorflex, ensuring supporter contact permissions are always up to date. The bridge also standardises data to match CRM requirements, including: Applying title case to names Reordering spreadsheet columns to match Donorflex import templates Setting required codes such as country codes (e.g. United Kingdom to GBR) and other consistency fields The result is a clean, compliant import file that aligns with Donorflex CRM's data model and reflects the latest supporter preferences captured at the point of donation. Impact More accurate and up-to-date supporter communication preferences in Donorflex Reduced risk of contacting supporters incorrectly Reduced compliance and GDPR risks Improved data consistency across fundraising and CRM systems Less manual effort required to prepare and validate consent-related data Greater confidence in CRM data as a source of truth It’s like having a small team of API developers at your fingertips without the very costly agency fees or contractor fees. Bridgit is saving our supporter care team hours already. - Dan Brown, Digital Marketing Manager, The Myton Hospices
Standardising fundraising data, campaign attribution and financial reconciliation in Salesforce
Charities using multiple fundraising and payments platforms often struggle to land consistent, reportable data in Salesforce. This use case shows how Bridgit helps charities standardise incoming data, automate campaign attribution and prepare Salesforce-ready uploads that support accurate reporting and reconciliation. Real Life Example: How ARC Cancer Support Centres standardised multi-platform fundraising data for Salesforce reporting and reconciliation Before Bridgit At ARC Cancer Support Centres, fundraising data was coming from multiple platforms, each with different structures, naming conventions and reporting requirements. A key challenge was campaign attribution. Salesforce expects specific campaign codes in order to organise, report on and reconcile income correctly. Assigning these codes manually meant reviewing donation and event data line by line and setting campaign values by eye, one of the heaviest and most error-prone admin tasks for the fundraising and finance teams. Preparing data for upload also required spreadsheets to conform exactly to ARC’s Salesforce uploader tool, adding another layer of manual formatting and validation. This made backdated reconciliation particularly time-consuming, with historic data stretching back up to two years needing careful review before it could be confidently imported. Life with Bridgit Bridgit is being used to standardise and prepare fundraising data before it reaches Salesforce, starting with iDonate and expanding to other platforms including Stripe, Donorbox and Eventmaster. For campaign attribution, Bridgit applies a series of lookup rules that automatically assign Salesforce campaign codes based on keywords found in fundraising page titles or event names. For example: Pages containing the word “swim” are assigned the Dip in the Nip campaign code Pages containing “tennis” are assigned Tennis for Cancer 2025 These rules can be easily updated over time, allowing ARC to add new keywords and campaigns without manual rework. Bridgit also transforms incoming data so it conforms to ARC’s Salesforce uploader requirements, delivering spreadsheets that are ready to import and consistent across platforms. Alongside this, Bridgit is supporting the team with backdated uploads to help bring historic data into Salesforce in a structured and reportable way. In progress Work is currently underway to further support financial reconciliation by capturing and logging payout dates alongside donation dates. This will allow ARC to report accurately on when funds are received in the bank and reconcile platform payouts against Salesforce records. This functionality will be rolled out as part of the ongoing setup. Impact Significant reduction in manual campaign code assignment More consistent, Salesforce-ready data across fundraising platforms Faster and more reliable historic data reconciliation Improved confidence in Salesforce reporting for fundraising and finance teams A scalable setup that can expand to additional platforms over time With thanks to the project team, including: Hannah Hynes, Database & Donor Care Executive Stephanie Nolan, Head of Fundraising & Communications Paul Switzer, Head of Finance & Transformation, & Deputy CEO