📖 Browse Documentation

Guides

Reference

🛟 Help Center
🔒 Trust Center

Task Database Configuration

Complete reference for configuring task databases - Notion databases with interactive Discord features.

What is a Task Database?

A task database is a Notion database with a Status property that's explicitly connected on the Tasks page. This enables Discord commands and quick actions.

New to task databases? See the task management guide for step-by-step setup instructions.

Configuration Options

1. Discord Command Name (Required)

Purpose: Customize the slash command for creating tasks

Rules:

  • Lowercase letters, numbers, and hyphens only
  • 1-32 characters
  • Cannot start or end with hyphen

Examples:

  • bug → Users type /bug to create bug reports
  • feature → Users type /feature for feature requests
  • task → Users type /task for general tasks

Multiple databases with same command:

📝 Shared Commands
Multiple databases can use the same command name. Discord shows a dropdown to select the database. Useful for separating task types (e.g., /task for Personal and Work databases).

2. Status Property Mapping (Required)

Purpose: Maps to Notion Status property for status change buttons

Requirements:

  • Must be type "status" or "select"
  • Used for status change buttons in Discord

Configuration:

  • Select from dropdown of available Status/Select properties
  • Only shown if database has Status property

3. Assignee Property Mapping (Optional)

Purpose: Enables "Assign to me" button

Requirements:

  • Must be type "people"
  • Used for "Assign to me" quick action button

Configuration:

  • Select from dropdown of People properties
  • Leave empty to disable "Assign to me" button

If not configured:

  • No "Assign to me" button on notifications or task creation confirmations

4. Modal Fields (Optional, up to 5)

Purpose: Customize the task creation form in Discord

Supported property types:

Type Description Examples
Text Single-line or multi-line text Title, Description, Notes, URL, Email, Phone
Number Numeric input Priority score, Story points, Hours
Date Date picker Due date, Start date, Deadline
Checkbox Yes/no toggle Urgent, Public, Reviewed
Status Dropdown with database status options Status, Phase, Stage
Select Dropdown with single choice Priority, Category, Type
Multi-select Dropdown with multiple choices Tags, Labels, Teams
People Dropdown with linked Notion users Assignee, Reporter, Reviewer
Relation Dropdown with related database pages Epic, Project, Parent task

Field configuration:

  • Up to 5 fields per database
  • Mark as required or optional
  • Reorder with arrow buttons
  • Title is always required (automatic)

Dynamic options:

🔄 Live Options
Status, Select, Multi-select, People, and Relation dropdowns fetch live data from Notion every time the modal opens. Options are never cached and always reflect current database state.

Default behavior (when first connected):

Modal is autofilled with up to 5 fields based on database properties, sorted by usefulness:

  1. Title (always included, required)
  2. Content/Description (rich text property)
  3. Relations (if present)
  4. Text properties (if present)
  5. Select/Multi-select (if present)

You can customize by removing defaults or adding different properties.

5. Quick Action Buttons (Optional)

Configure which buttons appear on task creation confirmation cards. Options: status change buttons and/or "Assign to me" button (requires mapped Assignee property).

Note: Notification rule buttons are configured separately on the Notifications page. See Quick Actions Guide for complete setup instructions.

Disconnecting Databases

You can remove task databases even if they're used in active notification rules. You'll see a warning showing the impact before confirming removal.

⚠️ Impact of Removal

This will remove:

  • Custom command (e.g., /bug, /feature) - stops working immediately
  • Tasks from /my-tasks command
  • Quick action buttons on new notifications from this database

Existing notification rules continue posting but without interactive buttons.

Task vs Page Database

Feature Task Database Page Database
Prerequisites Has Status property + connected on Tasks page Any database (no Status)
Discord commands ✅ Custom command (e.g., /bug), /my-tasks ❌ Not available
Quick actions ✅ Status buttons, "Assign to me" (configurable per rule) ❌ Read-only
Notifications ✅ With configurable buttons ✅ Read-only
Notification events ✅ Task Created, Task Updated ✅ Page Created, Page Updated
Configuration Command name, Status/Assignee mapping, fields, quick action buttons None
💬 Need Help?

See Commands Not Working troubleshooting guide