Tables can be dynamically updated and managed through workflow actions. These actions allow you to add, update, or manipulate table data as part of an automated workflow.

All Table-related actions can be found under the “Tables” collection in the action panel of the workflow editor

Managing Table Records with Workflow Actions

Blink provides powerful workflow actions that allow you to automate the management of table records. These actions enable you to add, update, retrieve, and delete records dynamically within your workflows.

Add a Record

Add new records to a table by entering field names and values or by providing data in JSON format.JSON input supports bulk creation, allowing multiple records to be added simultaneously in a single action.

You can also use the Variable Picker to easily insert dynamic variables into the ‘Add Record’ action’s input fields.

Add a record to a table by entering the table field name and the table field value.

ParameterDescription
TableThe name of the table.
RecordData of record, enter the field name and field value.

Create or Update Record

Ensure data consistency by either updating an existing record or creating a new one if no match is found. You can define specific conditions to determine whether a record should be updated or newly inserted. Supports both direct value input and JSON formatting for structured updates.

Create or Update an entire Record in a table by selecting the entire record option.

Note: Please note that if you leave any fields empty in the Create or Update Record action, the existing values in the table will remain unchanged.

ParameterDescription
TableThe name of the table.
Create or Update ConditionSet the condition for deciding weather to create or update the selected record.
Record Data FormatEntire Record
RecordThe value of the record you want to create or update

”Add Records” Action vs. “Create or Update Records” Action

When adding data to a table, choosing the right action ensures accuracy and prevents duplication. Use “Add Records” when you need to insert new data without verifying existing entries. If you want to update existing records or avoid duplicates, “Create or Update Records” is the better choice, as it checks for a match before adding new data. The table below outlines the key differences between these actions.

ActionBehaviorKey Difference
Add RecordWhen you need to insert new data without checking for existing recordsAdds records without checking for duplicates
Create or Update RecordWhen you want to prevent duplicates or update existing records based on specific conditionsChecks for a matching record before adding; updates if found, adds if not

You can manually set certain field types (Text, Numbers, Users, Time) as unique in the table. This ensures that each entry in a specific column is distinct, preventing duplicate values. For more details, visit this guide.


Get a Record

Fetch table data based on specified criteria using conditions, RQL queries, or SQL queries. Choose how the data is structured in the output (Table, JSON, or CSV) and refine results by applying filters, sorting, limits, and pagination options.

Get a Record from a table by using a condition. All records that match the condition will be returned.

ParameterDescription
Query MethodBy Condition- The query method to get records
TableThe table you want to get records from.
FieldsTable Fields.
ConditionCondition that compares two table field values.
Output FormatThe format of the output the records are returned- Table, JSON or CSV .
Limit (optional)Limit the amount of records returned by the query.
Offset (optional)Choose the offset from the data to start querying the table from.
Order By (optional)Choose what field to order the results by.
Sort (optional)Sort the records by ascending or descending order.
Include Query Metadata In Output (optional)Check the box to include Query Metadata in the Output.
All Pages (optional)Check the box to return all data in the table(this setting invalidates the Limit and Offset fields.)

Delete a Record

Remove specific records from a table by referencing their unique ID or by setting a condition to delete multiple records that meet certain criteria. This ensures precise control over data removal while preventing accidental deletions.

Deletes a record from a table by the Record ID.

ParameterDescription
Table NameThe name of the table.
Record IDThe record unique identifier. Can be obtained via the Select action.

Managing Tables with Workflow Actions

Blink provides powerful workflow actions that allow you to automate the management of tables. These actions enable you to create, clear, retrieve, copy and delete tables dynamically within your workflows.


Create a Table

Create a table based on a schema.

ParameterDescription
Table NameThe name of the table.
Table SchemaThe schema of the table in JSON format.
For more information, see the Copy table schema.
Skip if ExistsSkips table creation if a table with the same name already exists.

Copy Table Schema

For each table that is created, there is a table schema.


Does Table Exist

Check if a table with a given display name exists.

When using the Create Table action, and the chosen name of a table already exists, the Create Table action will fail. In order to prevent this scenario, you are recommended to use the Does Table Exist Action before the Create Table step.

ParameterDescription
Table NameThe name of the table.
Search BySearch by name, display name or both. Default is display name.

Clear a Table

Clear all table records.

ParameterDescription
Table NameThe name of the table.

Delete a Table

Deletes the entire table.

ParameterDescription
Table NameThe name of the table.

Event-Based Triggers for Table Events

New Table Record

The New Table Record option is an Event-Based Trigger event that executes the workflow every time a new record is added to the selected table.

Table Record Updated

The Table Record Updated option is an Event-Based Trigger event that executes the workflow every time a record in the selected table is updated.

Make sure the “Table Name” in the trigger setup exactly matches the name of your table. Even small differences, like extra spaces or capitalization, can cause the trigger to fail.