Smart webhook classifier
One URL. Every fundraising-platform event categorised.
Donations, event registrations, peer-to-peer pages, refunds, disputes, subscription updates — AI-classified into a single normalised event stream regardless of platform.
One webhook, every platform
Funraisin sends `d_email`. Raisely sends `data.donation.email`. Classy sends `member.email_address`. The smart webhook classifier accepts any of them. AI maps each incoming event onto a normalised event type (donation, registration, refund, dispute, subscription_succeeded/failed/cancelled, webform, shop, profile, team, other) and extracts the donor identity, amount, currency, country, and the dozen-or-so signals fraud detection actually cares about.
PII redacted on the way in
Donor email and name are SHA-256-hashed with a per-organisation pepper before storage; plaintext PII finds in the payload are tagged and redacted to sentinel strings on disk. The classifier sees enough to do its job without Cause Shield holding a plaintext donor identity database your auditor would have feelings about.
Donor-vs-fundraiser disambiguation done right
Funraisin's payloads carry both the donor email (`d_email`) and the fundraiser email (`m_email`) on a P2P donation. Get it wrong and you flag the wrong person. The classifier walks an explicit priority order — donor-tier keys first, then AI judgment, then heuristic fallback — to make sure the supporter linked to the donation is the human who gave the money, not the human who ran the page.
No per-platform configuration
You paste a single webhook URL into your fundraising platform's integration settings. There's no per-platform schema mapping to maintain, no field-by-field configuration screen, no breakage when the platform ships a schema change. The classifier learns the shape of each payload from the data itself.
How customers use it
Three scenarios where this lands
Scenario
Multi-platform charity rationalising monitoring
You run Funraisin for events, Raisely for general donations, and a custom WordPress form for one campaign. Three webhook URLs from three platforms, one Cause Shield endpoint. Fraud monitoring and supporter unification across all three without three integration projects.
Scenario
Catching a platform schema change before donors do
Your fundraising platform ships an update that drops the donor email field on certain donation types. The classifier logs the missing field as a PII finding; your absence-alert rule fires when normal donation volume disappears. You catch it on day one, not at week's end.
Scenario
Standardising reporting across a federation
Twelve chapters use four different fundraising platforms. Smart webhook ingests them all into the same `webhook_events` schema. Atlas and Trails work consistently across the portfolio without per-chapter data wrangling.
Try Smart webhook classifier on a 14-day free trial.
Included on the Partner plan and above. Full access during your trial.