The open-source Firebase alternative
Supabase currently provides 1 trigger that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
New Row
Fires when a new row is created in a table
Upload File
Upload a file to Supabase Storage
Create Row
Create a new row in a table
Update Row
Update rows in a table based on filter criteria
Upsert Row
Insert or update a row in a table
Delete Rows
Remove rows matching filter criteria from a table
Search Rows
Search for rows in a table with filters and pagination
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Supabase event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Row
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Supabase action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Upload File
Combine Supabase with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New Row
Finishes with
Upload File, then preserve the outcome in Coherence
The exact authentication fields depend on Supabase. The workflow structure stays straightforward:
Authorize the Supabase account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Supabase or provide a complementary trigger or action.
Supabase currently provides 1 trigger that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Supabase currently lists 1 trigger and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Supabase triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
