Definition: A database project is the data layer behind an app you build in Taskade Genesis. You describe what you track in plain English, and Taskade EVE, the meta-agent behind Taskade Genesis, builds the right fields and links the right projects together. No schema, no setup, no database knowledge required.
You are already doing a version of this. The customer list in your spreadsheet, the jobs in your inbox, the invoices in a folder named "to send." You already know what you track. A database project keeps all of it in one place, with the same fields filled in every time, ready for an AI agent or an automation to act on.
TL;DR: A database project is the app data behind your Taskade Genesis app. Describe what you track and Taskade EVE picks field types (text, number, date, select, USD currency) and links connected projects as the relational backbone. Powered by 15+ frontier models. Build yours free →
What is a database project?
A database project is structured app data that Taskade Genesis creates from your prompt. You say "track customers, their jobs, and the invoices for each job." Taskade Genesis turns that into clean records with named fields, and connects the projects so a customer shows their jobs and every job shows its invoices. The structure follows your words, not a database manual.
The result is one source of truth instead of three half-synced lists. Every record carries the same fields. Every link points to the right place. And because the data lives inside your Workspace, your agents and automations can read it and act on it the moment something changes.
How Taskade Genesis structures your data
You describe the business; Taskade EVE picks the fields and the links. There is no design step where you choose column types or draw a schema. You write a sentence, Taskade Genesis reads the intent, and the data layer appears ready to fill in. Add a need later, say it in plain English, and new fields slot into the existing records.
Connected projects: the relational backbone
Connected projects are how Taskade Genesis links one record to another. A customer connects to their jobs. Each job connects to its invoices. Open a customer and you see everything tied to them, without copying data between lists or keeping IDs in your head. This is the relational backbone of every app you build, and it is what turns three separate trackers into one working system.
For a service business, that backbone looks like this. Customers sit at the center. Jobs hang off each customer. Invoices hang off each job. Follow any link in either direction and the related records come with it.
Because the projects are connected, an automation can roll a job's invoices up to the customer, or flag a customer with an overdue invoice, without you touching a formula.
Under the hood, connected projects are the same relational model that powers every traditional database: a primary record, the records linked to it, and the relationships between them. The difference is you describe it in one sentence instead of designing tables and writing SQL. If you are curious how that data layer works at scale, system design explained walks through relational versus non-relational databases in plain English.
Field types you can use
Taskade Genesis assigns each field a type so the data stays clean and the right tools apply. A date field gets a date picker and feeds the Calendar and Gantt views. A USD currency field formats dollars and totals on its own. A select field offers a fixed set of choices, so a status is always one of the options you defined, never a typo.
| Field type | What it holds | Where it shines |
|---|---|---|
| Text | Names, notes, addresses, descriptions | Contact details, free-form notes |
| Number | Quantities, scores, counts | Stock levels, ratings, line quantities |
| Date | Due dates, appointments, deadlines | Scheduling, follow-ups, Calendar view |
| Select | One choice from a fixed list | Status, stage, priority, category |
| USD currency | Dollar amounts, formatted and summed | Invoice totals, deal value, budgets |
A record in a jobs project pulls these together into one tidy row.
┌─ JOB ────────────────────────────────────────────────┐
│ Title Roof repair, 14 Oak St (text) │
│ Customer → Maria Delgado (connected) │
│ Stage Scheduled ▾ (select) │
│ Visit date Jun 22, 2026 (date) │
│ Quantity 1 (number) │
│ Quote $2,400.00 (USD) │
└───────────────────────────────────────────────────────┘
How your data flows through an app
Data moves in a loop: it goes in, it gets read, it triggers action, and the action writes new data back. A form captures a lead. An agent reads the new record and drafts a follow-up. An automation watches the stage field and sends a reminder when a date arrives. Each step feeds the next, which is the Workspace DNA loop of Memory, Intelligence, and Execution at work on your own records.
| Step | What happens | Powered by |
|---|---|---|
| Capture | A form, import, or teammate adds a record | App forms |
| Read | An agent reasons over the data | 15+ frontier models |
| Act | An automation fires on a change | Reliable automation workflows |
| Update | New data writes back to the record | Connected projects |
Bring in data you already have
You do not start from an empty database. Taskade Genesis imports the customers, products, or jobs you already keep in spreadsheets and CSVs, then maps them to the right fields. The list you have been maintaining by hand becomes the first set of records in a real working app, with the structure filled in around it.
Frequently asked questions
Do I need to know SQL or design a schema?
No. You describe what you track in plain English and Taskade Genesis picks the field types and the links. There is no schema step, no table designer, and no database knowledge required. Taskade EVE reads the intent in your prompt and builds the data layer for you.
Can records link to each other?
Yes, through connected projects. A customer links to their jobs, and each job links to its invoices, so related records travel together. Connected projects are the relational backbone of every Taskade Genesis app. You set them up by describing the relationship in words.
What field types are available?
Text, number, date, and select fields cover most needs, plus a USD currency preset that formats and totals dollar amounts for you. A select field locks a value to a fixed list of choices, which keeps a status or stage consistent across every record.
Can I add fields after the app is built?
Yes. Describe the new field you need and Taskade Genesis adds it to the existing records without breaking what is already there. The data layer grows as your business does, so you start simple and expand when a new need appears.
Who can see and edit the data?
You control access with role-based permissions across 7 levels, from Owner down to Viewer. Published apps can also require built-in logins so only the right people reach your data, with optional password protection on top.
Can I import my existing spreadsheet?
Yes. Taskade Genesis imports from spreadsheets and CSVs, then maps your columns to the right field types. Your current list becomes the starting set of records, so you keep the data you already trust.
What you'd build with this
In Taskade Genesis, a database project becomes a tracker you and your team actually run on. Picture a job tracker for a service business: every customer connects to their jobs, every job connects to its invoices, and a status field moves each job from Scheduled to Done. You log in to one board, your crew updates their jobs from a phone, and a reliable automation sends the invoice reminder on its own when a due date passes. No spreadsheets to reconcile, no schema to maintain.
That same backbone scales into a full AI CRM when you are ready, and the Learn guide on building a CRM walks through it step by step.
Describe what you track and watch the data layer build itself. Start your first app free →