support.canned_reply.deleted
A saved reply is removed from a project's support inbox.
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_replytool.
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.deletedwithout 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 returns404.
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
shortcutcan be reused by a new snippet straight away. Key a mirror onid, not on the shortcut. - Remaining snippets are not renumbered. Their
sort_ordervalues are unchanged and noupdatedevents follow a delete.
Related events
support.canned_reply.created: the snippet's first appearance.support.canned_reply.updated: edits between creation and this event.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.
How is this guide?
Last updated on