
Browse Topics
On this page (5)
Database Projects
Definition: Database Projects are Taskade projects configured with Custom Fields and structured schemas that serve as the data backbone for Genesis apps, automations, and AI agent knowledge. They combine the flexibility of project-based work with the structure of a relational database.
Projects as Databases
Traditional databases require schemas, migrations, and SQL knowledge. Taskade Database Projects give you structured data storage through the familiar project interface:
Create a Schema: Add Custom Fields (Select, Number, Text, Password) to define your data structure
Enter Data: Each task/node becomes a record; each field becomes a column
Query with AI: Ask agents to search, filter, and summarize your data using natural language
Automate: Trigger workflows when records are created, updated, or match specific conditions
How Database Projects Power Genesis
When you build a Taskade Genesis app, Database Projects become the memory layer - the first pillar of Workspace DNA:
Form Submissions โ Database Records: User input through Genesis app forms creates new project nodes with field values populated automatically.
Agent Access: AI agents read from and write to Database Projects, enabling intelligent responses based on your actual business data.
Automation Triggers: Changes in Database Projects fire automation events - new records, field updates, or threshold crossings can trigger entire workflows.
Real-Time Sync: All data updates propagate instantly across the app interface, agent knowledge, and automation triggers.
Example: Client Onboarding Database
Schema:
- Client Name (Text)
- Company (Text)
- Contract Value (Number)
- Status (Select: New, Onboarding, Active, Churned)
- Account Manager (Text)
Connected Components:
- Genesis portal for client self-service
- Onboarding agent that guides new clients
- Automation that notifies the team on status changes
- Dashboard showing pipeline metrics
Database vs. Traditional Projects
| Feature | Traditional Project | Database Project |
|---|---|---|
| Structure | Free-form hierarchy | Typed fields + hierarchy |
| Data Entry | Notes and checklists | Structured field values |
| Querying | Manual search | AI-powered + field filters |
| Automation | Task-level triggers | Field-level triggers |
| Genesis Apps | Content source | Full data backend |
Best Practices
Design Your Schema First: Plan which fields you need before adding data. Changing schemas later is possible but easier to get right upfront.
One Database Per Domain: Keep each Database Project focused on a single data domain (Clients, Products, Tickets) rather than mixing concerns.
Use Select Fields for Status: Select fields enable automation triggers on specific values and provide clean filtering in Table View.
Connect to Agents: Train an AI agent on your Database Project so it can answer questions about your data in natural language.
Related Concepts: Custom Fields, Taskade Genesis, Three Pillars, Automation