Skip to main content

Projects & Databases: The Memory Pillar

The Memory Pillar β€” databases that store and retrieve workspace data.

Updated yesterday

Overview

Projects are the Memory component of your Workspace DNA, one of three pillars that power Genesis apps and form the Tree of Life architecture.

  • πŸ“š Memory (Projects): Your workspace's structured data and knowledge base
    ​

  • 🧠 Intelligence (Agents): Your workspace's reasoning and decision-making layer
    ​

  • ⚑ Execution (Automations): Your workspace's actions and workflows

Think of projects as the living memory of your workspace. They're act as databases that continuously feed context to your AI agents, apps, and automations.

  • Providing Context: Give AI agents the knowledge they need to make decisions

  • Storing Relationships: Map connections between customers, orders, and more

  • Capturing Results: Log outcomes of automation runs and app interactions

  • Evolving Over Time: Enrich your workspace DNA with real business knowledge

πŸ’‘ Note: When you create a Genesis app, your projects become the database backend of that application, storing customer records, managing inventory, tracking appointments, and maintaining structured information.

In this guide, you'll learn how to work with database projects in Genesis apps.


What Are Database Projects?

When Genesis creates an app, it automatically generates database projects that serve as your app's data layer. Those databases are perfect for apps like:

  • Customer portals with client data and project history
    ​

  • Booking systems with appointments and customer records
    ​

  • Inventory apps with product catalogs and stock levels
    ​

  • CRM applications with leads, contacts, and sales data

πŸ’‘ Note: Database projects default to the Table view for easy data management, but you can switch between views at any time.


Using Database Projects

Genesis apps use database projects for:

  • Smart data structure automatically created based on your app's needs
    ​

  • Real-time synchronization between your app interface and database
    ​

  • AI-powered insights from agents trained on your data
    ​

  • Automated workflows that respond to the actions within the app

Your workspaces and project become the single source of truth.


Creating Database Projects

There are several methods to create the memory pillar for your workspace.


Genesis-Generated Databases

When you create an app, Genesis automatically builds the required projects:

  • Describe your app needs to Genesis in plain English.

  • Genesis analyzes your requirements and generates projects to store data.
    ​

  • Custom fields and relationships are automatically configured.
    ​

  • Your app launches with a fully functional database backend.

You can also request a specific data structure in your prompts:

  • "Create a yoga studio booking app with a customer database, class schedule database, and instructor database."
  • "Build a client portal for our agency with a client database, project database, and invoice database."
  • "Make an inventory management system with a product database, supplier database, and order database."


Manual Database Creation

Here's how to add new database projects to existing apps:

  • Open your app in Taskade
    ​

  • Click + New Project within the app's dashboard view.
    ​

  • Choose a template, ask Taskade to generate a project, or start blank.
    ​

  • Configure custom fields inside the project.
    ​

  • Ask Genesis to connect to connect the database to the app.


Importing Data into App Databases

Transform existing business data into app-ready databases:

  • Navigate to your app's dashboard.
    ​

  • Got to Projects β†’ Import β†’ Import CSV.
    ​

  • Upload your file (CSV, Excel, Google Sheets).
    ​

  • Ask Genesis to use connect the database and adjust the custom fields.


App Database Automation

Automated App Workflows

Your app's database projects can trigger intelligent workflows.

For example, you can prompt Genesis in the chat to create:

Booking App Automations

  • When appointment status β†’ "Confirmed" β†’ Send reminder email
    ​

  • When new booking β†’ Created β†’ Notify staff and block calendar
    ​

  • When payment β†’ "Received" β†’ Update booking status and send receipt

CRM App Automations

  • When lead score β†’ Above 80 β†’ Assign to sales rep and create follow-up task
    ​

  • When deal stage β†’ "Proposal Sent" β†’ Set 7-day follow-up reminder
    ​

  • When client β†’ "Inactive for 30 days" β†’ Trigger re-engagement campaign

Inventory App Automations

  • When stock level β†’ Below minimum β†’ Create purchase order
    ​

  • When new product β†’ Added β†’ Update catalog and notify sales team
    ​

  • When order β†’ "Shipped" β†’ Send tracking info to customer

These are just a handful of examples of what can be accomplished with automation flows. Experiment, try different approaches, and build your perfect setup!


AI Agents in App Databases

Your app's custom AI agents can work directly with database data. Simply ask Genesis to generate a new AI agent specifically for your app.

πŸ’‘ Note: New to the concept of AI agents? Visit our guide to Custom AI Agents to learn everything you need to know to get stated.

Once you've created agents for your apps, you can ask them to:

  • Data analysis: "Analyze this month's bookings and suggest optimization"
    ​

  • Smart categorization: Automatically classify new leads or products
    ​

  • Predictive insights: Forecast inventory needs or sales trends
    ​

  • Data cleanup: Find and fix inconsistencies in customer records
    ​

  • Content generation: Create product descriptions or email templates
    ​

  • Decision support: Recommend next actions based on data patterns

πŸ’‘ Note: Read our guide to AI Agents Tools to learn more.


Best Practices for App Databases

Keep Data Focused

  • One main purpose per database project
    ​

  • Related data in the same project
    ​

  • Clear naming conventions for fields
    ​

  • Logical field ordering for user experience

Plan For Growth

  • Add fields you might need later
    ​

  • Use consistent data formats across apps
    ​

  • Regular data cleanup and validation\

Control Access

  • Control who can view the live app
    ​

  • Separate admin vs. user permissions
    ​

  • Secure sensitive data fields
    ​

  • Implement role-based access control
    ​

  • Limit who can edit the underlying data


🧬 Helpful Links

Did this answer your question?