💾 Database

You must first initialize the API Connector in order to select the correct type.
Please refer to this section for detailed instructions.

The Postgres schema which this table belong to.

Supabase table name (e.g todos).

By default, the plugin attempts to automatically retrieve the expected result based on the type defined in the API connector. To prevent any retrieval failures and ensure that the plugin can properly publish results from Supabase, we recommend you paste your schema into this field. This schema should match the one you have already entered in the API connector.

Receive real-time updates on Insert, Update or Delete. By default, realtime is disabled on the Supabase database.

By default, when you enable real-time updates (with "Listen to changes"), the plugin subscribes to changes on the selected table. If you are using a query join, for example, fetching author names (from the author table) associated with books (from the books table), you can specify here the joined tables to receive real-time updates on them (authors in this example).

If enabled, debug messages for real-time events will be logged to the browser console, providing detailed insights into its behavior. This will result in verbose console output and is recommended to be disabled in a production environment.

Automatically fetch data when the page loads. You can still fetch data anytime using the Fetch action in your workflow.

Allows you to specifiy specific columns. If you leave columns empty or set it to *, it will fetch all columns in the table.

Please check this section for more details.

If true, null values are treated as the lowest possible values when sorting in ascending order and as the highest possible values when sorting in descending order. This applies to all columns where ordering is enabled. The default is true.

The column to order by. Leave empty to not order results.

When set to true, the query will use an ascending order for this column.

The maximum number of rows to return. Setting this to 0 does not apply any limit.

When set to true, the query will limit results to a specific range defined by 'Limit From' and 'Limit To'.

The starting index from which to limit the result. This index is 0-based, meaning an index of 0 refers to the first record.

The last index to which to limit the result. This is inclusive, so the record at this index will be included in the result.

Count algorithm to use to count rows in the table or view.

• exact: Exact but slow count algorithm. Performs a COUNT(*) under the hood.
• planned: Approximated but fast count algorithm. Uses the Postgres statistics under the hood.
• estimated: Uses exact count for low numbers and planned count for high numbers.

When set to true, data will not be returned. Useful if you only need the count.

By default, the plugin attempts to automatically retrieve the expected result based on the type defined in the API connector. To prevent any retrieval failures and ensure that the plugin can properly publish results from Supabase, we recommend you paste your schema into this field. This schema should match the one you have already entered in the API connector.

Allows you to specifiy specific columns. If you leave columns empty or set it to *, it will fetch all columns in the table.

Use the selected filters for incoming real-time updates. This only applies if you select the option 'Listen to changes in real-time' on the database component.

Please check this section for more details.

If true, null values are treated as the lowest possible values when sorting in ascending order and as the highest possible values when sorting in descending order. This applies to all columns where ordering is enabled. The default is true.

Enable or disable this sorting. Only used when order by is set.

The column to order by. Leave empty to not order results.

Optional. The foreign table to use if "Order by" is a foreign column.

When set to true, the query will use an ascending order.

Select this to use the selected ordering options for incoming real-time updates. This only applies if you select the option 'Listen to changes in real-time' on the database component.

The maximum number of rows to return. Setting this to 0 does not apply any limit.

When set to true, the query will limit results to a specific range defined by 'Limit From' and 'Limit To'.

The starting index from which to limit the result. This index is 0-based, meaning an index of 0 refers to the first record.

The last index to which to limit the result. This is inclusive, so the record at this index will be included in the result.

Select this to use the selected limits options for incoming real-time updates. This only applies if you select the option 'Listen to changes in real-time' on the database component.

Count algorithm to use to count rows in the table or view.

• exact: Exact but slow count algorithm. Performs a COUNT(*) under the hood.
• planned: Approximated but fast count algorithm. Uses the Postgres statistics under the hood.
• estimated: Uses exact count for low numbers and planned count for high numbers.

When set to true, data will not be returned. Useful if you only need the count.

