DataStore Trigger
Description
Section titled “Description”The DataStoreTrigger module is a trigger that automatically initiates a workflow when changes occur in a DataStore group. It allows monitoring insertion, update, and deletion events of records. It can filter by specific tags and configure the tag evaluation mode (any, all, or exclude). The module provides the next node with all event information: event type, current and previous record data, record metadata (ID, key, group, tags), and support for bulk events (multiple records in one operation).
Configuration
Section titled “Configuration”Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
| group_name | dataStoreGroup | Yes | Selects the DataStore group that will activate this trigger. You can only monitor ONE group per trigger. |
| events | select | Yes | Events to monitor: All, Insert only, Update only, Delete only, or combinations. Default: insert,update,delete. |
| filter_tags | dataStoreGroupTags | No | Only activate the trigger for records that have these tags. Leave empty for all records. Depends on the selected group. |
| filter_tag_mode | select | No | Tag evaluation mode: Any (OR), All (AND), Exclude. Default: any. |
| trigger_id | hidden | No | Registered trigger ID. Automatically generated when saving. |
Output
Section titled “Output”{ "nextModule": "siguiente_modulo", "data": { "event": { "type": "insert", "timestamp": "2026-03-23T10:00:00.000Z", "group": "clientes", "isBulk": false }, "record": { "nombre": "Juan", "email": "juan@ejemplo.com" }, "previousRecord": null, "_record": { "id": 123, "key": "juan@ejemplo.com", "group": "clientes", "tags": ["nuevo", "vip"] }, "records": null, "count": 1, "_trigger": { "trigger_id": "abc123", "node_id": "DataStoreTrigger_1", "conditions": null, "raw": {} } }}Usage Example
Section titled “Usage Example”Basic case
Section titled “Basic case”{ "label": "DataStore Trigger", "group_name": "clientes", "events": "insert,update", "filter_tags": "", "filter_tag_mode": "any"}- Only one DataStore group can be monitored per trigger.
- For update events,
previousRecordcontains the data before the change. - For bulk events, the
recordsfield contains an array with all affected records andrecordwill be null. - The
event.isBulkfield indicates whether the event affected multiple records. - The
trigger_idis automatically generated when saving the workflow; it does not need to be configured manually. - Supports tag wildcards with modes: any (OR), all (AND), exclude.
Related Nodes
Section titled “Related Nodes”- dataStore (for CRUD operations on the DataStore)
- decision (to evaluate the event type)
- iterator (to iterate over records in bulk events)