Activity Log Metadata Versions

Each activity log event is tagged with a metadata version that describes the shape of its payload. This page contains the version changelog. Reference it when building Salesforce components, webhook handlers, or other integrations that consume activity data.

Version	Released	Summary
0.01	2024-11-02	Initial schema.
0.02	2026-03-11	Added `post.deleted` and `comment.deleted` activity types.
0.03	2026-03-21	Added `site.auth.login_success` and `site.auth.login_failure` activity types.
0.04	2026-04-10	Widened `post.edited` and `comment.edited` `source` to include `'slack'`.
0.05	2026-04-18	Added optional `message_id` to `post.created`, `post.edited`, `post.deleted`, `comment.created`, `comment.edited`, and `comment.deleted`.
0.06	2026-06-11	`message_id` values were regenerated and are not continuous with 0.05 (same `msg_` format, new values). Use `post_id` / `comment_id` for cross-version correlation.
0.07	2026-07-17	Added the `slack_profile.photo.updated` activity type.
0.08	2026-09-18	Added the `answer.selected`, `answer.unselected` and `answer.marked_best` activity types.
0.09	2026-09-22	Added the `slack_channel.member_joined` activity type.
0.10	2026-09-28	Added optional `registered_by_profile_id` to `calendar_event.user_registered`: present only when an admin registered the member on their behalf, naming that admin. Absent when the member registered themselves.
0.11	2026-10-28	Posts and comments created without a legacy ID record their message’s public ID (`msg_…`) in `post_id` and `comment_id`. Read output is unchanged, since every version already returns that ID.

IDs in the payload

Every *_id in an activity’s metadata is the public ID of the record it names, such as feed_A1b2C3d4E5f6 for a feed or prof_9f2b8c1d4e5a for a member. Where the Admin API or MCP server returns that record, it returns the same ID. A Slack channel keeps Slack’s own ID (for example C0123ABCD), and so does a Slack user. An ID is null when the record it names no longer exists, or when it belongs to a member who has been erased. post_id and comment_id carry the public ID of the message that holds the post or comment (for example msg_A1b2C3d4E5f6). From 0.06 on it equals message_id, and on every version it is the ID to correlate post and comment activity by. This applies to every version above, because IDs are translated when the activity is read, not when it is recorded. Salesforce records synced by earlier integrations carried internal IDs (UUIDs) in these fields. They are rewritten to public IDs when the integration’s record keys move to public IDs.

Getting Started

App Guides

Platform

Integrations

Support

Security

Activity Log Metadata Versions

IDs in the payload

​IDs in the payload

IDs in the payload