Rocket supports three productivity integrations. Each covers a different part of your team’s workflow. Most teams connect all three, but this guide helps you prioritize.
Quick answer
- Specs, wikis, and team knowledge - Connect Notion.
- Spreadsheets, docs, and calendars - Connect Google Workspace.
- Tickets, projects, and bug reports - Connect Linear.
Comparison table
| Capability | Google Workspace | Notion | Linear |
|---|---|---|---|
| Best for | Structured data, specs, calendars | Team knowledge, PRDs, content | Issue tracking, sprints, project management |
| What Rocket reads | Docs, Sheets, Calendar events | Pages, databases, wikis, templates | Tickets, projects, acceptance criteria |
| What Rocket writes back | Docs (copy, reports), Sheets (data, SEO metadata) | Pages (briefs, docs, copy banks, handoffs) | Issues (follow-ups, QA tickets, client changes) |
| Content types | Text, tabular data, calendar events | Rich text, databases, relations, embeds | Issues, projects, documents, labels |
| Real-time data | Yes (Sheets, Calendar) | Yes (databases, pages) | Yes (issues, projects) |
| Write-back creates | New documents and spreadsheets | New pages with structured content | New issues and project boards |
| Connection method | OAuth | OAuth | OAuth |
| Pricing | Free (personal), paid (Workspace) | Free tier available | Free tier available |
Choosing by use case
Specs and PRDs your team already wrote
Connect Notion or Google Docs. If your PRDs live in Notion, connect Notion. If they live in Google Docs, connect Google Workspace. Either way, Rocket reads the full spec and builds from it directly.Build from tickets and acceptance criteria
Connect Linear. Point Rocket at a ticket and it reads the title, description, and acceptance criteria, then generates the implementation. Your sprint board becomes your build queue.Data in spreadsheets that should drive your app
Connect Google Workspace. Rocket reads columns, rows, and data types from your Sheets and generates apps that reflect your real data structure. Pricing matrices, product catalogs, team rosters, and campaign trackers all work.Write documentation after building
Connect Notion. Notion is the best destination for generated docs: project documentation, campaign briefs, content banks, client handoff docs, sales one-pagers, and competitive positioning docs.Follow-up tickets created automatically
Connect Linear. After building, Rocket populates your board with QA tickets, enhancement requests, and client change requests. Each issue gets a description, priority, and acceptance criteria.Marketing team reviewing generated copy
Connect Notion or Google Workspace. Push generated copy to a Notion page or Google Doc. Your marketing team reviews and approves in the tool they already use.Connect everything for a complete loop
Connect all three. Specs from Notion or Docs inform the build. Rocket generates the app. Documentation flows back to Notion, follow-up tickets flow to Linear, and data exports flow to Sheets.How it works
These integrations work in both directions and happen during and after generation, not as a separate export step.| Direction | What happens | Example |
|---|---|---|
| Rocket reads | Your existing content informs the build | Spec in Notion becomes a working app |
| Rocket writes back | Generated output flows back to your tools | Generated copy pushed to Notion for review |
| Full loop | Both directions in one workflow | Read ticket from Linear, build feature, create QA tickets back in Linear |
Browse productivity integrations
Google Workspace
Read from Docs, Sheets, and Calendar. Write copy and data back.
Notion
Read pages, databases, and wikis. Write docs, briefs, and copy banks back.
Linear
Read tickets and projects. Write follow-up issues and updates back.