Supabase: insert row

Use Supabase: insert row to write a row into a Supabase table from a journey step, through your project’s REST API, using a service role key. This point authenticates with its own service role key. It doesn’t use any account-level integration configured elsewhere in Settings.

Typical uses:

• Write into your app’s own database: insert a row your app already reads from that Supabase table.
• Log events as they happen: write raw journey data straight into the table instead of waiting on a batch pipeline.
• Sync with existing data: insert a device or tag value your Supabase tables can join against your own data.

Caution

A service role key bypasses row-level security. If your table has RLS policies, don’t use the project’s anon key here — it doesn’t have the rights to insert, and the request fails.

Configure the point

1. Drag Supabase: insert row from the Integrations section of the left panel onto the canvas.
2. Double-click the point and enter a Step Name.
3. In Project host, enter your project’s host from its URL, for example abcdefghij.supabase.co. Don’t include https:// or a trailing slash. Pushwoosh adds https:// and the API path itself.

4. In Service role key, enter the key from Project Settings > API > service_role. It’s stored masked, like a webhook secret header, and Supabase never returns it back to Pushwoosh.

5. In Table, enter the target table’s name.

6. In Columns, add one row per table column to write. Enter the column name and the value. Names must be non-empty and unique. A value can be fixed text or a traveler macro such as {{tag:Name}}, the same macros as in a Webhook body. Or click Insert Dynamic Value to pick an attribute an earlier step in this journey produced, for example an LLM response or a mapped Webhook value.

Example

With Table set to travelers, setting Columns to device_id with the traveler’s device ID ({{device:hwid}}) inserts a row into that table’s device_id column.

7. Click Save.

Response

The traveler continues to whatever step you connect next on the canvas.

Attributes after the step runs

Attribute	What it holds
supabase_row_id	The new row’s id

How to use it in later steps

The traveler already continued to the next step regardless of this attribute. Save it to a Tag with Update user profile if you need to reference or update this specific row later, for example through Supabase’s own API.

Failures and unexpected responses

A failed request drops the traveler from the journey. See Errors and failed requests.

Example scenario: Logging a new trial in Supabase

An app wants every trial start recorded in its own Supabase database, without a separate export job.

1. Add a Trigger-based entry element and set it to fire on a TrialStarted event.
2. Add Supabase: insert row right after it. Set Table to travelers. In Columns, set device_id to {{device:hwid}}.
3. Click Save.

Once this runs, every trial start gets a row in the travelers table, ready for the app’s own queries.