Event-type nodes that work on data tables let you start workflows based on records that live outside the contact profile, such as orders, policies, subscriptions, or any other connected dataset.
In this article, we’ll look at the New data event node, which reacts to the creation of a new record, and the Data periodic filter node, which periodically analyzes the contents of a data table to identify relevant records.
New data event
How does it work?
You can use two configuration modes: simple and advanced.
Simple mode
Configure the node in simple mode:
- Select the association field that links the contact to the data table. For example, for a trigger on the orders table, select the contact field that connects the contact to their ordered items.
- Filter the data table items, so you don’t process all records indiscriminately, but only specific ones. For example, filter orders from the last 90 days.
Advanced mode
Advanced mode lets you select a database and a contact extension without requiring a dedicated contact field for the association.
Data periodic filter
It works on the contents of data tables by running scheduled checks over time. Unlike the New data event node, it doesn’t trigger when a new record is created, but instead periodically filters the data table to identify records that meet specific conditions.
How does it work?
You can use two configuration modes: simple and advanced.
Simple mode
Configure the node in simple mode:
- Select the association field that links the contact to the data table. For example, for a trigger on the orders table, select the contact field that connects the contact to their ordered items.
- Filter the data table items, so you don’t process all records indiscriminately, but only specific ones. For example, filter today’s hoodie orders.
- Choose the data table fields you want to use in the workflow (for example, in conditions or content personalization elements). For each selected field, a workflow variable containing that information will be created.
- Configure the execution frequency of the filter, using the same parameters available in the “Periodic filter” node.
Advanced mode
Advanced mode lets you manage more complex data models.
Make sure to specify in the SELECT query the fields you need and the field that identifies the contact; you can filter the desired records directly in the query by adding a WHERE clause.
Use cases
The key difference between the more traditional Periodic filter node and this Data periodic filter node is that the workflow starts from data table records rather than from contact data.
Order history
The data table contains the order history of an eCommerce store.
Filter only the products, quantities, or contacts you’re interested in and use all the information available in each order row to trigger a repurchase workflow for the same product.
Insurance policies
The data table stores insurance policies associated with a contact. Trigger a workflow a few days before each policy expires and use the single-policy data as session variables to personalize the messages sent to the contact, such as the policy number, the insured item, the vehicle license plate, or specific clauses.