Your app writes to Supabase, but the people who act on new sign-ups, orders or reports work in Slack. FlowMattic watches the tables you choose and posts the rows that matter to a channel or a person, with the fields they need. It suits developers and small product teams who want database events in front of the team without building a notifier.
3 triggers 28 actions 7 example workflows 5 ready-made templates Unlimited runs
When this happens in Supabase3 triggers
Do this in Slack14 actions
1. TriggerRow Inserted2. ActionSend Channel MessageWhen Supabase fires Row Inserted, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateA sign-up, booking or feedback row lands in a channel with its key columns, so the team sees new data without opening the Supabase dashboard or writing a query.
Row InsertedSend Channel Message
View the template Ready-made templateAn AI Agent reads free-text columns such as a feedback message, picks a category and a one-line summary, updates the row and tells the channel what it decided.
Row InsertedAI AgentUpdate RowSend Channel Message
View the template Ready-made templateA Router reads a status or priority column. Urgent rows go to the on-call channel while normal ones go to a quieter log channel, so alerts keep their meaning.
Row InsertedRouterSend Channel Message
View the template When a row's status turns to approved or failed, a Filter checks the value, the owner's email finds their Slack account and they get a direct message about their record.
Row UpdatedFilterFind User by EmailSend Direct Message
A daily Schedule runs Count Rows with a date filter and posts the number to the team channel, a small ritual that keeps everyone close to growth.
ScheduleCount RowsSend Channel Message
Each deletion from a sensitive table posts the old row's ID and key fields to a private channel, so an accidental delete can be traced and put back.
Row DeletedSend Private Channel Message
When a row points to a file in a private bucket, FlowMattic creates a signed URL and sends it to the reviewer, so the file opens without making the bucket public.
Row InsertedCreate Signed File URLSend Direct Message
By the end, each row inserted into your chosen Supabase table appears as a message in a Slack channel.
Add your Supabase project and your Slack workspace under Connects in FlowMattic.
Start a workflow with the Supabase Row Inserted trigger, select the table to watch and insert a test row so FlowMattic captures its columns.
Add Send Channel Message, pick the channel and place the columns you want, such as name, plan and created time, in the text.
Test the Slack step with the captured row, check the message reads well in the channel and switch the workflow on.
1. Trigger in Supabase
Row Inserted
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Supabase | To Slack |
|---|---|
| id | Message: record ID |
| Message: who it is | |
| plan | Message: plan or type |
| created_at | Message: time |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Supabase and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Alerts that would otherwise need a database function, a server and a Slack app are a few steps on the visual builder you can change any day.
FlowMattic runs on your own WordPress server with unlimited runs, so a table that gets thousands of inserts does not raise a bill.
With 14 Supabase actions, the same workflow can update the row, count rows or create file links before it posts to Slack.
Not from a Slack trigger, because Slack has none here. If another tool can send a webhook, use the Webhook trigger with Insert Row or Upsert Row, then confirm with Send Channel Message.
Each Supabase trigger watches the table you select. Create one workflow per table, each with its own message and channel.
Yes. After the trigger, use Get Row by ID or Select Rows with the foreign key from the new row, then use those columns in the Slack message.
Yes, if the row holds their email. Find User by Email returns their Slack user, and you can send them a direct message or mention them in a channel message.
Each inserted row starts its own run, so a bulk import posts one message per row. Point bulk loads at a table you are not watching, or add a Filter to skip imported rows.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 23 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Supabase integration 1.0.0, Slack integration 1.0.
