Customer events
Connect Supabase database webhooks
Map database changes into source-scoped customer events without transforming webhook bodies.
Configure a database webhook
- 01
Create a Supabase connection
Copy the one-time native webhook URL from AttuneMail.
- 02
Choose a narrow table and operation
Start with a business milestone table rather than mirroring an entire database.
- 03
Paste the URL
Create the Database Webhook and send the original payload without custom wrapping.
- 04
Insert or update a test row
Confirm the canonical name, identity fields, operation, and safe properties before adding a journey.
Canonical mapping
Events are named supabase.{schema}.{table}.{operation}. Idempotency uses x-supabase-event-id, a payload ID, or a stable payload hash. Identity may be resolved from record, new, user, or data fields.
Example canonical name
CopyEvent nameJourney triggerJourney trigger
supabase.public.onboarding_steps.UPDATEMinimize data at the source
- ✓Use a purpose-built milestone table or view where possible
- ✓Avoid sending secrets, tokens, password material, or unrestricted profile JSON
- ✓Use stable ID and email columns for resolution
- ✓Document the table and operation as part of the event contract