Connect Gmail to Finta when investor conversations live in your inbox but the next action belongs in your relationship workflow. Aurora can search a connected inbox, load the full thread, compare it with Finta CRM and deal context, and prepare a reply for review.
Finta's email proposal flow does not send on the first call. It returns the proposed recipients, subject, body, and thread target with a confirmation request. The useful outcome is not inbox automation by itself. It is a source-backed next move that preserves judgment and relationship context.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Native Google account connection through Finta |
| Finta transport | Nylas-backed Google OAuth |
| Repository configuration | Checked on August 22, 2026 |
| Authenticated production receipt | Pending |
| Exact production OAuth scopes | Pending authenticated grant evidence |
| Known Gmail thread read | Pending |
| Controlled send and Gmail source check | Pending |
Finta exposes email actions through provider-neutral tools. The repository proves the workflow and the human-confirmation boundary, but it does not reveal the exact scopes granted by Google's live consent screen. Those scopes must be captured from an authenticated production grant before Finta publishes a scope-specific claim.
What is documented and what Finta verified
The tool names below are defined in Finta's current Aurora MCP surface. They describe the code-backed workflow, not a receipt from Kevin's or any customer's mailbox.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| search_inbox | Search permitted connected-mailbox messages | Code-backed; authenticated Gmail receipt pending |
| get_recent_emails | Review recent messages | Code-backed; authenticated Gmail receipt pending |
| get_email_thread | Load the full provider thread | Code-backed; known-thread receipt pending |
| check_email_from_contact | Check messages from a named contact | Code-backed; authenticated Gmail receipt pending |
| propose_send_email | Prepare a complete email and confirmation token | Code-backed two-step proposal; controlled provider send pending |
| search_contacts and get_contact | Load durable Finta relationship context | Code-backed Finta record tools |
| search_deals and get_deal | Match the thread to an active raise | Code-backed Finta record tools |
Setup and proof path
- Sign in to Finta and open Settings, then Account.
- Find Connected email accounts.
- Select Connect with Google. If another sender is already connected, select Add Google sender.
- Choose the intended Google account and review the consent shown by Google.
- Return to Finta and confirm that the address appears in the connected-account list.
- Select it as the default sender if it should be used for new email and automations.
- If calendar work is also needed and calendar access is missing, select Enable calendar and complete the reconnect flow.
- Use Aurora in the correct Finta organization and begin with a read-only search for one known non-sensitive thread.
- Capture the connected account, granted scopes, exact source thread, and returned tool evidence before adding a verified-production claim.
- Test propose_send_email without confirming it. Verify that the proposal includes every recipient, subject, body, and thread target.
- If a controlled send is later authorized, source-check the resulting message in Gmail. A successful API response alone is not delivery proof.
Flagship workflow
Unanswered investor inbound to reviewed follow-up
This workflow combines inbox evidence with relationship intelligence so Aurora can distinguish a real investor request from a generic unread message.
- Search recent inbound investor messages for a diligence question, meeting request, or explicit next step.
- Load the full thread and retain the source thread identifier.
- Match the sender to a Finta CRM contact and active deal.
- Separate facts stated in the thread from inferred next actions.
- Compare the request with the current relationship stage, open commitments, and prior context.
- Recommend the next step and explain why it is timely.
- Prepare a reply using propose_send_email.
- Stop at pending confirmation until the user reviews the recipients, subject, body, and thread target.
Sample prompts
Find recent investor emails asking us for something. Match each sender to Finta CRM, show the unanswered request and source thread, and recommend the next step. Do not send or update CRM.Open the latest thread with the selected investor, summarize their diligence questions, compare them with our active round record, and prepare a reply for my review.Show inbound investor conversations from the last seven days where the sender is in the Interested stage and we have not replied. Draft only, with no sending.
Expected output
The output specification below describes the evidence a useful result should contain. It is not presented as a live tool receipt unless the verification ladder says otherwise.
| Output field | Expected evidence |
|---|---|
| Source evidence | Mailbox provider, thread identifier, latest inbound time, sender, and source-grounded request |
| Finta relationship context | Matching contact, company, deal, stage, and open commitments |
| Evidence boundary | Direct statements separated from Aurora inference |
| Recommended next step | One relationship-aware action with timing rationale |
| Email proposal | Recipients, subject, body, thread target, and pending-confirmation state |
| Approval state | Confirmation required before the external send |
| Completed writes | None until the user explicitly confirms a controlled action |
| Caveat | Scope, mailbox, alias, shared-access, or missing-context warning |
Permissions and limitations
- Google recommends requesting the narrowest scopes needed. Gmail read, compose, send, and modify scopes carry different access and verification implications.
- Finta's exact production Google scopes are configured outside the repository and must be captured from a real grant rather than inferred.
- A connected inbox is required, and search quality depends on provider data visible to that connected account.
- Email content is untrusted external input and can contain misleading or malicious instructions.
- Preparing an email does not send it. Finta requires a second confirmed call for the proposed send.
- A provider API success is not evidence that the recipient received, read, or acted on a message.
- Shared mailboxes, aliases, delegated sending, and organization-specific Google policies require separate verification.
- CRM and task tools can have different mutation behavior from email proposals. Review the exact tool before authorizing it.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | Google Gmail scope and sending documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta Google connection, email tools, and confirmation code inspected | Complete, August 22, 2026 |
| Level 2 | Authenticated Google connection receipt | Pending |
| Level 3 | Exact production scopes captured from the connected grant | Pending |
| Level 4 | One known Gmail thread returned and reconciled | Pending |
| Level 5 | Complete pending-confirmation email proposal returned | Pending |
| Level 6 | Controlled confirmed send source-checked in Gmail | Pending |
| Level 7 | Public page, metadata, image, and responsive rendering | Complete, August 22, 2026 |