Resources
Resources are the data connections that power an app. Every piece of data an app displays or writes comes from a resource — either a workflow or a table — that you explicitly connect in the App Builder editor.
To add a resource, open the Resources panel in the editor, click Add resource, and select a workflow or table. Give it a short, descriptive alias that you will use in your prompts. In a long list, search by name or description, or filter by the labels set on the workflows and tables.
Workflows versus tables
| Tables | Workflows | |
|---|---|---|
| What they are | Structured data with defined columns | Processes that fetch, transform, or send data |
| Schema visibility | Immediately available to App Builder | Requires 3+ executions before App Builder can use it |
| Best for | Static or semi-static master data, transactional records | Dynamic data, M3 integration, multi-source combinations |
| Setup speed | Fastest — add and prompt immediately | Slower initial setup due to the run requirement |
| Supports writes | Yes — forms can save directly to a table | Yes — via workflow execution |
Start with a table-backed app to learn the builder. Tables are immediately ready and require no warmup runs.
Using aliases
An alias is the name you give a resource in the editor. It is the term you use when prompting — for example, "show suppliers from supplier_table" or "trigger order_approval_workflow when the button is clicked."
Use aliases that are:
- Short and lowercase with underscores (e.g.
invoice_table,goods_receipt_workflow) - Self-explanatory to anyone reading your prompts
- Consistent — once set, don't rename the alias without re-prompting the app
Re-prompting when resources change
App Builder captures the structure of resources at prompt time. If a workflow or table changes later, you must re-prompt the app to reflect the change.
See Prompting — When resources change for the full guidance.