The transcript vault

Copies completed transcripts into your team's document store, one document per session, named so they are findable six months later.

Workflow 2 of 12Research opsSeptember 30, 2026

Get the workflow

Enter your details and the prompt appears here, ready to copy.

How do I get interview transcripts into Google Drive or Notion automatically?

Connect your AI tool to Great Question and to your document store, then run a weekly prompt that lists the week's repository sessions, checks each transcript has finished processing, and writes one document per session named after the study, participant and date. The readiness check is the important part: it stops half-finished transcripts landing in the folder unnoticed.

Who runs it
Research ops.
Where you sign off · Writes outside GQ
Nothing inside Great Question. The agent writes into your document store, not into your research data.
Schedule it · Weekly
Yes, weekly. The readiness check matters. Without it you end up with half-written transcripts in the vault and no way to tell which ones.

How to run it in Claude, ChatGPT, Cursor or Copilot

The prompt is the same in every tool. What changes is where you connect Great Question and where you paste it.

Run it in Claude

  1. 1

    Connect Great Question to Claude

    In Claude Desktop, open Settings → Connectors → Add custom connector. Name it Great Question, paste https://greatquestion.co/api/mcp/v1, then Save and Connect and sign in with your Great Question account. Restart Claude so the tools load.

  2. 2

    Connect the other end

    This workflow also needs your document store (Google Drive, Notion or SharePoint) connected in Claude, through that tool's own connector.

  3. 3

    Paste the prompt

    Start a new chat and paste the prompt. Claude asks before it uses each Great Question tool; allow the read tools, and read anything it proposes to write before you allow it.

Your admin has to switch the MCP on in Great Question first. The MCP guide covers every tool, the security model and a team rollout.

How to run it on a schedule

  1. 1

    Give the agent its own token

    A scheduled run has nobody there to sign in, so it uses an agent API token instead of OAuth. The token sees exactly what its user can see, and you can revoke it from your Great Question account.

  2. 2

    Run the prompt headless

    Claude Code runs a prompt without a chat window with claude -p "<the prompt>", and Codex with codex exec "<the prompt>". Either works once the Great Question MCP is added to it.

  3. 3

    Put it on a weekly timer

    Schedule that command with whatever your team already uses: cron, a CI job, or your AI tool's own scheduled tasks. Check the first few runs by hand before you stop looking.

The tools it calls

Named so you can see exactly what the agent touches before you let it near anything.

  • list_repo_sessions
  • get_repo_session
  • get_repo_session_transcript
  • get_study

What we never automate

Four rules sit under every workflow here, and they matter more than the workflows.

  • Nothing reaches a participant without a person

    No workflow sends an invitation, an email or a reminder. The MCP can do those things. They are left out on purpose, because a scheduled job that contacts your customers is a different category of risk from one that reads a transcript.

  • Nothing launches a study without a person

    An agent can build the screener and draft the messages. Someone still presses go.

  • Nothing reaches a stakeholder unchecked

    The synthesis workflows hand you quotes with links attached so you can check them in one click. Use the click. A misattributed quote in a board deck costs more than the hour it saved.

  • Nothing sees more than the person who connected it

    Permissions follow the individual, so an agent connected by a PM reaches exactly what that PM reaches. Your admin decides whether it is available at all.

Questions

Why not export transcripts by hand?

For a few sessions, do. The workflow earns its keep when a team runs a dozen sessions a week and the transcripts need to be readable by people who will never log in to the research platform.

Does it copy participants' personal data?

It copies what the transcript contains. If your admin has set the MCP to hide PII, names and emails stay hidden in what the agent reads. Check where the documents land and who can open that folder before you schedule it.

Which document stores does it work with?

Any your AI tool has a connector for, such as Google Drive, Notion or SharePoint. The Great Question side is the same in every case.

Related reading