Connect JustGiving so that the fundraising pages people set up for you, the donations made on them and the members of fundraising teams arrive in ThirdSectorBee, linked to the right fundraising activity. Once it’s running, a supporter’s JustGiving efforts sit on their record next to everything else they do for you.
Before you start
- JustGiving must be switched to Enabled on the Integrations overview. See enable a service first.
- Connecting, changing settings, saving mappings and running a sync need
justgiving:settings:change. - Have your JustGiving Application ID, API Key and Charity ID ready.
- Create the fundraising activities you want JustGiving events to count towards. Unlike Ticket Tailor, this integration doesn’t create activities for you.
Connect your account
- Open Integrations → JustGiving. The Settings tab opens.
- Enter Application ID, API Key and Charity ID.
- Leave Enable automatic sync (every 3 hours) on if you want ThirdSectorBee to check JustGiving on a schedule.
- Choose Connect JustGiving.
ThirdSectorBee checks the credentials with JustGiving before saving them. Once connected, the header shows Connected and the tab says “JustGiving is connected (charity …). Enter new credentials below to rotate them.” The API key is never shown again.
To change only the automatic sync switch, turn it on or off and choose Update credentials; you don’t need to re-enter your credentials. To replace credentials, enter a new Application ID and API Key (the Charity ID keeps its saved value if you leave it blank) and choose Update credentials.
Map JustGiving events to activities
Pages are grouped under JustGiving events. Pages and donations for an event you haven’t mapped aren’t brought in.
- Open the Activity mappings tab. It lists your charity’s JustGiving events.
- For each event you want to bring in, choose a fundraising activity in Mapped to. The Status column shows Synced for an event with a mapping and Not synced for one without.
- To stop bringing in an event, clear its mapping with the × in the field.
- Choose Save mappings. You’ll see “Mappings saved.”
Sync and check the result
Choose Sync now on the Settings tab to bring everything up to date straight away. The button only works when you’re connected and automatic sync is turned on. When it finishes you’ll see, for example, “Sync complete — 4 page(s), 12 donation(s), 3 team member(s) dispatched; 2 page(s) skipped (event not mapped).”
“Dispatched” means the records have been handed over to be written. Allow a short while before checking the activity and the contacts. With automatic sync on, the same check runs every three hours. Each check only brings in donations newer than the last successful one; a check that fails part-way picks up again from the same point next time.
What it creates
| From JustGiving | In ThirdSectorBee |
|---|---|
| Fundraising page | A fundraising page linked to the mapped activity, with its title, status (Active, Completed or Cancelled), type (Individual or Team), web address, target and currency |
| Page owner | A contact, matched by email address |
| Company named on a page | An organisation |
| Donation | The donor as a contact, matched by email address, and a Paid, inbound payment with the payment method recorded as Online, linked to the activity |
| Member of a team page | A contact, added as a member of the team page |
Refunded, cancelled, failed and declined donations aren’t imported. JustGiving doesn’t add any touchpoint types, payment methods or custom fields to your beehive, and it doesn’t record consent: giving on JustGiving doesn’t tell ThirdSectorBee whether a donor agreed to hear from you. Nothing is sent back to JustGiving.
Anonymous donations
When a donor chooses not to share their details, or a donation has no email address, it’s recorded against a hidden placeholder contact called “JustGiving anonymous donors” rather than a real person. That contact never appears in contact search. The Anonymous donations tab is the place to see these donations, with their Date, Amount and Status. “No anonymous donations yet.” means none have arrived.
Faster updates (webhook)
Once you’re connected, the Settings tab shows a Webhook URL and a Webhook signing secret, each with a Copy button. When JustGiving notifies that address about a fundraising page, ThirdSectorBee syncs that one page straight away. The three-hourly check still runs as well.
Each delivery must be signed with the secret: an HMAC-SHA256 of the raw request body, sent in the x-justgiving-signature header as sha256=<hex>. Unsigned or wrongly signed deliveries are discarded without an error, so pass both values to whoever sets up delivery on the JustGiving side. Keep the secret private.
If something goes wrong
| What you see | What to do |
|---|---|
| “JustGiving credentials are invalid or unreachable” | Check the Application ID and API Key in your JustGiving developer account |
| “appId, apiKey and charityId are required” | Fill in all three fields the first time you connect |
| Sync now is greyed out | Connect first, and make sure Enable automatic sync (every 3 hours) is on and saved |
| “Sync failed. Check that the integration is configured and enabled.” | Check the connection and the sync switch, then try again |
| Pages are skipped “(event not mapped)” | Map their events on Activity mappings and sync again |
| A donation is missing | Check its event is mapped, then look on Anonymous donations in case the donor withheld their details. Refunded and failed donations aren’t imported |
| The webhook seems to do nothing | Check the address and signing set-up against the values on Settings; an unsigned delivery is discarded silently |
| “Failed to save mappings. Please try again.” | Try again, and check you hold justgiving:settings:change |