Supabase

#Create the connection

In the dashboard, open Integrations › Your app and click Connect on the Supabase card. The connection has its own URL, which you paste into the provider, and it shows the step-by-step instructions on the same screen.

https://api.postal.so/integrations/crm/01a1c2d3-e4f5-7a6b-8c9d-0e1f2a3b4c5d/webhook

In Supabase, open Integrations › Database Webhooks and create a webhook on the auth.users table with Insert, Update and Delete. Under HTTP Request, choose POST and paste the connection URL. Under HTTP Headers, add:

X-Postal-Secret: whsec_… (the secret shown on the connection)

The secret belongs to the connection and can be rotated on its screen (the old one stops working). Authorization: Bearer <secret> works too.

App integrations count toward your plan limit (app_integrations). If they are not in your plan, the cards appear locked with an Upgrade button.

#Events

The properties are user_id, provider, email_confirmed, created_at and last_sign_in_at. Changes to other tables are ignored.

#Which contact

The user is matched by the Supabase ID, stored in the contact's external_id: if the email changes, the same contact is updated. The name comes from the user metadata, from first_name and last_name (or from full_name / name):

await supabase.auth.signUp({
  email: '[email protected]',
  password,
  options: { data: { first_name: 'Jane', last_name: 'Smith' } },
})

For deletions, the connection says what to do with the contact: only record the event (the default), unsubscribe the contact (it stays in the audience, but receives no marketing) or delete the contact (no event, since the contact is gone). A deletion never creates a contact that Postal did not have.

#Connection settings

• Events: only the checked ones become a contact and an event; the others are ignored (the response is still 202).
• Sync the name: updates the contact's first and last name with what the provider sends.
• Add to segment and Subscribe to topic: a static segment and a topic for every contact that arrives.
• When the user is deleted in the app: only record the event, unsubscribe the contact or delete it.

Everything the connection changes on a contact carries the source crm:<connection id> (last_change_source), and each delivery appears in the connection's log, with the result for each person. A delivery that the provider repeats (same ID) is not processed twice.

#Login emails (Send Email Hook)

With the Send Email Hook, Supabase hands each authentication email to Postal instead of sending it. To turn it on:

1. On the connection, under Login emails through Postal, turn sending on, choose the sender (from a verified domain of your team) and, if you want, the project URL (https://abcd.supabase.co).
2. In Supabase, open Authentication › Hooks, add a Send Email hook of type HTTPS with the hook URL shown on the connection, and generate the secret.
3. Copy the secret (v1,whsec_…) and paste it into the connection. Save.

https://api.postal.so/integrations/supabase/01a1c2d3-e4f5-7a6b-8c9d-0e1f2a3b4c5d/send-email

Each type has a template, written in Portuguese, that you edit on the connection (subject and HTML). Variables:

The emails take the same path as POST /emails: verified domain, daily and monthly quotas and a priority queue. They carry the supabase_auth tag with the type and show up under Emails. Security notification types (password_changed_notification and others) are accepted without being sent.

The response follows what Supabase expects: {} with 200 when the email was queued, and, on errors, the status with the reason, which shows up under Logs › Auth in Supabase:

Whoever receives these login emails is also kept in the Audience, as an unconfirmed contact that gets no marketing until you confirm: see Automatic audience from transactional emails.

{
  "error": {
    "http_code": 403,
    "message": "The example.com domain is not verified. Please, add and verify your domain."
  }
}

#Trigger automations

Each event is stored on the contact under the name supabase.user.created, with the properties from the table above. On the connection screen, the Create automation button next to each event opens a new automation with the Event received trigger already filled in. Through the automations endpoints, the trigger is {"type": "event", "event": "supabase.user.created"}.

Example: a welcome sequence starting at sign-up, and a reminder for anyone who has not confirmed their email after 2 days (with a condition on supabase.user.confirmed). In the emails, the event properties are available as {{event.amount}} in the steps or as template variables ({{{amount}}}).