Skip to main content

Sponsor Org Webhook Guide

Stay in sync with Gloo Impact the moment donations arrive, applications roll in, or a scholarship crosses the finish line.

Ryan Holdeman avatar
Written by Ryan Holdeman
Updated over 2 months ago

Why Configure Webhooks?

Webhooks send Impact events to your systems in real time—no polling or manual exports. Typical wins:

  • Instant donor thanks – trigger an email or CRM note seconds after a gift.

  • Zero‑touch application intake – pipe scholarship applications into your review queue automatically.

  • Fund admin alerts – email or Slack‑notify the Fund or Program administrator as soon as the scholarship is completed.


Events Available to Sponsor Orgs

Event

When it fires

Common automations

Individual Donation Received

A donor’s payment settles into one of your funds.

Thank‑you email, CRM update, Slack alert

Scholarship Application Received

An applicant submits an application tied to a program you sponsor.

Create review ticket, notify committee, kick‑off onboarding drip

Scholarship Complete

All milestones for a scholarship are verified and funds fully disbursed.

Send email or slack message to fund admin as soon as the scholarship is completed.


Before You Start

  • You must be an Org Owner or have Admin permission (help.impact.gloo.us).

  • Prepare a public HTTPS POST endpoint (Zapier, Make, custom API, etc.).

  • Locate your Signing Secret under Settings › Integrations (visible in the Webhooks card) —this secures every delivery.


Step‑by‑Step: Create a Webhook

  1. Go to Settings → Integrations in your Sponsor Org account.

  2. Click + Create webhook.

  3. Select an event from the dropdown.

  4. Give it a clear Nickname (e.g., Zapier – Donations).

  5. Paste your Webhook URL (must begin with https://).

  6. Click Create. Impact starts sending deliveries immediately.

You can repeat these steps to send different events to different tools.


Sample Payloads

Examples are abbreviated—see the Gloo Impact Docs for the full reference.

Individual Donation Received

{

"event": "individual_donation.received",

"delivery_id": "dly_01hxtxw9w4k3s8",

"created_at": "2025-04-28T20:14:31Z",

"data": {

"donation_id": "dn_12345",

"amount": 150.00,

"currency": "USD",

"donor": {

"id": "dr_67890",

"first_name": "Jordan",

"last_name": "Lee",

"email": "jordan@example.com"

},

"fund_id": "fund_abcde"

}

}

Scholarship Application Received

{

"event": "scholarship_application.received",

"delivery_id": "dly_01hxu03q2tm6jf",

"created_at": "2025-04-28T21:05:12Z",

"data": {

"application_id": "app_54321",

"applicant_name": "Maria Garcia",

"email": "mgarcia@example.com",

"program_id": "prog_lmnop",

"fund_id": "fund_abcde"

}

}

Scholarship Complete

{

"event": "scholarship.completed",

"delivery_id": "dly_01hxvb5r6aqj7p",

"created_at": "2025-04-30T09:17:02Z",

"data": {

"scholarship_id": "sch_77777",

"beneficiary_id": "ben_22222",

"program_id": "prog_lmnop",

"total_amount": 2500.00,

"currency": "USD",

"milestones": [

{"id": "ms_1", "name": "Enrolled", "verified": true},

{"id": "ms_2", "name": "Course Complete", "verified": true}

]

}

}


Security & Reliability

  • Signature verification – Compute HMAC‑SHA256(raw_body, signing_secret) and compare to the X‑Impact‑Signature header.

  • Retries – Impact retries up to 5 times with exponential back‑off if your endpoint returns a non‑2xx status.

  • Idempotency – Use the delivery_id to dedupe in case of retries.​

These patterns mirror best practices discussed in the Help Center’s troubleshooting guidance (help.impact.gloo.us).


Best‑Practice Automations

Tool

Trigger

Action

Zapier

Donation Received

Gmail – personalised thank‑you

Make

Scholarship Complete

Google Drive – generate PDF certificate

Slack Incoming Webhook

Any event

Post to #impact-alerts

Salesforce Flow

Donation Received

Upsert Contact & Opportunity


Troubleshooting

Issue

Likely cause

Fix

Delivery shows “Failed”

Endpoint returned non‑2xx

Check server logs; reply 200 ASAP

Duplicate events

Retries after timeout

Acknowledge fast; use delivery_id for idempotency

Signature mismatch

Wrong secret or modified body

Use raw request body & correct secret

You can always view recent attempts in Settings › Integrations › Webhook Logs (help.impact.gloo.us).


FAQ

Q: Can I send the same event to multiple URLs?

Yes—create additional webhooks with the same event but different URLs.

Q: How do I disable a webhook?

Open the Webhook detail pane and toggle Disable. You can re‑enable later without losing history.

Q: Is there a test mode?

Yes—use webhook.site or similar to preview payloads before wiring production endpoints (help.impact.gloo.us).

Did this answer your question?