Skip to content

Event catalogue

GET /events returns this list at runtime.

EventFired whendata
ticket.createdA ticket is createdticket
ticket.updatedA ticket field is updated (changes.field, oldValue, newValue)ticket
ticket.state_changedTicket state changesticket
ticket.assignedAssignee or group changesticket
ticket.comment_addedA comment is added (changes.commentHtml)ticket
ticket.comment_removedA comment is removedticket
ticket.attachment_addedAn attachment is added (changes.fileName)ticket
ticket.attachment_removedAn attachment is removedticket
ticket.approvedAn approval step is approvedticket
ticket.rejectedAn approval step is rejected (changes.note)ticket
ticket.deletedA ticket is deletedticket (id, number, boardId)
ticket.sla_breachedAn SLA target is breached (changes.metric, changes.policy)ticket
kb.article_approvedA knowledge base article is approvedarticle summary
kb.article_rejectedA knowledge base article is rejectedarticle summary
user.createdA user activates their accountuser
automation.triggeredAn automation rule runs its Send a webhook action (changes.field is the rule name, changes.note its optional note)ticket
webhook.testYou press Test on a subscriptiontest message

Filtering on field values

A subscription filters by event type and board only. To react to a narrower condition, such as priority is High or the customer is in a given company, build an automation rule with those conditions and give it the Send a webhook action, choosing this subscription as the target. The rule's conditions do the filtering, and the delivery arrives as automation.triggered.

A targeted delivery ignores the subscription's own event and board filters, because the rule already decided that it should be sent.

Board filters apply to ticket.* events. Events are delivered in the order they were queued per subscription, but ordering across retries is not guaranteed — use occurredAt when it matters.

Stoneity Public API v1