Verify and handle TutorCruncher webhook deliveries for lesson/tutor/client events
domain: app.tutorcruncher.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In TutorCruncher go to System > Settings > Integrations, add an integration, and set the webhook URL to receive events
Inspect an incoming payload's 'events' array; each event has action, verb, timestamp, branch, actor and subject fields describing what changed
Verify authenticity by computing an HMAC-SHA256 of the raw request body using the integration's private key and comparing it to the 'Webhook-Signature' request header
Use the action_types list (GET /api/action-types/) to map action codes like CREATED_A_CONTRACTOR or DELETED_AN_APPOINTMENT to their human-readable meaning
Return a 2xx response quickly; check the integration's webhook logs in TutorCruncher if deliveries appear missing
Known gotchas
Failed deliveries (timeout, no response, or 5xx) are retried up to 4 times with exponential backoff (1s, 10s, 100s, 1000s); 4xx errors (except 429) are NOT retried, and endpoints with a sustained >20% failure rate get auto-disabled
The 'extra_msg' field is only populated for some actions (e.g. API-created records show 'Created via the API.'); UI-created records often leave it blank, so don't rely on it always being present
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?