Event registry and subscribers
Events connect TaruviBase's fixed set of events to your functions. You choose which functions run when an event fires; TaruviBase fires events for user and data table activity in your site.
Resource model
- Event name — one of TaruviBase's fixed event names. You can't create new ones.
- Subscription — links one event to one function. Deleting a function removes its subscriptions.
Each function can subscribe to an event once, and to as many events as you like.
Event names
| Event | Category | Notes |
|---|---|---|
| PRE_USER_CREATE | User lifecycle | Blocking during site-user creation — see Emission and delivery |
| POST_USER_CREATE | User lifecycle | After the user row commits |
| POST_USER_UPDATE | User lifecycle | Previous and updated payloads |
| POST_USER_DELETE | User lifecycle | User delete flow |
| RECORD_CREATE | Database records | One event per created record |
| RECORD_UPDATE | Database records | Record update |
| RECORD_DELETE | Database records | Record delete |
List them with GET /api/cloud/events/. Details: Event types.
Subscription scope
A subscription belongs to the site, not to one app. Record events only run functions in the table's app. To see one app's subscribers, use GET /api/apps/APP_SLUG/events/EVENT_NAME/ or the app's Events page in the Console.
You can't publish events or define custom event names through the API.