Skip to content

Webhook event types

Use the ten supported document, collection, and comment event types without relying on unsupported lifecycle events.

Last updated

Quire v1 emits exactly ten webhook event types.

Event Meaning
document.created A new document was created.
document.updated Persisted collaborative edits settled into one metadata event.
document.moved A document moved between collection locations.
document.deleted A document moved to Trash.
collection.created A new collection was created.
collection.renamed A collection name and path changed.
collection.moved A collection moved to a new parent or root.
comment.created A new top-level comment or action-item thread was created.
comment.replied A reply was added to an existing thread.
comment.resolved A comment or action-item thread was resolved.

Scope matching

Team subscriptions match eligible events throughout the team. Collection subscriptions recursively match their selected collection and descendants.

A document move is evaluated against both its previous and destination locations, so a subscription can learn that a document entered or left its subtree. Collection rename and move matching also accounts for ancestor operations that change the subscribed subtree's path.

Settled updates

Live editing produces many persisted append operations. Quire waits 10 seconds after the latest persisted append before emitting document.updated. Continuous editing is flushed after a maximum 60-second batch window.

The event aggregates contributing actors, first and last history sequence numbers, batch start and end timestamps, and first/current locations. A batch containing any human contribution is delivered even when Include agent events is off. An agent-only event is delivered only when that option is enabled.

Events not in v1

Permanent document purge, document restore, collection.deleted, and comment.reopened are not v1 webhook events. Consumers should use MCP to reconcile current state when their workflow depends on those transitions.