Data collections provide events for when records are created, updated, or deleted.

Event Types

created - Triggered when a new record is created
updated - Triggered when an existing record is updated
deleted - Triggered when a record is deleted

Implementation Types

Implementation Type	Description	When to Use	Documentation
Webhook ⭐	Real-time event notifications via HTTP callbacks	External app supports webhooks	Webhook Events
Pull Latest Records	Fetch records based on timestamps	API supports timestamp filtering, no webhooks	Pull Latest Implementations
Custom Pull	Subscribe/pull with state management	API has delta/change tracking	Custom Pull Implementation
Full Scan	Compare complete record snapshots	No other options available, small collections only	Full Scan Implementation

⭐ Recommended - Choose webhook implementation whenever possible for best performance and real-time updates.

If event implementation is not provided, a full-scan implementation will be used by default.

Data Collection Events Configuration Example

events:
  created:
    implementationType: webhook # or pull-latest, custom-pull, full-scan
  updated:
    implementationType: webhook
  deleted:
    implementationType: webhook

Configuring Intervals

The custom pull and pull-latest records implementation types use a default interval of 300 seconds, while Full scan uses a default interval of 10,800 seconds.

These intervals can be configured at either the trigger node level (when a data source is not used) or the data source level(when a data source is used) using the pull update interval and full sync interval options.

Refer to the limits page to see the minimum allowed interval.