Skip to main content
The Send to Digest node adds the current event to a digest owned by a subscription topic. Events accumulate per user and release on that topic’s schedule. Use it for periodic summaries, a daily activity email or a weekly report, instead of one notification per event. Use Send to Digest when releases should follow a fixed schedule that the user controls. Use the to release based on volume or an inactivity window within the journey itself.

Configuration

Configure the digest on the topic

The schedule, categories, retention, and template mapping live on the subscription topic, not on the node. Configure them in the (Platform → Preferences):
  • Schedule: when the digest releases (at least one schedule is required, multiple appear as choices on the hosted preferences page).
  • Categories: separate types of data within one digest, each with its own retention (First, Last, Highest, or Lowest N, where Highest and Lowest need a sort key).
  • Template mapping: the notification template that renders the released digest.
The Send to Digest node only collects. Releases happen when the topic’s schedule fires.

Digest payload

When the digest releases, each category is delivered with the total count and the retained items:
count is the total number of events received (it can exceed the retained count). items are the retained events. Reference this data in your digest template.

Via the API

In a journey definition, a Send to Digest node uses type: "add-to-digest":
See for the full node reference.