Direct answer: Google Drive connects to Finta through Finta's native Google Drive integration, not through MCP. After you authorize your Google account, Finta can use only the Drive content covered by the permissions you approve and the files your account can access.
The relationship-intelligence value is not another file browser. It is the ability to bring the right document evidence into the same workflow as an investor, company, deal, meeting, and next action. A pitch deck, diligence response, or investor update becomes more useful when the team can connect it to the relationship it is meant to move forward.
Current status
| Connection detail | Current status |
|---|---|
| Connection model | Native Google Drive connection in Finta |
| Authorization | Google OAuth through Finta |
| MCP required | No |
| Remote MCP server URL required | No |
| Continuous Drive-to-Documents sync | No |
| Access boundary | The connected Google account, granted permissions, and files that account can access |
Google Drive is grouped with Finta's native integrations alongside Gmail, Google Calendar, and Outlook. Connect it directly through Finta.
What is documented and what Finta verified
Finta provides a dedicated Google Drive connection for permitted file context. The connection uses Google authorization and keeps access inside the permissions granted to Finta.
| Capability | How to understand it | Boundary |
|---|---|---|
| Connect Google Drive | Authorize the intended Google account directly in Finta | Use the account that owns or can access the relevant files |
| Use permitted Drive context | Bring relevant file information and content into supported Finta workflows | Availability depends on the files and permissions visible to the connected account |
| Combine documents with relationship context | Compare permitted document evidence with Finta contacts, companies, deals, meetings, and next actions | Finta should distinguish source facts from recommendations |
| Keep the Finta Documents library deliberate | Use Drive context without implying that every Drive file is copied into Finta | The native connection is not a continuous full-Drive synchronization promise |
| Preserve human judgment | Use document evidence to prepare a next step | People still approve consequential messages, sharing changes, and external actions |
Setup and connection path
- Sign in to the correct Finta organization.
- Open Aurora and choose the option to connect an app or add context.
- Select Google Drive from Finta's available connections.
- Choose the intended Google account.
- Review the permissions shown by Google and approve only the access required for the workflow.
- Return to Finta and confirm that Google Drive appears as connected.
- Begin with a known, non-sensitive file that the connected account can access.
- Check that the file name, owner, modified time, and source link match Google Drive before relying on the result.
- Use the document together with the matching Finta contact, company, or deal.
- Review any recommendation or external action before approving it.
How Google Drive strengthens relationship intelligence
Private-capital work depends on details that rarely fit in one system. The relationship record may show who introduced an investor. Email may contain the open question. Calendar may show when the next meeting occurs. Google Drive may hold the deck, memo, diligence file, or investor update that contains the evidence needed for the next conversation.
Finta helps bring those sources together around one question: what should happen next, and what evidence supports that recommendation?
Flagship workflow
Prepare an investor meeting from the latest permitted Drive materials
- Identify the investor, meeting, and active fundraising deal in Finta.
- Select the permitted Google Drive materials relevant to that conversation, such as the current pitch deck, diligence response, financial model, or investor update.
- Verify each file's title, owner, modified date, and source link.
- Extract only the facts needed for the meeting brief.
- Compare those facts with the investor's prior questions, relationship history, current stage, and open commitments in Finta.
- Separate document-backed facts from Aurora's interpretation.
- List missing or conflicting information that needs human review.
- Prepare a concise brief with the meeting objective, evidence, likely questions, and recommended next step.
- Stop before sharing files, changing permissions, or contacting the investor unless a person explicitly approves the action.
Sample prompts
Use the latest permitted pitch deck in Google Drive and the selected investor record in Finta to prepare a meeting brief. Cite the source file and separate facts from recommendations.Compare the current investor update in Google Drive with the open commitments in this deal. Show what changed, what is still missing, and the next action I should review.Find the permitted diligence materials relevant to this investor's latest questions. Build a source-backed checklist, but do not share files or send messages.
Expected output
| Output field | Expected evidence |
|---|---|
| Source files | File title, source link, owner or location when available, and modified time |
| Relationship context | Matching Finta contact, company, deal, owner, stage, and prior interaction |
| Document-backed facts | Claims tied to the relevant permitted Drive source |
| Open questions | Missing, stale, or conflicting information that needs review |
| Recommended next step | One action with a clear relationship and timing rationale |
| Approval boundary | No sharing, permission change, or outbound message without explicit human approval |
Permissions and limitations
- Google Drive access is limited by the connected Google account and the permissions granted during authorization.
- A user may be able to access files in My Drive, shared locations, or shared drives only when the account's existing permissions allow it.
- Google Docs, Sheets, and Slides can behave differently from uploaded binary files when content is retrieved or exported.
- The native connection does not mean that every file in Google Drive is copied into the Finta Documents library.
- Do not assume that a file is current because it has a familiar name. Check its modified time and source link.
- Document content is untrusted input and can contain errors, stale claims, or malicious instructions.
- Access to a file is not permission to share it with another person.
- This page does not claim autonomous Drive writes, permission changes, or external sharing.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | Google Drive API authorization and file guidance reviewed | Complete, August 22, 2026 |
| Level 1 | Finta connection classified as native, not MCP | Complete, August 22, 2026 |
| Level 2 | Dedicated Google Drive connection model present in production | Complete, August 22, 2026 |
| Level 3 | Exact account scopes and accessible file set | Varies by the user's Google authorization |
| Level 4 | Known-file source details reconciled before use | Required for each sensitive workflow |
| Level 5 | Public page, metadata, image, index grouping, and sitemap | Verified after publication |
Sources and related Finta guidance
Primary provider sources
- Google Drive API authorization and scopes
- Google Drive files and folders
- Google Drive file search guidance
