Canny verdict · build Solution request

Bulk task editor and mover for Sunsama with public API

Built for Sunsama users managing large task portfolios daily.

“Sunsama API. Expose an API to allow custom integrations with Sunsama. 111. 880. Batch/bulk edit, Select Multiple tasks to move or edit. Sometimes I want to ... …”

The receipts — real demand

“Sunsama API. Expose an API to allow custom integrations with Sunsama. 111. 880. Batch/bulk edit, Select Multiple tasks to move or edit. Sometimes I want to ... Read more”

Full dossier

Unlock the full dossier — free

Every corroborating quote, the source receipts, and the community echo. One email, no payment.

6.2 / 10 · demand score
Pain 7
Willingness to pay 4
Feasibility 7
Specificity 8
Audience 8
Competition 6

Why this is a gap

Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.

The market

Sunsama users managing large daily task portfolios need to bulk-edit and move multiple tasks at once, and hook into Sunsama via public API for custom workflows. No search volume provided; the feature request on Sunsama's own roadmap with 111 votes indicates clear demand.

Competition & the opening

Wedge play crowded — win on a narrow angle Moat 3/10 · thin angle Market 3/10 · small niche
Crowded market · 6/10 vs Sunsama (native bulk edit — requested on their own roadmap, not yet shipped)Zapier (automation layer over Sunsama via integrations)Make (formerly Integromat — Sunsama automation workflows)n8n (open-source workflow automation with Sunsama nodes)Notion + custom scripts (users migrate tasks in bulk via database operations)Custom scripts via Sunsama public API (DIY solution already available to developers)

Sunsama's native bulk edit is requested but not shipped; Zapier, Make, and n8n offer automation over Sunsama, and custom scripts via the Sunsama public API already exist. The gap: no one-click bulk mover for Sunsama that lets users select tasks on the board and move them to a date or project without leaving the UI; integrations like Zapier require multi-step config.

What's hard to build

Sunsama's public API is minimal and not officially documented for third-party bulk operations; Sunsama treats UI state (board filters, selection) as ephemeral, so a bulk editor must rebuild selection logic on the client. The small user base (vs. Asana, Monday) means low volume to justify deep API partnerships.

Why now

Sunsama's bulk edit is still on roadmap; Zapier/Make add cost and latency; a native Sunsama public API + lightweight UI would eliminate friction for power users.

How you'd monetize

Free (consume Sunsama API and monetize on Zapier/Make marketplaces) or $5–10/mo