Updated for Charitable Pro 1.8.20
Describe the fundraiser. Charitable builds it.
- Connect the ChatGPT or Claude you already use, with the free WPVibe plugin
- Ask for a campaign, a receipt for a check that came in the mail, or a report on your biggest supporters
- It runs on your own site, against your own donor records
- Nothing changes until you turn write access on, and anything you cannot undo previews first
- No add-on to buy, and free AI plans work
- WordPress 6.9+ and Charitable Pro 1.8.18+
New To AI? Start Here.
If you have used ChatGPT, you already know most of this. Here is what is new, and how to start.
Nothing to buy, nothing to install, and no setup inside Charitable.
No code, and nothing to set up.
You type what you want, the way you would ask a coworker to do it.
What Is An AI Assistant?
A chat window. You describe what you want in plain language and it answers. ChatGPT and Claude both work this way.
What Changed?
Before, an assistant could only give advice about your site. Now it does the work inside Charitable while you watch.
Why Does It Matter Here?
Small teams rarely have a developer on call. Whoever knows what the fundraiser should say can now just describe it.
Five steps, about ten minutes. You only do this once.
Check Your Versions
WordPress 6.9 or later, Charitable Pro 1.8.18 or later. On WordPress 6.8 nothing registers and nothing about your site changes. The donor and donation work marked 1.8.20 below needs that release.
Add A Connector
Your assistant reaches your site through a small bridge. WPVibe is a free one that works with Charitable out of the box.
Create An Application Password
In WordPress go to Users > Profile and scroll to Application Passwords. Name it after your assistant and copy it straight away, because WordPress shows it once. This section only appears on sites served over HTTPS.
Connect Your Site
Give your assistant your site address, your username and that password. If your connector offers a one-click approval link instead, take it, and you never type the password at all.
Turn Write Access On
Go to Charitable > Tools > AI MCP and turn on Enable AI write access. Leave it off and you still get a genuinely useful read-only assistant for reporting.
“Set up a fundraiser for the animal shelter, $5,000 goal.”
That is the whole job. There is no form to fill in, and you never name an operation.
Full Instructions
The five steps above are the whole setup. These guides go deeper, and cover every operation in full.
Getting started with AI assistants
Connect an assistant in five steps, with write access off until you turn it on.
AI assistants in Charitable: the full reference
Every operation, how permissions map to roles, and what is deliberately out of reach.
All Charitable documentation
Every guide for the plugin and its add-ons, in one place.
Prompts To Try
Copy any of these and change the details to match your own fundraising. Ask in your own words if you prefer, because you never need to name an operation or fill in a form.
Build a campaign
Set up a fundraiser for the animal shelter, $5,000 goal, ending at the end of next month
You get a real campaign in the Campaign Builder, from a template the assistant picks from your words, with suggested amounts scaled to your goal. It arrives as a draft.
Create a campaign for our winter coat drive with a $2,500 goal
Copy last year’s gala campaign and call it Gala 2027
The copy keeps the story, goal, dates, design and form settings, arrives as a draft, and starts at nothing raised. Donations are never copied.
Use this photo on the winter coat drive and file it under Appeals
New in this release: the image is fetched into your Media Library, and categories and tags you already use are matched by name.
What campaign templates can I choose from?
The winter coat drive looks right, publish it
Nothing goes live by accident: a campaign an assistant makes is a draft until you ask for it to be published.
Customize the donation form
Add a question asking how they heard about us
Make that a dropdown instead: Facebook, a friend, or our newsletter. Default it to our newsletter.
Choice fields can carry their own options and a pre-selected default, in one request.
Make that campaign’s donate button green
Only the button changes. Nothing else moves.
Move the phone number field above the payment section
Make the suggested amounts 25, 50 and 100, and still let people type their own
What can you actually change on this campaign’s form?
It reads back the field types, colours, type sizes and animations this site accepts, so it is working from your vocabulary rather than guessing.
Record a gift that came in offline
Someone posted a check for $250 from Jane Smith, record it
It will ask for the donor's email address, and it should, because donors are matched on email and inventing one would split or merge real records.
Record a $1,000 cash donation to the winter coat drive
Log a $500 bank transfer from our board chair against the capital appeal
Put a donation right after the fact
The bank transfer for donation 1042 has landed, mark it as paid
Moving a donation into or out of a paid status asks you to confirm, and the preview tells you to check the gateway first. Marking it paid does not collect anything.
The check for donation 1099 bounced, set it to failed
A move between two unpaid statuses happens straight away, because nothing about it is hard to undo.
Resend the receipt for donation 1042
Paid donations only, and once a minute at most, because it sends a real email to a real person. Ask for the donor's current address if you have just corrected it.
Add a note to donation 1042: the donor rang to say the gift is in memory of their mother
The note joins the donation's history in your dashboard, marked as added by an assistant so you can tell it from one a colleague left. Notes cannot be edited afterwards.
Look after donor records
Jordan wrote in with a new postal address, update their donor record
Only the fields you name change. Past donations keep the details the donor gave at the time, so old receipts still match what was sent.
There is a typo in that donor’s email address, fix it but leave their WordPress login as it is
Changing the email of a donor who also has a WordPress account moves their login, and where password resets go, so that one asks you to confirm. You can tell it to leave the login alone.
A donor has asked us to delete their data. Show me exactly what would be erased
The answer to a data-subject request. It always previews first: which profiles, saved details and donation fields would go, and which donations your retention setting keeps. Amounts, dates and campaign totals stay, so your reporting does not move. It refuses an administrator's account.
What has this donor given us over the years?
A read, so it answers with write access switched off.
Ask about your fundraising
Who are our biggest supporters?
Ranked over your whole history. Never includes an email or postal address.
Which campaign has raised the most?
What did we raise last month compared to the month before?
How many donors gave more than once this year?
Show me a day by day breakdown for the winter coat drive
How much came from repeat donors rather than first-time donors this year?
Export last quarter’s donations to a CSV
You get a download link rather than thirty thousand rows pasted into the chat.
Diagnose a problem
Why aren’t my donations showing up?
It reads your gateway and test-mode status, so you get a real diagnosis instead of a guess.
Is my site still in test mode?
Which payment gateways are set up?
What can my Charitable site do?
Is AI write access switched on for this site?
Worth asking first if a request to change something was refused.
Safe By Design
Nothing is exposed to anyone who could not already do it in your dashboard. Every operation checks a Charitable capability before it runs.
An assistant signs in as a person
It connects as one of your WordPress users, with an application password that user created, and it inherits exactly that person’s permissions. There is no AI account and no separate key, so an assistant never reaches further than the person it is acting for. Every request is checked against those permissions, not just the first one.
Changes are off until you turn them on
A connected assistant reads immediately and cannot change anything until an administrator enables write access under Charitable > Tools > AI MCP. Ask it to build something with the gate off and it refuses, then tells you the exact switch to flip.
Payment credentials are never readable
Your Stripe, PayPal and Square keys are not in anything an assistant can see, whoever is asking.
Donor contact details need a second permission
Seeing that a gift arrived, for how much and to which campaign, is one level of access. A donor’s email or postal address is a separate and higher one: a list never carries it, and an address comes back only one donation at a time. From Charitable Pro 1.8.20 you also tick which roles may let an assistant read donor data at all, and that list can only narrow access, never widen it.
There is no permanent delete for a campaign
An assistant can move one to the trash, which is reversible, and nothing more. It also refuses to trash a campaign that already has donations unless you confirm.
New campaigns are drafts
Unless you ask for otherwise, so nothing goes live by accident.
The changes you cannot undo ask first
Erasing a donor’s personal data, marking a donation paid, and changing the email of a donor who has a WordPress account each run in two steps. The first one changes nothing: it returns a preview of exactly what would happen, which your assistant reads back to you. Nothing moves until you say yes, and the agreement expires after ten minutes.
Refunds and cancellations are not on the list
An assistant can move a donation between statuses, but refunding or cancelling one is deliberately left to your dashboard and your payment gateway. Marking a gateway donation paid does not move money either way.
Every change is logged
Charitable > Tools > Logs, filtered to Abilities, records what an assistant did. Charitable > Tools > System Info has an Abilities API section, the first place to look if a client connects but cannot see your data.
What You Can Do With AI
In Charitable Right Now
Two thirds of them read, the rest write, and every one is registered with the core WordPress Abilities API.
Charitable registers 39 operations, 24 of them read-only. Writes stay off until an administrator turns them on, and the handful that cannot be undone ask you to confirm even once they are on.
| Group | What it covers | Reads | Writes | Total |
|---|---|---|---|---|
| Diagnostics | Plugin and licence info, site environment, and gateway status. Never keys or secrets. | 3 | 0 | 3 |
| Campaigns | List, read, create, update, duplicate, status, trash and restore, plus the campaign image, categories and tags, donation form fields and Design styles. | 7 | 9 | 16 |
| Donations | List, read and summarise totals, record a gift that came in offline, change a status, resend a receipt, and add a note to the donation’s history. | 3 | 4 | 7 |
| Donors | List donors and totals, read one donor in full where permitted, correct their details, and erase their personal data on request. | 3 | 2 | 5 |
| Reports | Overview, day-by-day activity, top campaigns, top donors, named date ranges, and repeat donors against first-time donors. | 6 | 0 | 6 |
| Export | Donations and donors to a CSV, handed back as a download link rather than pasted into the chat. | 2 | 0 | 2 |
| All groups | Everything registered today. | 24 | 15 | 39 |
Six of those arrived in Charitable Pro 1.8.20: correcting a donor’s details, erasing a donor’s personal data, changing a donation’s status, resending a receipt, adding a note to a donation, and duplicating a campaign. The same release let an assistant set a campaign’s image, categories and tags.
Each operation carries a description written for the assistant, telling it when that operation is the right choice and what its values mean. The complete list, how permissions map to roles, and what is deliberately out of reach are all in the full reference.
Watch And Learn
Short walkthroughs of Charitable and AI. Click any thumbnail to play it here.
Visit Our YouTube ChannelFrequently Asked Questions
The things people ask before connecting an assistant to a live fundraising site.
Do I need to install a Charitable add-on for this?
No. There is no add-on to buy, nothing to install, and no setup inside Charitable at all. If you are running Charitable Pro 1.8.18 or later on WordPress 6.9 or later, the operations are already registered and waiting for a client to connect.
Which AI assistants work with Charitable?
Any assistant that reads the WordPress Abilities API. Claude, ChatGPT and Cursor are the ones we have used. Charitable did not build an integration with one company’s AI, so when a new client appears it works with Charitable on day one with nothing for you or us to do.
Can an assistant see my donors’ email addresses?
Donor lists never include email or postal addresses, whoever is asking. Reading one named donor’s contact details requires the sensitive-data capability, so a single permitted read cannot become a bulk export of your donor file.
Could an assistant reach my payment keys or move money?
No. Your Stripe, PayPal and Square credentials are not included in anything an assistant can see. It can tell you which gateways are enabled and whether each is configured, and nothing more.
Can an assistant delete one of my campaigns?
There is no permanent delete. An assistant can move a campaign to the trash, which is reversible, and that is all. It will also refuse to trash a campaign that already has donations unless you confirm.
Can an assistant change or delete a donor’s details?
From Charitable Pro 1.8.20 it can correct a donor’s name, email, phone or address, and it can erase a donor’s personal data when that donor asks you to. Both need write access and the sensitive-data capability, erasing needs WordPress’s own erase permission on top, and both preview before they act where the change is hard to undo. An erase keeps amounts, dates and campaign totals, so your reporting does not change, and it refuses a donor attached to an administrator account.
Can an assistant mark a donation as paid, or refund one?
It can move a donation between statuses from 1.8.20, and moving one into or out of a paid status asks you to confirm first. Refunding and cancelling are deliberately not available to an assistant at all: those stay in your dashboard and your payment gateway. Marking a gateway donation as paid records it in Charitable and does not collect any money, so check the gateway before you agree.
How do I stop an assistant making changes?
Changes are off until you switch them on. A newly connected assistant can read everything and change nothing until an administrator enables write access under Charitable > Tools > AI MCP. You can turn it back off whenever you like, and reads keep working either way.
How do I see what an assistant actually did?
Go to Charitable > Tools > Logs and filter to Abilities. Every change an assistant makes is recorded there. Charitable > Tools > System Info also has an Abilities API section, which is the first place to look if a client connects but cannot see your data.
What happens if I am still on WordPress 6.8?
Nothing registers and nothing about your site changes. The Abilities API arrived in WordPress 6.9, so 6.9 is the floor for any of this to work.
For Developers
An AI assistant is only one consumer of the Abilities API.
Everything here is reachable from your own code.
Charitable registers its operations with the WordPress Abilities API, which landed in core in WordPress 6.9. Any plugin can describe what it can do, and any connected client reads the same description.
An AI assistant is only one consumer
Every operation is equally reachable from your own PHP, from WP-CLI, or from any HTTP client. If you have been writing custom queries against Charitable’s tables to build a report, an ability is a supported alternative that fires the plugin’s own validation and capability checks.
The write gate is a filter
It defaults to the ai_mcp_write_enabled setting, which is off on a site that has never set it, and you can override it in code. This is the clean way to guarantee an assistant can never write on production while leaving it on in staging.
add_filter(
'charitable_abilities_allow_write',
function ( $enabled ) {
if ( function_exists( 'wp_get_environment_type' ) && 'production' === wp_get_environment_type() ) {
return false;
}
return $enabled;
}
);
The gate keys off each operation’s own readonly annotation rather than a list of operation names, so a write operation added in a later release is covered by that filter automatically. Permission checks are separate and always run: every operation tests a Charitable capability before it does anything, so the gate sits on top of your role setup rather than replacing it.
This Is Just The Start
Charitable Pro 1.8.20 covers campaigns, donations, donors, reports and exports. Support for the add-ons is next, and this page is where each one gets documented as it lands.
Machine-readable: this page as Markdown · site index





