Build Overview¶
Use this section as the map for how data moves through Centrali. The core path is:
If you are building a webhook-backed app, that is the order to learn the platform. Supporting capabilities like files, AI features, and Pages sit around that flow, but they are not the starting point.
Core Path¶
- Receive: Accept inbound HTTP traffic asynchronously through webhook-style HTTP triggers. If you need a synchronous request/response API instead, use endpoints in the React path.
- Store: Persist payloads and business data as records so they can be inspected, queried, enriched, and reused later.
- React: Run functions when records change, on a schedule, on demand, or through endpoints. Add automations when one function is not enough.
- Send: Push record changes and outcomes back out through outbound webhooks, notifications, or live subscriptions.
Receive¶
Start here when an outside system needs to call Centrali.
Store¶
Start here when accepted payloads need to become durable application data.
- Collections & Records
- Query Records
- Saved Queries
- Query Cheatsheet
- Secret Fields
- Record TTL
- CSV Import
- Bulk & Batch Operations
- Text Search
React¶
Start here when data is already in Centrali and you need code to run or a synchronous custom API surface.
- Triggers
- Functions
- Writing Functions
- Trigger Parameters
- Trigger Loop Prevention
- Function Re-run
- Automations
- Recipes
Send¶
Start here when Centrali needs to notify something downstream.
Supporting Areas¶
Workspace & Files¶
Pages (Beta)¶
Pages is available, but it is not the main frontend story for the docs. Most teams should pair Centrali with Next.js, React, Vue, or another UI stack through the SDK.