Rocket Blogs
Engineering

The work is only as good as the thinking before it.
You already know what you're trying to figure out. Type it. Rocket handles everything after that.
Rocket Blogs
Engineering

You already know what you're trying to figure out. Type it. Rocket handles everything after that.
Table of contents
In this Guide: Learn how Rocket Connectors let you build apps on top of the tools you already trust — Notion, Airtable, Linear, Mailchimp, Mixpanel, Cal.com, Calendly, Stripe, and 20+ more — all flowing directly into code generation, not bolted on after.
25+ Connectors Flowing INTO Generation. Not After. During.
"The app looks right. The layout is clean. Everything seems in place. Then you check the code... and discover none of it is actually connected to your real-world services."
Result:
After just a few integrations, all time saved on code generation gets lost to manual wiring and setup.
| Component | How It Looks | Why It Fails |
|---|---|---|
| Pricing card | Static layout | Misses Stripe price objects, proration logic |
| Signup form | Generic state handler | Lacks Supabase session/auth handling |
| Analytics snippet | <script> placeholder | Doesn't follow Mixpanel event taxonomy |
| Email capture form | Basic onSubmit handler | Not integrated with Mailchimp lists/fields/opt-in |
| Booking widget | Placeholder calendar | No connection to Cal.com or Calendly availability |
| Content section | Hardcoded text | Not synced with Strapi or Directus CMS |
Integration Gap: The code you get is not just incomplete — it can actively work against your integration needs.
"The best products aren't built in isolation. They're built on workflows that already work."

This is the largest layer and the one that matters most to your product.
What this means in practice:
How it works:
What this means in practice:
Supabase handles the foundational concerns:
Every generated Rocket app leverages your actual Supabase project and config for core functions. This is the infrastructure layer that the connectors and routed services build on top of.
Most builders hard-code API keys or secrets, creating maintenance issues and security holes. Rocket avoids this completely.
Dependency Layer Overview:
| Connectors | Services via Supabase | Supabase Infrastructure |
|---|---|---|
| Notion, Mailchimp, Mixpanel, Cal.com, Strapi, etc. | Stripe, Twilio, Resend | Auth / Database / Realtime |
| Authenticate, fully decoupled | Require Supabase for logic & security | Foundation for all layers |
| Integration Type | Rocket Layer | Post-Build Integration | Generation-Time Integration |
|---|---|---|---|
| Workspace (Notion, Linear) | Connector | Manual API setup, field mapping | Workspace data mapped at generation |
| Marketing (Mailchimp, Brevo) | Connector | Redo forms for each list/field | List/field connections already present |
| Analytics (Mixpanel, GA) | Connector | Hand-write event tracking per component | Events mapped in generated code |
| Scheduling (Cal.com, Calendly) |
Bottom line: Generation-time integration fundamentally changes how your application is structured — so the code you receive is actually ready for use in production, right away.
Early Phase:
Turning Point:
"Treating Stripe as 'just a connector' did not match real-world usage. Webhook management, secure checkout, and subscription logic all demanded a robust server foundation. Supabase delivered that. Meanwhile, tools like Notion, Mailchimp, and Cal.com needed direct workspace-level access — no server layer required."
Current Model:

Comparison: Post-build integration means hours of manual wiring. Generation-time integration means production-ready output from the first preview.
Step-by-Step Walkthrough
Integration Context Resolution
Component Structuring
Auth and Data Logic
Ready-to-Use Output
"The real integration gap — the hours lost connecting generated code to your stack — is the main reason developers drop generated projects. Rocket Connectors close that gap."
| Connector |
| Manual calendar widget embed, no data flow |
| Availability and booking flow wired |
| CMS (Strapi, Directus) | Connector | Manual content API setup, field mapping | Content types and fields synced |
| Forms (Typeform) | Connector | Embed iframe or manual API integration | Form data flows into app components |
| AI Services (OpenAI, etc.) | Connector | Configure each prompt/model manually | Integrated to the right APIs |
| Payment (Stripe, PayPal) | Via Supabase | Wire checkout, subscription manually | Full stack is production-ready |
| SMS (Twilio) | Via Supabase | Manual flow configuration | Fully set up via platform |
| Email (Resend) | Via Supabase | Manual templates and triggers | Secure, RLS-compliant emails |
| Auth (Supabase) | Infrastructure | Manual session rewrite, RLS setup | Auth flow correct out-of-the-box |
| Database (Supabase) | Infrastructure | Replace mock data, remap relationships | Relationships correctly mapped |
| Realtime (Supabase) | Infrastructure | Set up websockets, channels | Subscriptions already present |