Message groups
Introduction
The Sublime Platform automatically groups similar messages to reduce alert fatigue and provide a better user experience when viewing flagged messages in the Dashboard.
This means that if 100 users receive the same email, you'll only see one grouping in the Dashboard. And if you have email alerts configured, for example, you'll only receive one alert.

In this example, 15 similar messages went to 7 different mailboxes. The subject is the same for each message, but the links within the body are different.
For more information about Sublime message grouping, read our blog post.
canonical_id
canonical_id
When a message is processed, it’s grouped with similar messages that have already been processed. This group ID is called the canonical_id
and it’s a unique identifier for the group itself. All messages in a group will have similar subjects, body contents, attachments, sender email, headers, etc., but none of these fields are guaranteed to be exactly the same.
The canonical_id
is a unique identifier of a group within an organization, but the same message in a different organization could belong to a group with an entirely different canonical_id
, even if it’s the only message in the group. It’s not recommended to use the canonical_id
across different organizations, because the values may not match.
Webhook actions
Since Webhook Actions currently operate on
message.flagged
events (opposed tomessage_group.flagged
events), you'll receive a webhook notification for every message that flags in a group. The flagged message'scanonical_id
is included in the webhook payload.
Updated 9 days ago