Table

The Table trigger reacts to committed row inserts, updates, or deletes in a Sim table. For example, start enrichment when a row is added or send a notification when a watched status changes.

Configuration

  1. Select Table, or enter Table ID in advanced mode. Choose a table in the workflow's workspace.
  2. Choose Event: Row Inserted, Row Updated, or Row Deleted. The default is Row Inserted.
  3. For updates, optionally select Watch Columns. Leave it empty to react to any update.
  4. Choose Map Row Values to Headers, on by default, then connect the downstream blocks.
  5. Deploy the workflow and make the corresponding row change. Verify the run in Logs.

One trigger watches one event type. Use separate trigger blocks to handle several event types.

Outputs

These examples use a trigger named Table:

ReferenceValue
<table.row>Name-keyed row with missing schema columns filled, when header mapping is on; otherwise null
<table.rawRow>Row values projected to column names, including select option names
<table.previousRow>Previous row for an update, deleted row data for a delete, or null for an insert
<table.changedColumns>Changed column names for an update; empty for inserts and deletes
<table.rowId>Row ID
<table.headers>Table column names
<table.tableId>Table ID
<table.tableName>Table name
<table.timestamp>Event time in ISO format

Watch Columns applies only to updates. If none of the watched columns changed, that update does not start a run.

Delivery behavior

Table events fire directly after the row mutation rather than waiting for a poll. Workflow dispatch is fire-and-forget: a workflow failure does not undo the committed table change. Runs use the deployed trigger configuration, so deploy an update after changing its event or watched columns.