Connecting Databases

Once your Notion workspace is connected, the next step is to link your databases to widgets. This guide explains how to set up database connections and configure field mappings.

Understanding Connections

A connection in Notionarise represents a link between a widget and a Notion database. Each connection has a specific type that defines what kind of data structure is expected.

Connection Types

Notionarise supports several connection types:

  • Habits - For habit tracking databases
  • Tasks - For task and to-do databases
  • Goals - For goal tracking and progress monitoring
  • Events - For calendar and event tracking
  • Custom - For flexible, user-defined schemas

Creating a Connection

Step 1: Create a Widget

  1. Navigate to Dashboard → Widgets
  2. Click Create Widget
  3. Choose your widget type (e.g., Heatmap, Levels, Progress Bar)
  4. Give your widget a name

Step 2: Add a Connection

  1. In the widget editor, click Add Connection
  2. Select the Connection Type that matches your database structure
  3. Choose your Notion Database from the dropdown
  4. Configure field mappings (explained below)

Step 3: Configure Field Mappings

Field mappings tell Notionarise which columns in your Notion database correspond to the required fields for the connection type.

Field Mappings

Field mappings are crucial for widgets to correctly interpret your data. Each connection type has specific required fields.

Habits Connection

Required fields:

  • Habit (Relation) - Links to your habits list
  • Date (Date) - When the habit was completed
  • Status (Optional, Checkbox/Status) - Completion status

Example mapping:

Your Notion Database          →    Notionarise Field
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"Habit Name" (Relation)       →    Habit
"Completed On" (Date)         →    Date  
"Done" (Checkbox)             →    Status

Tasks Connection

Required fields:

  • Task Name (Title) - The task title
  • Due Date (Date) - When the task is due
  • Status (Status/Select) - Task completion status
  • Priority (Optional, Select) - Task priority level

Example mapping:

Your Notion Database          →    Notionarise Field
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"Task" (Title)                →    Task Name
"Due" (Date)                  →    Due Date
"Status" (Status)             →    Status
"Priority" (Select)           →    Priority

Goals Connection

Required fields:

  • Goal (Title) - Goal name
  • Target (Number) - Target value
  • Current (Number) - Current progress
  • Deadline (Optional, Date) - Goal deadline

Field Mapping Interface

The field mapping interface helps you visually connect your database columns:

  1. Select Database - Choose your Notion database first
  2. Auto-detect - Notionarise will try to automatically match fields
  3. Manual Mapping - Adjust any incorrect mappings using dropdowns
  4. Validation - Green checkmarks indicate correct field types

Field Type Compatibility

Each required field expects specific Notion property types:

Required FieldCompatible Notion Types
Title/NameTitle, Text
DateDate
StatusStatus, Select, Checkbox
NumberNumber
RelationRelation
TagsMulti-select, Select

Database Requirements

Habits Database Structure

Recommended setup for a habits tracking database:

Main Database (Habit Tracker):

  • Habit (Relation to Habits List)
  • Date (Date)
  • Completed (Checkbox)
  • Notes (Optional, Text)

Habits List Database:

  • Habit Name (Title)
  • Category (Select)
  • Target Frequency (Select: Daily, Weekly, etc.)
  • Created (Created Time)

Tasks Database Structure

Recommended setup for a tasks database:

  • Task (Title)
  • Status (Status: Not Started, In Progress, Done)
  • Due Date (Date)
  • Priority (Select: High, Medium, Low)
  • Project (Relation, Optional)
  • Tags (Multi-select, Optional)

Multiple Connections

Widgets can use multiple connections to combine data from different sources:

Example: Combined Heatmap

A heatmap widget could display:

  • Habits connection → Shows habit completions
  • Tasks connection → Shows task completions
  • Combined view → Total productivity activity

Setting Up Multiple Connections

  1. Create your first connection as normal
  2. Click Add Another Connection
  3. Choose a different connection type or database
  4. Configure field mappings for the new connection
  5. The widget will merge data from all connections

Testing Connections

After configuring a connection:

  1. Preview Data - Click "Test Connection" to see sample data
  2. Verify Mapping - Ensure fields are populated correctly
  3. Check Dates - Verify date ranges are being read properly
  4. Review Calculations - Confirm totals and stats are accurate

Troubleshooting

Database Not Appearing

If your database doesn't show up in the dropdown:

  • Ensure you've granted Notionarise access in Notion (see Connecting Notion)
  • Refresh the page to reload the database list
  • Check that the database hasn't been deleted or archived

Field Mapping Errors

If you see field mapping validation errors:

  • Type Mismatch - The Notion property type doesn't match the required type
  • Missing Field - A required field hasn't been mapped yet
  • Empty Database - The database has no entries to validate against

No Data Showing

If your widget shows no data:

  • Verify the database has entries within the widget's date range
  • Check that status/checkbox fields have the expected values
  • Ensure related databases (for relations) are also shared with Notionarise
  • Look at the widget's filter settings

Advanced Configuration

Filters

Add filters to limit which database entries are used:

  • Date Range - Only include entries from specific time periods
  • Status Filter - Only count completed items
  • Tag Filter - Filter by specific tags or categories

Data Refresh

Notionarise automatically updates widget data:

  • Real-time Updates - Via Notion webhooks (Premium)
  • Periodic Sync - Every 15-60 minutes (Free tier)
  • Manual Refresh - Click refresh button in widget settings

Cache Management

Widget data is cached for performance:

  • Cache Duration - Data cached for optimal loading speed
  • Invalidation - Automatically cleared when Notion data changes
  • Force Refresh - Clear cache manually in widget settings

Best Practices

Database Organization

  • Consistent Naming - Use clear, descriptive property names
  • Standard Types - Stick to standard property types when possible
  • Complete Data - Ensure all required fields are filled for all entries

Performance Tips

  • Limit Database Size - Large databases (>10,000 entries) may be slower
  • Use Date Filters - Filter to only load necessary date ranges
  • Archive Old Data - Move old entries to separate databases

Maintenance

  • Regular Audits - Periodically check that mappings are still correct
  • Update Connections - If you change database structure, update mappings
  • Monitor Errors - Check widget error logs for connection issues

Next Steps

You're now ready to:

  • Create your first widget with connected databases
  • Customize widget appearance and settings
  • Embed widgets in your Notion pages
  • Explore advanced widget features

Need help? Check our FAQ or contact support for personalized assistance.