Access Charity CRM
CRMConnect AI agents to Access Charity CRM (formerly thankQ), the fundraising CRM from The Access Group. Agents record donations and pledges, keep constituent records current, log communications, and track memberships, events, and Gift Aid declarations.
What This Integration Enables
Access Charity CRM is a ledger before it is a pipeline. A record here is not a sales opportunity, it is a supporter's giving history, their consent, their membership, and in the United Kingdom their Gift Aid position, which the charity reclaims tax against. That changes what automation is for. The goal is not to move records faster through stages, it is to make sure every gift, communication, and declaration lands on the right person with the right codes, and that the ones that cannot be settled automatically are handed to a fundraiser instead of guessed.
FlowRunner agents work the full constituent record through this connector: matching and creating contacts, recording payments and pledges, logging communications, booking supporters onto events, opening and canceling memberships, and reading legacy records. Two design details in Access Charity CRM shape how agents use it. Contacts are addressed by serial number, so every payment, pledge, membership, and booking hangs off that identifier, and Get Lookup Values exists because payment methods, communication categories, action statuses, and relationship types are defined per organization rather than fixed by the vendor. An agent resolves those values first and writes second. Everything it cannot resolve becomes an automation exception for a person, which is what human-in-the-loop orchestration is for.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Offline giving reconciled without a rekeying week
The finance team drops a bank file into Google Sheets each Monday. The agent reads the rows, calls Search Contacts on name, email, and postcode for each donor, and uses Get Lookup Values to resolve the payment type and destination codes this charity actually uses. Confident matches go straight to Record Payment against the donor's serial number, with the external reference field carrying the bank line ID so the two systems can be reconciled later. Rows that match nobody, or match two people, are collected into a single named list for the database officer. The fundraiser spends the morning on twelve ambiguous rows instead of four hundred clean ones.
Event bookings that confirm themselves
Signups for a fundraising dinner arrive through a web form. The agent runs Search Events to find the right event, Search Contacts to see whether the attendee already exists, and Create Contact when they do not. Create Event Booking registers them with their dietary and access details, and Gmail sends the confirmation. Log Communication then writes that confirmation back onto the supporter record, so the next fundraiser to open the contact sees the dinner invitation, the booking, and the confirmation email in one history rather than three systems.
Stewardship that reacts to the gift, not to the calendar
After Record Payment posts a gift above the charity's major donor threshold, the agent calls Get Contact with the relationship and communication includes to see who owns the relationship and when they last spoke to the donor. Create Action opens a follow-up task for that fundraiser with a due date, and Log Communication records the thank-you that Gmail sends. When the gift arrives from someone already carrying a pledge, Search Pledges checks whether this payment satisfies an instalment before the agent creates anything, so a scheduled gift is not double-counted as a new one.
Human-in-Loop Highlight
A Gift Aid declaration is not a CRM field. It is a statement the donor makes about their own tax position, and it is what the charity's reclaim from HMRC rests on. This connector can call Create Gift Aid Declaration, and it has no matching action to withdraw one. So when the import agent finds a donor whose paper form has the Gift Aid box ticked but whose Access Charity CRM record carries no declaration, it stops short of writing it. It records the gift with Record Payment, pulls the supporter's existing declarations and address history with Get Contact, and posts the case to the fundraising manager in Slack: "Gift of GBP 250 recorded against serial 41822, J. Hartley. The paper form ticks Gift Aid, the CRM record has no declaration, and the address on the form does not match the address on file. Create a declaration, or route this back for a fresh form?" The agent does the matching and the evidence gathering. A person decides whether the charity is entitled to make the claim. Cancel Membership sits behind the same rule for the same reason: this connector can end a membership, and it cannot reinstate one.
Agent Capabilities
22 actionsConstituents
4- Search Contacts Searches the constituent database with filters for name, email, postcode, contact type, or serial number, returning a paginated collection. Used as the match step before any create, so imports do not manufacture duplicate supporters.
- Get Contact Retrieves a single contact by serial number, with optional include flags that expand addresses, consent, preferences, profiles, groups, relationships, payments, and communications. Used to load the whole relationship before a stewardship or data quality decision.
- Create Contact Creates a constituent from a key name plus any known details, with role flags for volunteer, funder, prospect, committee, and alumni. Used when a form, event signup, or donation introduces someone the database has never seen.
- Create Relationship Links two contacts to each other with a relationship type drawn from the account's own lookup values. Used to connect a donor to their household, employer, or trust so soft credit and stewardship are not split across records.
Donations and Pledges
6- Search Payments Returns a paginated set of payments filtered by contact, date range, or other criteria. Used for reconciliation sweeps and to check whether a gift has already been posted.
- Get Payment Retrieves a single payment record in full. Used to confirm the source, destination, and amount before a downstream write to finance systems.
- Record Payment Posts a donation or gift against a contact's serial number with its source, destination, and Gift Aid detail. The workhorse action for turning bank files, online giving, and event income into supporter history.
- Search Pledges Returns pledges matching the supplied filters. Used to check whether an incoming payment satisfies an existing commitment before it is treated as a new gift.
- Create Pledge Creates a recurring or scheduled giving commitment for a supporter. Used when a donor signs up to give regularly rather than once.
- Search Legacies Returns legacy records matching the supplied filters. Used for reporting on legacy pipeline without exporting the whole database.
Gift Aid
1- Create Gift Aid Declaration Records a supporter's Gift Aid declaration so the charity can reclaim tax on their giving. This connector creates declarations and does not withdraw them, so agents gather the evidence and put the decision in front of a person.
Communications and Actions
4- Search Communications Returns the communication history matching contact, date, or category filters. Used to check what a supporter has already been sent before adding to it.
- Log Communication Records an inbound or outbound communication against a contact, with an optional external reference for cross-system matching. Used so email, calls, and letters sent by other tools still land in the supporter's single history.
- Search Actions Returns tasks matching status, owner, or date filters. Used to audit open fundraiser follow-ups.
- Create Action Opens a follow-up task for fundraising staff with a status drawn from the account's lookup values. Used to put stewardship on a real list instead of in someone's memory.
Memberships
3- Search Memberships Returns memberships matching the supplied filters. Used for renewal sweeps and lapsed member reporting.
- Create Membership Opens a membership for a supporter against a scheme and band. Used when a supporter joins or upgrades.
- Cancel Membership Cancels an existing membership. This connector has no reinstate action, so cancellations are treated as a human decision rather than a cleanup step.
Events
3- Search Events Returns events matching the supplied filters. Used to resolve the right event before booking anyone onto it.
- Create Event Creates a fundraising or supporter event record. Used when an event is planned outside the CRM and needs to exist inside it before bookings arrive.
- Create Event Booking Books a supporter onto an event with their attendee details. Used to turn form signups into attendance records without a spreadsheet in between.
Reference Data
1- Get Lookup Values Retrieves the account's own lookup values for fields such as payment type, communication category, action status, relationship type, and membership scheme band, with several lookups fetchable in one call. Used before every write, because these options are defined per organization rather than fixed by the vendor.
Frequently Asked Questions
What can FlowRunner do with Access Charity CRM?
FlowRunner agents can run Search Contacts, Get Contact, and Create Contact in Access Charity CRM, plus 19 more actions.
Does connecting Access Charity CRM to FlowRunner require OAuth?
No. Access Charity CRM connects to FlowRunner with an API key, no OAuth flow required.
Can Access Charity CRM trigger a FlowRunner workflow automatically?
Access Charity CRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Access Charity CRM
$100 in credits. No card required. Connect in minutes.