Supabase Integration

Connect your Supabase database to automatically sync users to Sequenzy. When users are added to your database, they become subscribers instantly.

What is Supabase?

Supabase is an open-source Firebase alternative that provides a PostgreSQL database, authentication, real-time subscriptions, and more. Many SaaS applications use Supabase as their backend.

Connecting Supabase

Step 1: Generate a Webhook Secret

Go to Settings → Integrations in Sequenzy
Click Connect next to Supabase
Click Generate Secret to create a secure webhook secret
Copy the generated secret — you’ll need it in the next step

Step 2: Create Database Webhook in Supabase

Go to your Supabase Dashboard
Navigate to Database → Webhooks
Click Create a new hook
Configure the webhook:
- Name: sequenzy-user-sync (or any name you prefer)
- Table: Select your users table (e.g., users or profiles)
- Events: Select INSERT, UPDATE, and DELETE
- Type: HTTP Request
- Method: POST
- URL: Paste your Sequenzy webhook URL (shown in the modal)
Add an HTTP header for authentication:
- Header name: x-webhook-secret
- Header value: Paste the secret you generated in Step 1
Click Create webhook

The x-webhook-secret header is required to verify that webhooks are coming from your Supabase project. Make sure the value matches exactly what you entered in Sequenzy.

Step 3: Save the Connection

Return to Sequenzy’s Supabase connection modal
Click Save Connection

That’s it! Your Supabase users will now sync automatically to Sequenzy.

Route Supabase Auth and Security Emails Through Sequenzy SMTP

The database webhook above handles subscriber sync. Supabase Auth emails are a separate path. If you want Supabase invites, magic links, password resets, and security notifications to send through Sequenzy too, configure Supabase to use Sequenzy SMTP and point each Supabase email template at a Sequenzy transactional email.

Step 4: Configure Supabase SMTP

Create a Sequenzy API key in Settings → API Keys
In Supabase, go to Authentication → Emails → SMTP Settings
Enable custom SMTP and use:

Setting	Value
Host	`smtp.sequenzy.com`
Port	`587`
Username	`api`
Password	Your Sequenzy API key

Use a sender address that belongs to a verified Sequenzy sending domain. Supabase still needs a sender configured, even when Sequenzy renders the final template.

Step 5: Point Supabase Email Templates at Sequenzy Transactionals

If your workspace does not have a verified sender profile yet, Sequenzy automatically provisions a shared-domain sender and assigns it to the default Supabase templates. In Sequenzy, open the Supabase integration modal and click Create default Supabase auth templates. This provisions the standard transactional emails for:

supabase-confirm-signup
supabase-invite
supabase-magic-link
supabase-password-reset
supabase-email-change
supabase-password-changed
supabase-phone-changed
supabase-identity-linked
supabase-identity-unlinked
supabase-mfa-enrolled
supabase-mfa-removed

Then replace the Supabase message body with a JSON payload that references the matching Sequenzy slug. You can reference the Sequenzy email by slug or transactionalId. variables and dataVariables are both supported. Example for a Magic Link template:

{
  "slug": "supabase-magic-link",
  "dataVariables": {
    "confirmation_url": "{{ .ConfirmationURL }}",
    "token": "{{ .Token }}",
    "token_hash": "{{ .TokenHash }}",
    "redirect_to": "{{ .RedirectTo }}",
    "site_url": "{{ .SiteURL }}",
    "email": "{{ .Email }}"
  }
}

Example for an Email Changed notification:

{
  "slug": "supabase-email-change",
  "dataVariables": {
    "email": "{{ .Email }}",
    "old_email": "{{ .OldEmail }}",
    "new_email": "{{ .NewEmail }}"
  }
}

Suggested Variable Mapping

Supabase template variable	Suggested Sequenzy merge tag
`{{ .ConfirmationURL }}`	`{{confirmation_url}}`
`{{ .Token }}`	`{{token}}`
`{{ .TokenHash }}`	`{{token_hash}}`
`{{ .RedirectTo }}`	`{{redirect_to}}`
`{{ .SiteURL }}`	`{{site_url}}`
`{{ .Email }}`	`{{email}}`
`{{ .NewEmail }}`	`{{new_email}}`
`{{ .OldEmail }}`	`{{old_email}}`
`{{ .Phone }}`	`{{phone}}`
`{{ .OldPhone }}`	`{{old_phone}}`
`{{ .Provider }}`	`{{provider}}`
`{{ .FactorType }}`	`{{factor_type}}`

Recommended Setup

Keep the database webhook integration enabled for subscriber sync
Use Sequenzy SMTP for Supabase Auth email delivery
Create one Sequenzy transactional email per Supabase template type
Use clear slugs like supabase-invite, supabase-magic-link, and supabase-password-reset

What Gets Synced

Sequenzy automatically maps common database columns to subscriber attributes:

Email Detection

Sequenzy looks for email in these columns (in order):

email
email_address
user_email
contact_email

User ID Detection

User ID is extracted from:

id
user_id
uid
uuid

Synced Attributes

