Events
Run your functions automatically when users or data records change. Subscribe a function to one of TaruviBase's events, and TaruviBase calls it each time that event happens.
Access rules and limits are on Security and limits.
How Events works
A subscription links one event to one function. TaruviBase has a fixed set of events; see Event types.
| Event | Fires when |
|---|---|
PRE_USER_CREATE | A site user is about to be created — the function can check or change the user, or stop the creation |
POST_USER_CREATE | A site user was created |
POST_USER_UPDATE | A site user was updated |
POST_USER_DELETE | A site user was deleted |
RECORD_CREATE | A record was created in a data table |
RECORD_UPDATE | A record was updated |
RECORD_DELETE | A record was deleted |
Record events only run functions that belong to the same app as the data table. User events run every subscribed function in the site.
What you can build
| Goal | Start here |
|---|---|
| React to new records, such as sending a notification | Subscribe to your first event |
| Validate or enrich new users before they are created | Emission and delivery |
| Add, remove, and review subscriptions | Manage subscriptions |
| Run a function only for some records | Filter conditions |
Choose an interface
| Interface | Use it to |
|---|---|
| TaruviBase Console | Subscribe and unsubscribe functions and see each event's subscribers. Open your app and select Events. |
| REST API | Manage subscriptions from scripts and automation |
| Functions | Write the code that runs when an event fires — see Functions |
The JavaScript and Python SDKs don't include Events methods; use the Console or the REST API.
Start building
- Subscribe to your first event.
- Manage subscriptions.
- Read Emission and delivery for what your function receives.
- Review Security and limits before production.
Good to know
- You can't define your own event names or publish events over the API.
- TaruviBase doesn't retry a function run that fails. Make functions safe to run again, and check their runs in Logs and invocations.