Choose a backend for each flow
Use the available connections without assuming that they synchronize with each other.
The editor lists AppStruct, Supabase, and Firebase under Backend, but they have different roles.
| Entry | Current purpose |
|---|---|
| AppStruct | Built-in tables and app records |
| Supabase | An external database connection and table schema |
| Firebase | Push-notification setup for iOS and Android apps |
Match the service to the task
For a web form, start with the backend that should own its saved records. Configure the appropriate data action, values, filters, and response mapping for that source.
Connecting more than one service does not create a shared table model or automatically copy records between them. Plan any cross-service transfer as an explicit operation and verify its result on both sides.
Keep the flow understandable
Name components and actions according to the task, document which source owns each record, and test a failure in each external dependency. Avoid presenting a flow as complete when only one of several writes succeeded.
For web data, see AppStruct Database and Supabase. For an external HTTP service, use the HTTP Request action when its API and authentication design are appropriate for the browser flow.