support.canned_reply.deleted

When this fires

A creator removes a saved reply from a project:

• Dashboard: the delete action on a snippet under Saved Replies in the support inbox.
• REST: DELETE /v1/projects/{project}/support/canned-replies/{reply}.
• MCP: the delete_canned_reply tool.

It does not fire when:

• The snippet was already gone. A second delete writes nothing and emits nothing.
• A message composed from the snippet is deleted or edited in a conversation. The saved reply is a template; what was sent is a separate message with its own lifecycle.
• The project itself is deleted. Its snippets go with it under project.deleted without a per-snippet event.

This is the final event for the given canned_reply.id. The snapshot is taken just before the row goes, so the payload still names what disappeared even though the canned reply endpoint now returns 404.

Caveats

• The body is gone with the row and was never in any event, so a mirror that wants to keep the text must have fetched it while the snippet existed.
• The freed shortcut can be reused by a new snippet straight away. Key a mirror on id, not on the shortcut.
• Remaining snippets are not renumbered. Their sort_order values are unchanged and no updated events follow a delete.

Related events

• support.canned_reply.created: the snippet's first appearance.
• support.canned_reply.updated: edits between creation and this event.

Header Parameters

The signed JSON envelope posted to your endpoint.

Response Body