Describe what you need to track
Tell Appaca what one record represents and which fields you need. It creates the table in conversation, or as part of building your app.
Store business records in Appaca’s built-in database. Use the same data across your internal apps, and ask Appaca to find the details your work needs.
No tables found. Try another name.
8 records used
Sales leads
| ID | Company | Contact | Stage | Deal value | Created | Updated |
|---|---|---|---|---|---|---|
| a81f3204 | Northstar Studio | Jamie Chen | Qualified | $18,000 | 29 Oct 2026, 10:00 | 30 Oct 2026, 09:40 |
| a81f3203 | Fieldwork Co. | Alex Morgan | Contacted | $9,500 | 29 Oct 2026, 10:00 | 30 Oct 2026, 09:25 |
| a81f3202 | Forma Partners | Sam Rivera | Qualified | $24,000 | 29 Oct 2026, 10:00 | 29 Oct 2026, 16:10 |
| a81f3201 | Common Ground | Taylor Brooks | New | $12,000 | 29 Oct 2026, 10:00 | 29 Oct 2026, 14:20 |
There are 2 qualified leads in your Sales leads table:
You can review the details in your CRM or open the table here.
Keep the next conversation moving.
No leads match.
Jamie Chen
Needs a shared workspace for a growing operations team. Follow up with a proposal.
Stored in Sales leads
A table defines your fields. A record holds one customer, request, or item. Keep that structure in Appaca, ready for the next app or conversation.
Tell Appaca what one record represents and which fields you need. It creates the table in conversation, or as part of building your app.
Your tables belong to the workspace. A CRM, a reporting tool, and a conversation can all work with the same sales records.
Open Data to find tables by name, browse their records, and see which apps use them. Check created and updated timestamps in the same view.
Turn your data into a tool your team can return to. Appaca builds the forms, lists, and actions around your process, with database access already connected.
Create, update, and delete records through the app. Keep customer details, request statuses, and working notes together.
Build views with search, filters, sorting, and pagination. Count matching records or change several in one operation.
Store text, numbers, fixed choices, lists, and more. Ask Appaca to add fields when you need to track something new.
Work with Appaca in a conversation, or connect an external agent through MCP. Both can work with the records already in your workspace.
For a connected agent, choose the workspace and approve its permissions. It can discover tables, inspect their fields, and query records. Approved write access also lets it add, update, and delete records.
Records give the work a structure. Files add the supporting detail. Routines bring it back into focus when it’s time to act.
Store proposals, images, and documents in workspace storage. Save their file references in the records they belong to, so your apps can bring both together.
Schedule a pipeline review or an operations check. Appaca can read workspace records and carry out the routine within the actions you’ve approved.
More about data storage, shared records, and the apps you build in Appaca.
No. Appaca includes a built-in database for structured workspace records. Describe what you want to track in a conversation or while building an app, and Appaca creates the table and fields. There is no separate database account, connection string, or hosting setup to manage.
Yes. Tables belong to your workspace and can be reused by its apps and conversations. Ask Appaca to use an existing table when you build a new tool. Changes to a shared record are available to the other apps that read that table.
Tables support text, numbers, true-or-false values, fixed choices, lists, and structured objects. Dates can be stored as formatted text values. Ask Appaca to add fields when your process changes; new fields do not automatically fill in older records.
The Data page is a read-only view for browsing tables, records, timestamps, and the apps using each table. To create, edit, or delete records, use an app built around the table or ask Appaca to make the change.
Mention a table in your message, or describe the table you want to use. Appaca can find its fields, read and filter records, count matches, and save structured results. It can also add fields and create or change records as part of the work you request.
Yes. Connected agents can access workspace data through Appaca’s MCP server with the permissions approved for their connection. The data:read permission allows table discovery, field inspection, and record queries. The data:write permission allows adding, updating, and deleting records. Data permissions apply across the connected workspace’s tables.
Yes. Apps can upload files to workspace storage and save a file reference in a record, keeping documents and images connected to the work they belong to. Files are stored separately from structured database records and count toward the workspace’s file-storage allowance.
Routines can use workspace tables for recurring work, such as a weekly pipeline review, within their approved actions. Records count toward your workspace’s database allowance, and files count toward its storage allowance. Direct MCP record reads and writes do not spend Appaca AI credits; work that uses Appaca’s intelligence is charged separately through workspace AI credits.
Describe what you need to track. Build the tools and workflows around it in Appaca.