Create and manage a Neon CRM v2 webhook subscription for donation, membership, and event-registration changes
domain: developer.neoncrm.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Neon CRM v2 API
Create a webhook subscription specifying the target URL, data type (Accounts, Donations, Memberships, Event Registrations, Orders, or Activities), and action (create/update/delete)
Choose a delivery content type (application/json or form-encoded with a JSON payload string)
Implement the receiving endpoint to parse the standard payload (eventTrigger, eventTimestamp, organizationId, data, customParameters)
List, update, or delete the subscription via the Webhooks API as your integration evolves
Known gotchas
Failed deliveries retry only up to 3 times with short (2-second) intervals — don't rely on webhooks alone without a periodic reconciliation job
API v1 and its legacy webhook structure are being sunset by Neon — build new integrations against v2, not v1
customParameters are echoed on every webhook POST and can carry sensitive config — be careful logging raw payloads
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?