Digest - SuprSend, Notification infrastructure for Product teams

Digest: Batches and sends summary notifications at a recurring digest schedule.

name

string

required

Human-readable name of the node

Example:

"Daily digest"

node_type

string

required

Allowed value: "digest"

schedule_type

enum<string>

required

Type of schedule. Determines how the digest schedule is resolved.

static: Schedule is fixed and will be used for all recipients.

dynamic: Schedule is dynamic and will be computed at runtime using the dynamic_schedule_expr.

category_digest_schedule: Uses the digest schedule configured on the notification category linked to this workflow. The recipient's selected digest option (or the category default) determines the schedule.

Available options:

static,

dynamic,

category_digest_schedule

description

string | null

Description of what this node does

dynamic_schedule_expr

string

jq-expression for deriving dynamic digest schedule at runtime. Eg. .digest_schedule

Example:

".digest_schedule"

schedule

object

Static schedule configuration for digest notifications.

Show child attributes

retain_count

integer

Maximum number of items to retain after digest closes (1-100). By default, 10 items are retained.

Required range: 1 <= x <= 100

retain_order

enum<string>

Retain items in this order when retain_count is specified.

Available options:

first,

last

trigger_min_count

integer

Digest will be sent if number of triggers in the batch are greater than or equal to this count, else skipped.

Required range: x >= 1

{ "name": "Daily digest", "node_type": "<string>", "description": "<string>", "dynamic_schedule_expr": ".digest_schedule", "schedule": { "interval": 2, "weekdays": [], "monthdays": [ { "pos": 0 } ], "time": "<string>", "dtstart": "<string>", "tz_fixed": "<string>" }, "retain_count": 50, "trigger_min_count": 2 }