Access Charity CRM Make integrationAutomate Access Charity CRM with Make.
Donors, events and payments can reach your CRM without anyone retyping them. The Access Charity CRM Make integration offers 22 action modules. This page shows fundraising and operations teams what each one does and how to build a first working flow.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Access Charity CRM Make integration do?
It links your Access Charity CRM account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Other apps then feed the CRM with contacts, event bookings and payments, and the CRM feeds them back, without copy and paste.
A donor file that updates itself. A donation form in another app starts the scenario, Create a Contact or Update a Contact keeps one record per supporter, and Create a Single Payment adds the gift to it.
Events without double entry. An approved event becomes a record through Create an Event, then each registration lands with Create an Event Booking and Create an Event Attendee.
A complete contact history. Log an Email and Create a Communication keep a trace of every exchange sent from other tools, and Get Payments can feed a thank-you flow or a donations sheet.
Two limits to know. The app has no trigger, so a scenario starts from another app or from a schedule. And Make itself warns that its documentation for Access Charity CRM is limited, so test each module before trusting it. If you are still choosing a platform, the n8n vs Make comparison lays out the criteria, the Make pricing page explains operations, and the Make training gets a team started.
How do you connect Access Charity CRM to Make?
- 01
Add a module and open the connection
In your scenario, add any Access Charity CRM module and click Create a connection. A connection is your CRM account linked to Make once, then reused by every module of the app.
- 02
Name it so you find it later
Giving the connection a name is optional, yet handy when several accounts or environments exist. Something like the name of your charity makes the right one easy to pick in each module.
- 03
Authorize Make and save
Depending on what the app asks for, approve Make on the Access Charity CRM page that opens, or paste the key the app gives you. Then click Save and the module fields become available.
Your first scenario with Access Charity CRM
GoalWhen a donation form is submitted in another app, Make creates or updates the donor in Access Charity CRM and records the payment.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the form or payment app your donors already use as the starting point.
- 02
Add the donor module
Click the + on the right, search Access Charity CRM and choose Create a Contact or Update a Contact. Create the connection, then map the donor details sent by the first module.
- 03
Record the gift
Add Create a Single Payment after it. The same connection is reused, and you map the amount data from the form plus the contact returned by the previous module.
- 04
Test with Run once
Submit a test donation, then click Run once. Open each module to read the bundle it received (one bundle is one item, here one donor) and check the CRM record.
- 05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on a bundle counts as one operation on your plan.
The 22 Access Charity CRM modules in Make
Access Charity CRM gives you 22 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Communication
ActionIn the docs onlyEvery exchange with a supporter can land in Access Charity CRM as a communication record, so nobody types it in twice. The module adds one record for each bundle it receives.
Create a Contact or Update a Contact
ActionIn the docs onlyOne module covers both cases: a new person gets a contact record, and someone already on file gets refreshed rather than duplicated. That keeps the supporter list clean when the same donor comes back through several channels.
Create a Single Payment
ActionIn the docs onlyA gift made elsewhere becomes a payment in Access Charity CRM, so finance and fundraising read the same figures. Pick it over Make an API Call whenever recording one payment is all you need.
Create an Event
ActionIn the docs onlyYour gala, webinar or collection day gets its own event record in the CRM, ready for bookings and attendees. Start here whenever the event does not exist in the CRM yet.
Create an Event Attendee
ActionIn the docs onlyAdding a person to the list of attendees of an event happens here, which gives the team an up-to-date picture of who is coming. One bundle in, one attendee added.
Create an Event Attendee Type
ActionIn the docs onlyAttendee types let you tell volunteers, speakers and guests apart on the same event, and this module adds a new type when your categories grow. It is setup work rather than daily traffic.
Create an Event Booking
ActionIn the docs onlyA booking records that someone reserved a place, and this module writes it into Access Charity CRM from whatever tool took the reservation. Reach for it when the reservation, not the attendance, is what you track.
Get Communications
ActionIn the docs onlyPulling the communication history out of the CRM lets another app see what was already said to a supporter before it acts. The records come back as bundles you can map into the next module.
Get Contacts
ActionIn the docs onlyNo more spreadsheet exports: this module hands your supporter records to the rest of the scenario. Pick it whenever the data lives in the CRM but another app is the one that needs it.
Get Event Attendee Types
ActionIn the docs onlyThis read returns the attendee categories already defined in the CRM, so the scenario can pick the right one instead of guessing. Small module, useful guardrail.
Get Event Attendees
ActionIn the docs onlyWho is actually on the list for an event? This module answers by returning the attendees recorded in Access Charity CRM, ready to go to a sheet or a messaging app.
Get Event Bookings
ActionIn the docs onlyBookings stored in the CRM come out here as bundles, so you can reconcile them with the tool that sold the places. Choose it over Get Event Attendees when reservations matter more than turnout.
Get Events
ActionIn the docs onlyListing events gives your scenario the event record it needs before attaching bookings, attendees or changes. Think of it as the lookup step of any event flow.
Get Payment Batches
ActionIn the docs onlyPayment batches recorded in the CRM come out through this module, so finance can follow them in another tool. It reads the batches and leaves them as they are.
Get Payments
ActionIn the docs onlyPayment records flow out of Access Charity CRM here, so a thank-you email, a dashboard or an accounting tool can react to real gifts. Use it when you need the payments themselves, not their batches.
Get a Single Payment Batch
ActionIn the docs onlyWhen one specific batch matters, this module fetches just that one instead of the full list. Less data, fewer bundles and a simpler mapping for the modules after it.
Log an Email
ActionIn the docs onlyEmails sent from another tool can be logged against the supporter in the CRM, so the history stays complete even when the message left from somewhere else. The point is the trace on the record.
Make an API Call
ActionIn the docs onlyAnything the listed modules leave out can still be reached here, because this module calls any endpoint of the Access Charity CRM API with the connection you already set up. It is the fallback, not the first choice.
Update an Event
ActionIn the docs onlyWhen an event changes in your planning tool, this module carries the change over to the existing record in Access Charity CRM instead of creating a second event. One source of truth for the whole team.
Update an Event Attendee
ActionIn the docs onlyAttendee records change after sign-up, and this module applies that change to the person already on the event. The list the team reads on the day stays correct.
Update an Event Attendee Type
ActionIn the docs onlyAdjusting an attendee category happens here, and the change applies to the type the CRM already holds. Handy when your labels evolve and should stay consistent across events.
Update an Event Booking
ActionIn the docs onlyA reservation that moves or changes in another tool gets corrected in Access Charity CRM through this module, instead of leaving an outdated booking on file.
Need help automating Access Charity CRM with Make?
A person reads every message.
