Skip to main content
Databases are the heart of Hyperaide. They are collections of structured information that help you organize and manage everything important to you.

​
What are Databases?

Think of databases as smart, flexible storage containers for your information. You can create a database for tasks, projects, ideas, contacts, goals, habits—anything you want to track and manage.
Example: A tasks database might include fields like name, description, due date, and priority. A contacts database might include name, email, phone number, and relationship type.
Each database you create can have its own set of fields, and you can link databases together to create powerful relationships between your information.

​
Creating a Database

There are two ways to create a database in Hyperaide:
  • Ask Your Assistant
  • Manual Creation
The easiest way! Just tell your assistant what you want to track:
  • “Create a database for my reading list”
  • “I need a database to track my workouts”
  • “Set up a projects database”
Your assistant will create the database and suggest relevant fields based on what you want to track.

​
Database Fields

Each database contains fields—the individual pieces of information that make up a database record. Hyperaide supports several field types:

Text

Store any text content like names, descriptions, notes, or URLs

Number

Store numerical values for quantities, prices, ratings, or counts

Date

Store dates and times for deadlines, appointments, or timestamps

Boolean

Store yes/no values like completed status or flags

​
Field Descriptions

Each field has a description that tells Hyperaide what the field is for and how to use it. This is crucial—think of it like a prompt that guides your assistant’s understanding.
Pro tip: Write clear, detailed field descriptions. Instead of “date,” write “The due date when this task should be completed.” Your assistant uses these descriptions to better understand your data.

​
Database Descriptions

Your database itself also has a description. This description helps Hyperaide understand the purpose of the database and when to use it. 
"Tasks I need to complete, including personal and work-related items. Each task has a description, due date, priority level, and completion status. Use this database to track what I need to do and when."
The better your description, the better your assistant understands how to work with your data.

​
Linking Databases

This is where Hyperaide becomes powerful. Database records can link to records in other databases automatically—no additional setup required.
1

Create related databases

For example, create both a “Tasks” and “Projects” database
2

Tell your assistant to link them

Simply say: “Link this task to the Website Redesign project”
3

Your assistant handles the rest

Hyperaide automatically creates and maintains the relationships

​
Common Linking Patterns

Link tasks to projects to organize work and track progress by project
Link tasks to people to remember who you need to follow up with
Link notes and ideas to specific projects for easy reference
Link daily habits to longer-term goals to track progress

​
Working with Your Databases

Once your databases are set up, interact with them using natural language:
  • Creating Records
  • Querying Records
  • Updating Records
  • Bulk Operations
"Add a task to review the quarterly report by Friday"
"Create a new project called Website Redesign"
"Add John Smith to my contacts with email [email protected]"

​
Best Practices

Start Simple

Begin with basic databases and add complexity as needed. You can always add fields later.

Descriptive Names

Use clear field and database names. “Due Date” is better than “Date” or “Date1”.

Rich Descriptions

Write detailed descriptions for databases and fields. This helps your assistant understand your data better.

Link Strategically

Connect related databases to create a knowledge graph of your life and work.

​
Examples

Here are some common database setups to inspire you:
Tasks Database: name (text), description (text), due_date (date), priority (text), completed (boolean)Projects Database: name (text), description (text), status (text), start_date (date)Link tasks to projects for full project management capabilities.
Contacts Database: name (text), email (text), phone (text), relationship (text), notes (text)Interactions Database: date (date), type (text), notes (text)Link interactions to contacts to maintain relationship history.
Notes Database: title (text), content (text), category (text), created_date (date)Topics Database: name (text), description (text)Link notes to topics for organized knowledge capture.
Habits Database: name (text), description (text), frequency (text), target_value (number)Entries Database: date (date), value (number), notes (text), completed (boolean)Link entries to habits to track progress over time.
Remember: There’s no “right” way to structure your databases. Create what makes sense for your workflow and adjust as you learn what works best for you.