Colorful sticky notes arranged on a bright window beside a desk

Claude + Google Forms: What the Integration Can (and Can't) Do in 2026

No — there’s no Google Forms connector for Claude, and here’s the part that surprises people: Claude’s Google Drive connector can’t read Forms either. The official Google Drive connector is read-only and handles Docs, Sheets, Slides, PDFs, images, and Office files — but it does not render Google Forms files or expose form responses. Google hasn’t shipped a Forms MCP server. The honest workaround is a Forms feature, not a Claude one: link your form’s responses to a Google Sheet, and Claude’s Drive connector can read and analyze that Sheet on demand. Real automation — reacting when a response arrives — lives in the Google Forms API or Apps Script, not in Claude.

Here’s what actually works, what the API makes possible, where the limits bite, and what to use if you want form responses handled on their own.


What Claude can actually do with Google Forms today

  • Analyze responses via the linked Sheet. In Forms, link responses to a Sheet (Responses tab → Sheets icon). Claude’s Drive connector reads that Sheet, so “summarize this week’s survey responses — themes, sentiment, top verbatims” works well. This is the whole supported story, and it’s genuinely useful.
  • Draft forms as text. Claude will happily write your question set, answer options, and branching logic as a spec — you paste it into Forms by hand. (Google’s own Gemini “Help me create a form” builds forms from a prompt in-product, on eligible Workspace plans — expanded to 21 more languages in April 2026.)
  • Not: open a Form file, read its structure, see responses without the Sheet link, or notice a new submission. The Drive connector skips Forms files entirely, and everything is conversation-initiated — you ask, Claude reads.

Where the real automation lives: the Forms API and Apps Script

Google Forms has a real API — it’s just not wired to Claude:

  • Forms API v1 (forms.googleapis.com, OAuth 2.0): read and update form structure (forms.get, batchUpdate), and read responses with forms.responses.list, including timestamp filters for “everything since I last checked.”
  • Push notifications: register a forms.watches watch with EventType.RESPONSES targeting a Cloud Pub/Sub topic — you’re notified within minutes of new submissions. The catch: watches expire every 7 days and must be renewed via watches.renew, so this is a maintained service, not a set-and-forget hook.
  • Apps Script: an installable onFormSubmit trigger fires server-side on every submission — the simplest real-time hook, no Pub/Sub plumbing. It can even call the Anthropic API via UrlFetchApp to classify or summarize a response, if you want to write and maintain that code.

All three are developer routes. None of them turn into “Claude handles my form responses” without you building the pipeline.


The limits that actually matter

  • The Drive connector blind spot. Claude reads your Docs and Sheets but not your Forms — no structure, no responses, unless you route responses into a Sheet first.
  • No triggers, no monitoring. Even with the Sheet linked, Claude only analyzes when you ask in a chat you started. There’s no “when a response arrives, triage it.” The Forms API’s watches and Apps Script triggers exist precisely because someone has to catch that event — and Claude can’t.
  • Read-only, conversation-only. Claude can tell you the intake form got three urgent submissions; it can’t create the CRM contact, schedule the kickoff, or send the welcome email.
  • Laptop-bound for anything scheduled. The nearest thing to autopilot is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events.

So Claude is good for “read the responses Sheet and tell me what it says” — and not built for “handle each response as it lands.”


If you want Google Forms work that runs on its own: Carly

Forms are a front door: intake requests, RSVPs, survey answers, support asks. The value is in what happens right after someone hits submit — which is exactly when nobody’s in a chat.

That’s where Carly fits. Carly is an AI executive assistant built to act on triggers. Google Forms connects to Carly via your own API credentials — paste them on carlyassistant.com/integrations — and Carly works the responses as they land:

  • When a form response arrives, Carly triages it — categorizes the request, drafts a reply, and routes it to the right teammate.
  • When a client-intake form is submitted, Carly creates the CRM contact, schedules the kickoff, and drafts the welcome email from the answers.
  • Friday at 4pm, the week’s survey responses become a digest — themes, sentiment, top verbatims — in the team’s inbox.
  • Event RSVPs roll into a live headcount, with dietary and accessibility answers flagged for the catering email.
  • No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
  • Actually sends — drafts and sends email across Gmail and Outlook, updates your CRM, manages tasks.
  • Connects to anything — 200+ native integrations across 40+ categories (see integrations), plus any tool with an API via your own key.

AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.


Claude’s Google Forms options vs Carly

Claude (Drive connector + linked Sheet)Carly
Read form responsesOnly via the linked Sheet, on requestYes, as they arrive
Read/edit form structureNoVia the Forms API
Reacts when a response is submittedNoYes
Creates contacts / schedules follow-ups from answersNoYes
Weekly response digest, unpromptedNoYes, on a schedule
Works while your laptop is closedNoYes (cloud)
Sends replies and welcome emailsNo (Gmail draft-only)Yes (Gmail + Outlook)
PricingPro $20 / Max $100–$200AI agents from $35/mo

Claude is a sharp analyst for a responses Sheet you hand it. Carly is a teammate that works each submission the moment it lands.


Frequently Asked Questions

Does Claude work with Google Forms?

Not directly. There’s no Google Forms connector, and Claude’s official Google Drive connector — which reads Docs, Sheets, Slides, and PDFs — does not read Google Forms files or responses. The supported path: link your form’s responses to a Google Sheet, which Claude’s Drive connector can read and analyze in a chat you start.

Can Claude read my Google Forms responses?

Only through the linked responses Sheet. Turn on the Sheets link in your form’s Responses tab, and Claude can summarize, categorize, and analyze the data on request. Without the Sheet link, Claude has no access to responses at all.

Can Claude do something automatically when someone submits my form?

No. Claude has no event triggers — the real-time hooks are the Forms API’s forms.watches push notifications (Pub/Sub, renewed every 7 days) or an Apps Script onFormSubmit trigger, both developer builds. For no-code triage, CRM entry, and follow-up email on every submission, a trigger-based agent like Carly does it in the cloud, 24/7.

Can Claude create a Google Form?

Not in Forms itself — Claude can draft the questions and logic as text for you to paste in. Programmatic creation runs through the Forms API’s batchUpdate, and Google’s own Gemini “Help me create a form” builds forms from a prompt inside Forms on eligible Workspace plans.


More: Claude + Google Drive · Claude + Google Sheets · Claude + Typeform · Claude + Jotform · Claude + Tally · Can Claude send emails

Ready to automate your busywork?

Carly schedules, researches, and briefs you—so you can focus on what matters.

See what people say

"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.

Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.

On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."

Gus Ibrahim, Founder & Director, IHR