Select this to use the selected options for incoming real-time updates. This only applies if you select the option 'Listen to changes in real-time' on the database component.

Inserting a single row (using Payload and/or JSON payload) or multiple rows (using List payload or List JSON payloads).

The values to insert into your Supabase DB when using single insert.

The values to insert into your Supabase DB in JSON format when using single insert.

The values to insert into your Supabase database when the insert type is set to "bulk".
This must be a list of items that match your table schema.
You can use the Bulk data state as the value from the database component after adding data to it using the Add item to bulk data action.
If this field is specified, "List JSON payloads" will be ignored.

The values to insert into your Supabase DB in JSON format. Must be a valid array of JSON objects.
If "List payload" is specified then this field is ignored.

If true, missing fields in the payload will be inserted as null values. Otherwise, missing fields will used the the default column value. Defaults to true. Only applies for bulk insert.

Count algorithm to use to count inserted rows.

• exact: Exact but slow count algorithm. Performs a COUNT(*) under the hood.
• planned: Approximated but fast count algorithm. Uses the Postgres statistics under the hood.
• estimated: Uses exact count for low numbers and planned count for high numbers.

If you set "true," a select operation will be executed post-insertion, and the inserted row(s) will be available in the "Last insert" and the "Last inserts" states.
This requires that you have an RLS (Row Level Security) policy that allows "select" on the table.

A list of fields that should have empty values (e.g., "") converted to null before inserting into your table. This is useful for columns that expect non-string types, like dates, where an empty string would cause an error.

The values to update your object with.

The values to update your object with in JSON format.

Please check this section for more details.

Count algorithm to use to count updated rows.

• exact: Exact but slow count algorithm. Performs a COUNT(*) under the hood.
• planned: Approximated but fast count algorithm. Uses the Postgres statistics under the hood.
• estimated: Uses exact count for low numbers and planned count for high numbers.

If you set "true," a select operation will be executed post-update, and the updated row will be available in the "Last update" and "Last updates" states.
This requires that you have an RLS (Row Level Security) policy that allows "select" on the table.

Upserting a single row (using Payload and/or JSON payload) or multiple rows (using List payload or List JSON payloads)

The values to upsert with. These will be automatically merged with the JSON payload field. To ensure a value is treated as a string, enclose it in double quotes (e.g., "text").

The values to upsert with in JSON format. These will be automatically merged with the payload field.

The values to upsert into your Supabase database when the upsert type is set to "bulk".
This must be a list of items that match your table schema.
You can use the Bulk data state as the value from the database component after adding data to it using the Add item to bulk data action. If this field is specified, "List JSON payloads" will be ignored.

The values to upsert into your Supabase DB in JSON format.
Must be a valid array of JSON objects (e.g. [{"c1": "v1", "c2", "v2"}, {"c1": "v1", "c2", "v2"}]).
If "List payload" is specified then this field is ignored.

If true, missing fields default to "null".
Otherwise, missing fields will used the the default column value. This only applies when inserting new rows, not when merging with existing rows under "Ignore duplicates?" is false. Defaults to true. Only applies for bulk upsert.

Count algorithm to use to count upserted rows.

• exact: Exact but slow count algorithm. Performs a COUNT(*) under the hood.
• planned: Approximated but fast count algorithm. Uses the Postgres statistics under the hood.
• estimated: Uses exact count for low numbers and planned count for high numbers.

Unique column(s) to specify how duplicate rows are determined. Two rows are duplicates if all the "On conflict" columns are equal.

If you set "true," a select operation will be executed post-upsert, and the upserted rows will be available in the "Last upsert" and "Last upserts" state. This requires that you have an RLS (Row Level Security) policy that allows "select" on the table.

Please check this section for more details.

Count algorithm to use to count deleted rows.

• exact: Exact but slow count algorithm. Performs a COUNT(*) under the hood.
• planned: Approximated but fast count algorithm. Uses the Postgres statistics under the hood.
• estimated: Uses exact count for low numbers and planned count for high numbers.