The transcript vault
Copies completed transcripts into your team's document store, one document per session, named so they are findable six months later.
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
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
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
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.
Run it in ChatGPT
- 1
Connect Great Question to ChatGPT
In the ChatGPT or Codex desktop app, go to Settings → Plugins → MCPs → Add server. Name it Great Question, choose Streamable HTTP, paste https://greatquestion.co/api/mcp/v1, save, then authenticate.
- 2
Connect the other end
This workflow also needs your document store (Google Drive, Notion or SharePoint) connected in ChatGPT, through that tool's own connector.
- 3
Paste the prompt
Open a new chat with the Great Question server switched on and paste the prompt. If ChatGPT answers without calling a tool, say “use the Great Question tools” and it will.
Run it in Cursor
- 1
Connect Great Question to Cursor
Open Cursor Settings (Cmd/Ctrl + Shift + J) → MCP → New MCP Server, and add a server named great-question with the url https://greatquestion.co/api/mcp/v1 to mcp.json. Save, click Connect, and sign in.
- 2
Connect the other end
This workflow also needs your document store (Google Drive, Notion or SharePoint) connected in Cursor, through that tool's own connector.
- 3
Paste the prompt
Paste the prompt into the chat in Agent mode, which is the mode that can call MCP tools. Cursor asks before it runs each tool unless you have switched on auto-run.
Run it in Copilot
- 1
Connect Great Question to Copilot
In Copilot Studio, open your agent's Tools page → Add a tool → New tool → Model Context Protocol. Server name Great Question, server URL https://greatquestion.co/api/mcp/v1, OAuth for authentication, then add it to the agent.
- 2
Connect the other end
This workflow also needs your document store (Google Drive, Notion or SharePoint) connected in Copilot, through that tool's own connector.
- 3
Paste the prompt
Paste the prompt into the agent's chat. To run it the same way every time, put the prompt in the agent's instructions instead and share the agent with your team.
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
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
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
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
- Protecting PII in research ops
Worth reading before transcripts leave the platform.
- The best research repositories for research ops
If the real question is where research should live.
More workflows
See all 12- 03
Transcript to markdown
Turns a session transcript into clean markdown you can drop into a repo, a wiki or your notes, without paraphrasing a word.
Read only - 04
Attach the evidence to the ticket
Pulls the transcript and the participant's company onto the matching task in your planning tool, so whoever picks up the work can read the source.
Writes outside GQ - 05
The response rate tracker
Counts how many people you invited against how many submitted a screener, for any date range, without building a report.
Read onlySchedule monthly
