Webhooks
Event Reference
The events you can subscribe an endpoint to, grouped by category. Select the events you want per endpoint in Settings → Webhooks.
Engagement
| Event | Description |
|---|---|
event.pod_is_viewed | A viewer opened the Pod. |
event.new_question | A viewer asked a new question. |
event.pod_is_commented | A comment was added to the Pod. |
event.pod_is_shared | The Pod was shared. |
event.form_submitted | A form in the Pod was submitted. |
event.map_is_updated | A mutual action plan was updated. |
Media & widgets
| Event | Description |
|---|---|
event.widget_video_played | A video widget was played. |
event.widget_video_paused | A video widget was paused. |
event.widget_voice_note_played | A voice note was played. |
event.widget_proposal_downloaded | A proposal was downloaded. |
event.widget_timeline_item_completed | A timeline item was marked complete. |
Files & links
| Event | Description |
|---|---|
event.file_uploaded | A file was uploaded to the Pod. |
event.file_downloaded | A file was downloaded from the Pod. |
event.link_clicked | A link in the Pod was clicked. |
event.widget_link_copied | A widget link was copied. |
event.page_link_copied | A page link was copied. |
Internal events
Events raised by trumpet or a user, rather than by an external viewer. Their data shape differs from engagement events — see the status-change payload.
| Event | Description |
|---|---|
event.pod_status_changed | A Pod's status changed in trumpet — via the UI (including drag-and-drop on the board), a bulk change, Copilot, or first-view auto-promotion. |
⚠️
CRM-originated changes don't emit
To avoid loops, status changes that come from a connected CRM — or through the Update Pod API — do not fire
event.pod_status_changed. Only changes originating inside trumpet do.💡
More events over time
Additional event types may be added as trumpet adds features. Existing endpoints only receive the events they are explicitly subscribed to — new event types must be enabled per endpoint in Settings → Webhooks.