On the afternoon of November 20 I opened a Rork project and the sidebar no longer said "Connectors." It said "Plugins." For a second my hands stopped: had my GitHub connection just been dropped?
It hadn't. Only the name had changed; everything I'd connected was still there. What did change is that Google Docs and Google Drive can now be connected, and that is going to shift how I start a new screen.
The thing I'd like to say first: Plugins are not features that go into your app. They're places Rork itself can read from while it works. Keeping that straight removes most of the decisions before you connect anything.
What changed on November 19
Rork's changelog entry for November 19 says, in short:
- Connectors are now called Plugins, in the same places: the sidebar and the chat's "+" menu
- Anything you'd already connected stays connected
- The directory opens with popular services such as Gmail, Notion, Supabase, GitHub and RevenueCat
- Each card shows which account it's connected as
- A card tells you when a service needs a new sign-in or its tools have changed
- Seven new plugins for everyone: Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Slack and Zoom
- The side chat (the "?" button in the chat header) is gone; ask questions in the main chat
For the seven new ones, the suggested use is: connect in Plugins, then ask Rork in chat to read from it or make changes. The reader is Rork, not the app you're building.
Reading Sheets from inside your app is a different road
This is where I nearly got confused myself. "I want my budgeting app to export totals to Google Sheets" and "I connected Sheets in Plugins" are two unrelated jobs.
| What you want | Which road | Official source |
|---|---|---|
| Let Rork read your spec while it builds | Connect Google Docs / Drive in Plugins | Changelog, Nov 19 |
| Use Sheets or your own API from the finished app | Ask for the integration in chat and provide an API key | FAQ: Integrations |
| Add an outside tool to Rork's own work | Register it in Settings → MCP, then enable it from the + menu | Same FAQ |
The FAQ says that for Sheets or Notion you ask Rork to integrate, it asks for your API key, and it may need the API docs to get it right. The Google account you connected in Plugins does not travel to your users' phones.
On rename day, look at two things on each card
Open Plugins and go through the connected cards one by one. It takes a few minutes.
- The connected account. This is new on the cards. If, like me as an indie developer, you keep a work Google account separate from your everyday one, this is where a mix-up shows.
- Any notice about signing in again or changed tools. If a card says so, reconnect today rather than finding out mid-build.
I settled on a single work account for this. All I want Rork to read is the spec; there's no reason to show it my inbox or calendar.
How I hand Rork a spec now
I used to paste long write-ups of each screen straight into chat. By the third request I'd lose track of which version I had pasted, and once I sent the same instruction twice. It didn't go well.
The order I use now:
- Write one spec in Google Docs with fixed headings: screens, data, decided, not decided yet.
- Connect Google Docs in Plugins.
- Before any building, ask Rork to read it and only return a summary.
- Compare that summary with my spec, and when they disagree, fix the spec.
- Once they match, ask for one screen.
Step 3 uses nearly the same wording every time:
Please read the Google Doc "Budget app spec v3".
Don't write any code yet.
Reply with these four things as bullet points:
1. The list of screens (name, and what the user can do there)
2. The data to store and its type (amounts as whole yen, and so on)
3. The commitments under the "Decided" heading
4. The items under "Not decided yet"
If the spec doesn't say something, write "not stated" instead of guessing.The two lines doing the work are "Don't write any code yet" and the last one. If guesses slip into the summary, they slip straight into the first screen. One read-back round catches "that's not what my spec said" before it becomes code.
Where to put commitments that are expensive to change later, like money and dates, is something I wrote about in three lines in the first prompt of a budgeting app.
Rork reads one spec; I correct the spec, not the summary. Since I drew that line, what I paste into chat has shrunk to almost nothing.
I'm leaving "make changes" aside for now
The changelog also says you can ask Rork to make changes in a connected service. It sounds handy, but for the spec I only let it read.
The reason is simple: the spec is where I write down my own decisions. The AI summarizes and I edit — flip that direction and I can't trace later which choices were mine. If I try edits at all, it'll be on a duplicate of the doc.
With the side chat gone, questions like "what does this code do?" now sit in the main chat too. If requests and questions start to blur, I've found it helps to open a question with "Question only, please don't change anything."
When the preview doesn't behave and you're tempted to repeat the same request, I listed what to check in opening the Logs panel when a list is empty. And before changing plans, see checking that exported code rebuilds outside Rork.
What to do next
Open Plugins and check the account shown on each connected card. Then write a one-page spec for the app you're working on in Google Docs, and start with a "summary only" request. That single round trip is where I'm starting my next screen, too.