Database Column	Subscriber Attribute
`first_name`	`firstName`
`last_name`	`lastName`
`full_name`	`fullName`
`avatar_url`	`avatarUrl`
`phone`	`phone`
Any other column	Stored as custom attribute

Sensitive columns like password, password_hash, and encrypted_password are automatically excluded.

Tracked Events

Database Event	Sequenzy Event
`INSERT`	`contact.subscribed`
`UPDATE`	Attributes updated (no event)
`DELETE`	`contact.unsubscribed`

Using with Automations

Welcome Sequence for New Users

Go to Automations → Create New
Set trigger to Event Received → contact.subscribed
Add your welcome email sequence
Activate the automation

Every new row in your users table will trigger the welcome sequence.

Custom Attributes

Any column in your users table becomes available for segmentation and personalization:

-- Your users table might have:
CREATE TABLE users (
  id UUID PRIMARY KEY,
  email TEXT,
  first_name TEXT,
  plan TEXT,          -- becomes {{ plan }}
  company_name TEXT,  -- becomes {{ company_name }}
  created_at TIMESTAMP
);

Use these in emails:

Hi {{firstName}},

Thanks for signing up for the {{plan}} plan!

Database Schema Recommendations

For best results, include these columns in your users table:

-- Recommended columns
email TEXT NOT NULL,        -- Required for subscriber creation
first_name TEXT,            -- Maps to firstName
last_name TEXT,             -- Maps to lastName
-- Optional but useful
avatar_url TEXT,            -- Profile picture
phone TEXT,                 -- Phone number
plan TEXT,                  -- Subscription plan
created_at TIMESTAMP        -- For tracking

User Lifecycle

Supabase Event	Sequenzy Action
Row inserted	Subscriber created, `contact.subscribed` triggered
Row updated	Subscriber attributes updated
Row deleted	Subscriber unsubscribed

When you delete a user from your database, they’re automatically unsubscribed in Sequenzy.

Troubleshooting

Users Not Syncing

Verify the webhook URL is correct in Supabase
Check that the x-webhook-secret header matches the secret in Sequenzy
Ensure all events (INSERT, UPDATE, DELETE) are selected
Check Supabase’s webhook logs for failed deliveries

Missing Email

If users are inserted without an email column value, Sequenzy cannot create a subscriber. Ensure your users table has a valid email.

Wrong Columns Mapping

Sequenzy looks for standard column names. If your schema uses different names:

email_address → works (detected automatically)
customer_email → works (detected automatically)
e_mail → won’t be detected as email

Consider using standard column names or storing data in the expected format.

Signature Verification Failed

Verify the x-webhook-secret header value in Supabase matches exactly what you entered in Sequenzy
Secrets are case-sensitive
Try generating a new secret and updating both Supabase and Sequenzy

FAQ

Which table should I use?

Use whichever table contains your user data. This is typically users, profiles, or auth.users. If you’re using Supabase Auth, you might want to create a trigger to sync to a profiles table with the columns you need.

Does this sync existing users?

No, only new inserts after connecting will create subscribers. For existing users, you can export them as CSV and import into Sequenzy.

Can I sync from multiple tables?

You can create multiple webhooks for different tables. Each will sync to the same subscriber list, matched by email.

Is this included in my plan?

Yes, Supabase integration is included at no extra cost.

Get Started

Send Email

Core Concepts

Email Features

Analytics

Deliverability

Guides

Widgets

Payment Integrations

Commerce Integrations

Auth Integrations

Analytics Integrations

Automation Integrations

Developer Tools

Documentation Index

​What is Supabase?

​Connecting Supabase

​Step 1: Generate a Webhook Secret

​Step 2: Create Database Webhook in Supabase

​Step 3: Save the Connection

​Route Supabase Auth and Security Emails Through Sequenzy SMTP

​Step 4: Configure Supabase SMTP

​Step 5: Point Supabase Email Templates at Sequenzy Transactionals

​Suggested Variable Mapping

​Recommended Setup

​What Gets Synced

​Email Detection

​User ID Detection

​Synced Attributes

​Tracked Events

​Using with Automations

​Welcome Sequence for New Users

​Custom Attributes

​Database Schema Recommendations

​User Lifecycle

​Troubleshooting

​Users Not Syncing

​Missing Email

​Wrong Columns Mapping

​Signature Verification Failed

​FAQ

What is Supabase?

Connecting Supabase

Step 1: Generate a Webhook Secret

Step 2: Create Database Webhook in Supabase

Step 3: Save the Connection

Route Supabase Auth and Security Emails Through Sequenzy SMTP

Step 4: Configure Supabase SMTP

Step 5: Point Supabase Email Templates at Sequenzy Transactionals

Suggested Variable Mapping

Recommended Setup

What Gets Synced

Email Detection

User ID Detection

Synced Attributes

Tracked Events

Using with Automations

Welcome Sequence for New Users

Custom Attributes

Database Schema Recommendations

User Lifecycle

Troubleshooting

Users Not Syncing

Missing Email

Wrong Columns Mapping

Signature Verification Failed

FAQ