> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Connected services
> Link Notion and Google Drive to your Rocket.new project for live context.
export const LlmsDirective = () =>
For the complete documentation index, see llms.txt.
For a lightweight markdown version of this page, append .md to the URL.
;
Connected services bring live external content into your project. Link Notion pages or Google Drive files and Rocket can read their content to inform every Solve and Build task without you copying, pasting, or re-uploading anything.
Connected services are different from [Build connectors](/build/connectors/overview). Build connectors add functionality to your apps (payments, databases, email). Connected services provide **context**: they give Rocket access to external documents and data to inform your work.
## Supported services
Google Docs and Google Sheets.
Notion pages (`.md`) including product specs, meeting notes, and wikis.
## Connect a service
Click **Projects** in the sidebar, then click your project.
Click the **Context** tab on the right panel. You'll see connectors for My Device, Google Drive, and Notion.
Click the service you want to connect. A modal appears. Paste the URL of the file or page, then click **Submit**.
The connected item appears in the **Files** section of the Context tab and is immediately available to all tasks in the project.
Connected services provide read-only access. Rocket reads your content but never writes back to or modifies your external documents.
## How connected context helps
Once connected, Rocket uses that content automatically when it's relevant.
* A Notion product spec means your Build task produces an app that matches the brief from the first generation.
* A Notion brand doc means Solve and Build tasks reflect your actual positioning without you re-describing it.
* A Google Drive file with pricing data means a Solve task can analyze real numbers rather than placeholders.
## Manage connections
To remove a connected source, open the **Context** tab in your project.
* **Remove:** hover over the item in the Files section and click the **X** button that appears.
* **Add more:** click the service connector again and paste a new URL.
Removing a connected source removes its content from the project context. Existing task outputs are not affected, but future tasks won't have access to that content.
## What's next?
Upload files directly to your project for additional context.
See how connected services fit into the broader context flow.
Add functional integrations like Stripe, Supabase, and analytics to Build tasks.