Checklist · 17 Nov
Checklist before you connect your production database
Approved by the founder
How-to · 2 min read
If your app's users live in Supabase and every newsletter starts with a CSV export into another email tool, the list is out of date before you hit send. Someone signed up this morning and is not in it. Someone else deleted their account last week and still is. You want to email the people in your database as they are today, without a weekly export ritual, and without handing your data to yet another service.
Most email tools keep their own copy of your contacts, so you either export and import by hand or build a sync job that you then have to maintain. Manual exports drift the moment you finish them, and it is easy to upload an old file by mistake. A custom sync means API keys, webhooks and edge cases, which is real engineering time for a small team. And giving an outside service a database login that can write is a risk many founders would rather not take. On top of that, the second tool usually charges by the size of the list it holds, so you pay every month for a copy of data you already have.
This part describes the usual way. It makes no claims about Rowsend, so nothing is quoted here.
Rowsend is a Mac app that reads contacts straight from your own database and sends through your own email provider. For Supabase and other Postgres databases, its setup SQL creates a contacts view and a login that can only read it, so the app never gets write access. You pick which table and columns it reads, then build segments from those columns. Sending goes out through SES, Postmark, Mailgun or SMTP, at your provider's price.
Supabase, Postgres, MySQL, MongoDB or Firebase. Your users become your audience, read through a login that can't write.Quoted from rowsend.com
Rowsend’s setup SQL creates a view and a read-only login, the same way as on Supabase.Quoted from rowsend.com
The select must return id, email and updated_at.Quoted from rowsend.com
Tick the columns you will want to filter on later, such as plan or last sign-in. Segments can only use what the view returns, so it is easier to add them at setup.
Pick a table and its email and last-changed columns, join a second table if you like, and tick any extra columns.Quoted from rowsend.com
Make sure the last-changed column really updates when a user changes. If it never moves, you cannot rely on it to tell you which rows are new. A trigger that sets it on every update is a common fix, and it only takes a few lines of SQL.
General advice. Not a claim about the product.
If your database host limits who can connect, allow your own IP address first, or the test will fail from your Mac.
Your database has to accept connections from your computer. On a cloud host, allow your IP address if it limits who can connect.Quoted from rowsend.com
Add topics before your first big send. People can then leave product updates and keep the newsletter, which keeps more of your list.
Topics let people leave one kind of email and keep the rest.Quoted from rowsend.com
No. It reads through a login limited to a contacts view, and it checks the role cannot write before syncing.
Your users become your audience, read through a login that can't write.Quoted from rowsend.com
No. The setup login is used once to list your tables, and the password is not saved.
Rowsend uses this login once, to list your tables. It doesn’t save the password.Quoted from rowsend.com
Yes. Rowsend sends through your own SES, Postmark, Mailgun or SMTP account and adds no markup.
Use SES, Postmark, Mailgun or SMTP. Rowsend adds no markup to your sends.Quoted from rowsend.com
Checklist · 17 Nov
Approved by the founder
Story · 17 Nov
Approved by the founder
Guide · 17 Nov
Approved by the founder