alfadocs-webhooks

To parse form-urlencoded webhook payloads in a Supabase Edge Function, read the raw request body and use URLSearchParams to convert indexed bracket-form fields into structured event objects for reliable processing.

Supabase Edge Functions receive repeated AlfaDocs webhook retries when the endpoint fails to return an unconditional HTTP 200 response immediately after parsing the raw body, triggering retry mechanisms.

Handling multiple indexed records batched in a single webhook POST requires expanding bracket-key notation from the raw body into separate structured event objects before routing them individually.

Routing AlfaDocs webhook events to the correct tenant in Supabase involves resolving the archiveId from the parsed payload and mapping it to the appropriate connected practice using service-role database access.

AlfaDocs appointment and patient notifications cannot be processed as JSON payloads because they arrive exclusively as form-urlencoded data, requiring URLSearchParams parsing instead of standard JSON deserialization.

The best way to structure Supabase Edge Functions for AlfaDocs webhooks is to parse raw bodies with URLSearchParams, route events by archiveId, apply service-role database access, and return HTTP 200 unconditionally.