This connector is only available for Next.js TypeScript web build tasks.
Confluence is a workspace-level connector. Connect it once from Settings and it is available across all tasks.
What you can do
Build from specs
Link a product spec, PRD, or technical design doc in Rocket. Rocket reads the requirements and builds exactly what was specced.
Use architecture docs as context
Feed your team’s API reference, system design, and architecture docs into Rocket so generated code matches your actual patterns.
Sync knowledge base content
Pull Confluence space pages into your app. Turn internal wikis into searchable help centers or onboarding tools.
Align with team standards
Sprint notes, ADRs, and runbooks become context so every output reflects your team’s real decisions and conventions.
Before you connect
Confluence uses OAuth via Atlassian, so no API key is required. You authorize Rocket through Atlassian’s login screen, then select your cloud instance and Confluence space inside Rocket.Connect Confluence
- Web Browser
- Mobile App
You can connect from three places. All do the same thing.Option 1: From chatType a prompt that references Confluence - for example, 
Connect our Confluence space and use the API spec doc when building this feature. Rocket detects the intent and shows a Connect button inline. Click it to open the authorization flow.... button in the preview toolbar, then select Connectors.Connect from workspace Settings
Connect once from Settings and it is available across all tasks.
Disconnect a service
Disconnect or switch spaces from workspace Settings.
Example prompts
Replace[CONFLUENCE_URL] with the link to your Confluence page or space.
| Use case | Prompt |
|---|---|
| Build from spec | Read our product spec at [CONFLUENCE_URL] and build the described feature with all data models and user flows. |
| Use API reference as context | Use the API reference in our Confluence space when generating the integration layer for this service. |
| Architecture-aligned code | Generate the authentication module following the patterns in our architecture doc at [CONFLUENCE_URL]. |
| Help center from wiki | Turn the FAQ page at [CONFLUENCE_URL] into a searchable help center with category filters. |
| Onboarding from runbook | Build an onboarding checklist app using the steps from our new-hire runbook at [CONFLUENCE_URL]. |
| Standards enforcement | Generate the database schema following the conventions documented in our Confluence data model guide at [CONFLUENCE_URL]. |
Tips
- Paste Confluence page URLs directly in chat. Linking to a specific page gives Rocket focused context. Vague references may pull less relevant content from across the space.
- Connect the most relevant space. If your team has multiple Confluence spaces, connect the one that contains the specs and docs closest to what you are building.
- Specs produce the most accurate code. The more structured and detailed your Confluence doc, the more precisely Rocket can match your requirements.
- To switch spaces, reconnect. You can only connect one Confluence space at a time per workspace. Disconnect and reconnect to switch to a different space.
- Confluence context is RAG-based. Rocket retrieves the most relevant content from your space at generation time. It does not load the entire space into every prompt.
What’s next?
Notion
Prefer Notion for your docs? Connect Notion as an alternative source of specs and wikis.
Linear
Build directly from Linear tickets alongside your Confluence specs.
Supabase
Store app data with Supabase while Confluence provides the documentation context.
GitHub
Push generated code to GitHub to keep it in sync with your team’s workflow.