Open connector marketplace for Make and n8n where developers publish, monetize, and maintain custom integrations under a revenue-share model, with built-in versioning and a community trust score so bu
The long tail of niche SaaS integrations will never be built by Make or Zapier but a credentialed marketplace could turn that gap into a developer income stream and a platform moat
Built for Make.com users and developers who need integrations not yet supported natively and want to build or use community-created modules..
Solve the trust and maintenance problem of unofficial connectors by requiring automated test suites and escrow-based maintenance commitments before a module is listed as production-ready
“I recently joined Make and have experience with other automation tools, along with watching many hours of Make automation tutorials. I wanted to create an autom…”
The receipts — real demand
“I recently joined Make and have experience with other automation tools, along with watching many hours of Make automation tutorials. I wanted to create an automation but found that the integration I need is paid. I want to develop my own version to provide an alternative for others.”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
demand score 6.1 — the receipts are below
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Make.com users hitting native integration limits need a way to plug unsupported services into workflows. No search data exists, suggesting this is a known-but-small pain point within Make's existing user base rather than a category with independent demand signals.
Competition & the opening
Make's own native module library and community templates already cover common use cases. The opening is in serving power users who need non-native integrations faster than Make's roadmap allows, but Make could close this gap by expanding native modules.
What's hard to build
Building a stable, discoverable marketplace requires Make API stability, vetting contributor code for security and reliability, and handling versioning/breakage when Make updates core functionality. Unknown feasibility likely reflects uncertainty about Make's API maturity and openness to third-party module distribution.
Why now
Make.com restricts integrations to approved partners; community-built modules can solve long-tail connector gaps.
How you'd monetize
$0.50-2 per module execution or marketplace revenue share