
Task Board
Kanban board build in react with drop-in Inbox and Preference Centre.
Try it out | GitHub code repository
Try it out | GitHub code repository
Follow these steps in order. You’ll set up SuprSend, create dashboard assets, then run the prompts so your AI assistant can build the app. By the end you’ll have a working TaskBoard with OTP login, Kanban board, in-app inbox, and notification preferences.
Step 1: Setup SuprSend MCP Server
Start by setting up SuprSend MCP Server in your AI coding assistant. Once MCP Server is setup, you can just copy and paste the prompts below to build the entire application step by step.Step 2: Get Your SuprSend Keys
Get workspace key and secret for the backend, and a public key for the frontend. Add them after Prompt 1 creates the project.- Open SuprSend dashboard → Developers → API Keys.
- Copy workspace key and workspace secret (backend).
- Copy one Public Key (frontend).
.env and the public key in client .env. Don’t commit these files.
Step 3: Setup in the SuprSend dashboard
Create these in the SuprSend dashboard (same account as Step 2). Do this before or after Prompt 1.| Asset | What you create |
|---|---|
| Preference categories | 1 category “Task Management” with 3 sub-categories |
| Templates | 4 templates (OTP, task-created, task-status-changed, task_deleted) |
| Workflows | 4 workflows (otp_verification, task_created, task_status_changed, task_deleted) |
3a. Create notification categories
Set up your notification categories with root Task Management and sub-categories. Publish the structure.
3b. Create templates
In Templates, create these four. Use placeholders (e.g. user name, code, task title) in the body. Publish each.| Template name | Where it’s sent | What it’s for |
|---|---|---|
| otp_verification | Email (optionally SMS) | 6-digit login code |
| task-created | Email + In-app | New task created |
| task-status-changed | Email + In-app | Task moved to another column |
| task_deleted | Email + In-app | Task deleted |
3c. Create workflows
In Workflows, create these four. Add Email and In-App nodes with the templates from 3b. Commit the workflows.| Slug | Trigger | Template |
|---|---|---|
task_created | API | task-created |
otp_verification | API | otp_verification |
task_status_changed | Event | task-status-changed |
task_deleted | API | task_deleted |