Event Catalog
The catalog of what can happen: every event type the installed apps declare, each with an example payload. This is where you look before wiring a workflow or an outbound webhook to a topic.
Where you find it
Integration Studio › Events › Event Catalog —
/integrations/defined-events. The sidebar says Event Catalog; the page
title is Defined Events.
Fields and controls
The list is headed Emits — published by this tenant's apps; the tenant in the screenshot declares 117 event types.
| Column | What it shows |
|---|---|
| Topic | The event type in code style, for example revenexx.carts.cart.abandoned, each with an example link that opens a sample payload. |
| Fired by | App for events an app publishes deliberately, or Row change for database-level change events. |
| App | The owning package with its version, for example revenexx/customers v0.30.0. |
| Entity | For row-change events, the table behind them — carts, channels, addresses. |
| Version | The event's version. |
Search covers topic, app and entity.
What happens when you change it
Nothing directly — the catalog reflects what installed apps declare in their manifests. Installing or updating an app is what changes this list. What you do from here is downstream: bind a messaging template to a topic, subscribe an outbound webhook, or trigger a workflow.
Permissions
Not verified.
Related
- Event Stream — the types firing in reality.
- Guide: Events and webhooks