Connect GivJoy to your tools, without writing code.
Website embeds, Zapier, connected AI assistants and a full data download are in development. A public API is coming later.
What's planned
| Connection | What it does | Plans |
|---|---|---|
| Zapier | Starts an automation in Zapier (Zapier calls it a Zap) when something happens in GivJoy: a gift arrives, a new donor or monthly donor, a monthly gift is paused or stopped, a gift is refunded, a supporter's contact preferences change, an event registration is made, changed or cancelled, or a guest checks in. Typical Zaps add new donors to a Google Sheet, post gifts in Slack or add guests to a Mailchimp list. | Starter and Pro |
| Your AI assistant, such as Claude or ChatGPT | MCP (Model Context Protocol) is the standard way an AI assistant uses another service. Connect an assistant such as Claude to ask about your giving, draft a campaign, open its Publish review for a person to confirm in GivJoy, or get your donation form's code for your website. | Every plan |
| Website embeds | Put a donation button and popup, a donation form, a ticket picker or a goal progress bar on your own website by copying a short snippet GivJoy gives you. | Every plan |
| Download all your data | Everything your nonprofit has in GivJoy, with a guide to every column and ready-made files for Excel and Power BI (Microsoft's reporting tool), plus report exports and a file for your accountant. | Every plan |
How each one keeps you in control
Zapier only receives. It can't create, change or delete anything in GivJoy. The connection belongs to your organization, an administrator approves it, and it keeps working when that person leaves. Test gifts start Zaps too, marked as tests, so a Zap can skip them. At first, the GivJoy Zapier app is private. It isn't listed in Zapier's app directory, so an administrator adds it from a link in GivJoy's settings.
An AI assistant acts as you, never more.
- Connection scope. Each connection belongs to one staff member and one nonprofit. For now, each person's assistant stays with the first nonprofit they approve it for.
- Permissions. It can do only what that person's role allows. No AI assistant can:
- email supporters
- change contact records
- change your plan or billing
- publish anything (a person publishes on GivJoy’s own Publish review)
- Compatibility. We test Claude and ChatGPT. Other assistants may work, but we don't promise them yet.
- Usage. Asking questions uses your assistant's own AI, so it doesn't count against your GivJoy plan.
Your data leaves only through doors you open. GivJoy never gives anyone direct access to its database. Notes never leave GivJoy through Zapier.
Coming later
None of these has a date yet.
- A public developer API
- General webhooks, Make and n8n
- Zapier actions or searches (creating or finding anything in GivJoy from Zapier), and a public listing in Zapier's app directory
- Salesforce and QuickBooks connections
- Scheduled delivery to Google Sheets or a data warehouse, and a reporting API
The GivJoy launch list
The launch list isn't open yet. Please check back soon.
You can email support@givjoy.io with questions.
What the labels mean
- Exploring
- We are looking into the problem. It may never be built.
- In development
- We are working on it. Not usable yet.
- Early access
- A few invited nonprofits can use it, in test mode where that applies.
- Live
- Available to the stated audience.
- Not pursuing
- Dropped or paused, with a short reason and a date.