Sequin

Sequin sends your Supabase rows and changes anywhere you want. It’s designed to never miss an insert, update, or delete and provide exactly-once process for all changes.

You can receive changes via HTTP push (webhooks) or pull (think SQS). You can easily send changes to your application, another service (i.e. trigger.dev, resend, ingest), or trigger a Supabase edge function.

At some point, almost every Supabase app needs to trigger side effects. Think of sending a new user a welcome email or fanning out Jobs when an order arrives. Sequin aims to give you the tools to make that happen.

Killer features

• Never miss a message: Sequin persists messages until they are acknowledged (i.e. exactly once processing guarantees).
• SQL-based routing: Filter and route messages using SQL where conditions
• Replays: Rewind to any row on your table. Republish messages that match a SQL query.
• Backfills: Queue up records from this moment forward or the entire table.
• Observability and debugging: Sequin has a web console that adds the Supabase queue tooling you’ve been looking for.
• Skip the PL/pgsql: Define business logic in the language of your choice and in your application.
• Transforms: Transform message payloads with Lua functions.

Documentation

This guide steps you through connecting Sequin to your Supabase database to send database changes anywhere.

1. Connect to Sequin with a direct connection

Sequin uses the Write Ahead Log (WAL) to capture changes from your Supabase database. Supabase's connection pooling does not support the WAL, so you need to connect to your Supabase database using a direct connection.

Here is how to set up a direct connection in Supabase:

1. Login to Supabase and navigate to the database settings page (Settings > Configurations > Database).
2. Disable the Use connection pooling option to show your direct connection credentials:
3. In Sequin, enter the direct connection details in the Database connection page, including the Host, Port, Database, User, and Password for your Supabase database. Turn SSL on.

✓ Sequin will automatically detect that you're using a Supabase database and check that your connection is configured correctly.

2. Create a replication slot in Supabase

With your Supabase database connected to Sequin, you'll now create the replication slot that Sequin will use to detect changes in your database.

1. In the Supabase SQL editor, run the following SQL command to create a replication slot:

   
   

   _10

   select pg_create_logical_replication_slot('sequin_slot', 'pgoutput');

   
   

This creates a replication slot named sequin_slot.

2. Next, you'll create a publication to indicate which tables will publish changes to the replication slot.

   In the SQL editor, run the following SQL command to create a publication:

   
   

   _10

   create publication sequin_pub for table table1, table2, table3;

   
   

   If you want to publish changes from all the tables in your database, you can also use the for all tables option:

   
   

   _10

   create publication sequin_pub for all tables;

   
   

3. Back in the Sequin Console, enter the name of the replication slot (e.g. sequin_slot) and publication (e.g. sequin_pub) you just created. Then, name your database and click Create Database.

   

✓ Sequin will now capture rows and changes from your Supabase database.

3. Add a consumer in Sequin

Sequin and Supabase are now working together. Every change in your database will be captured and can be sent to your application, another service, or trigger a Supabase edge function.

You’ll add a consumer in Sequin to define what changes you want to process and where you want to send them.

1. In the Sequin Console, navigate to the Consumers page and click Create Consumer.
2. Select your Supabase database and the table that contains the data you want to process in the consumer. Then, add filters to process just the rows and changes you need.
3. Set your consumer as an HTTP push consumer or HTTP pull consumer, and then configure the endpoints and headers as needed. Then save your consumer.

✓ Make a change in your database, and see it appear in your consumer:

Next steps

You’ve now walked through the basics of connecting to Sequin, creating a consumer, and capturing changes. Now, you can write the business logic for your application to react to the changes.

From here, you might want to:

• Move some Supabase webhooks to Sequin.
• Set up a Sequin consumer to trigger a Supabase edge function.
• Use the Sequin javascript SDK to pull messages from a consumer.
• Dig into Sequin’s core concepts to tune your setup.