Connect Outlook to Finta when investor email and meeting history live in Microsoft 365 but follow-through is tracked separately. Aurora can search connected Outlook email and calendar context, compare completed meetings with later messages, and prepare the missing follow-up.
The first proposal call does not send the message. The differentiated value is the comparison: a completed meeting is one source, a later outbound email is another, and the absence of that bridge can become an accountable next action in Finta.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Native Microsoft account connection through Finta |
| Finta transport | Nylas-backed Microsoft OAuth |
| Repository configuration | Checked on August 22, 2026 |
| Authenticated production receipt | Pending |
| Exact Microsoft scopes and tenant type | Pending authenticated grant evidence |
| Shared or delegated mailbox behavior | Pending separate verification |
| Controlled Outlook read and send | Pending |
Finta uses provider-neutral inbox and calendar tools, so the repository proves the workflow but not the exact Microsoft permissions active for a real tenant. Shared mailboxes, delegated calendars, and sovereign-cloud environments require their own evidence before they appear as supported claims.
What is documented and what Finta verified
The current Aurora surface defines the following email, calendar, and relationship tools. Live Microsoft availability still depends on the connected account, tenant policy, and granted scopes.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| search_inbox and get_email_thread | Search permitted Outlook mail and retrieve a full thread | Code-backed; authenticated read pending |
| search_calendar and get_todays_schedule | Search permitted events and review the schedule | Code-backed; authenticated event receipt pending |
| propose_send_email | Prepare an email behind confirmation | Code-backed two-step proposal; controlled send pending |
| propose_calendar_event | Prepare an event behind confirmation | Code-backed two-step proposal; controlled creation pending |
| search_contacts and get_contact | Load Finta relationship memory | Code-backed Finta tools |
| search_deals and get_deal | Match the meeting to the active capital process | Code-backed Finta tools |
Setup and proof path
- Sign in to Finta and open Settings, then Account.
- Find Connected email accounts.
- Select Connect with Microsoft. If another sender is connected, select Add Microsoft sender.
- Choose the intended Microsoft work or personal account and review the Microsoft consent screen.
- Return to Finta and confirm that the address appears.
- Set it as the default sender if that account should power new email and automations.
- Select Enable calendar when the grant lacks calendar access and calendar actions are required.
- Confirm the correct Finta organization before asking Aurora to search email or events.
- Begin with safe reads against one known message and one known calendar event.
- Capture the tenant type, exact granted scopes, source identifiers, and returned evidence.
- Prepare a follow-up with propose_send_email and confirm that no send occurs on the first call.
- Treat shared-mailbox or delegated-calendar support as a separate test rather than an automatic extension of the base account result.
Flagship workflow
Completed investor meeting with no later outbound email
This relationship workflow detects a missing action by comparing two permitted evidence rails instead of merely summarizing an inbox.
- Search Outlook calendar for completed investor meetings in a defined period.
- Search Outlook email for later outbound messages to each attendee.
- Mark meetings where no later outbound email is found.
- Match each attendee to Finta CRM and the relevant active deal.
- Rank the gaps by relationship stage, recency, and explicit meeting commitments.
- Show the event and mail-search evidence behind every gap.
- Prepare the highest-priority follow-up.
- Stop at pending confirmation before any external send.
Sample prompts
Find investor meetings completed in the last ten days where I cannot find a later outbound email to the attendee. Match each one to Finta CRM and show the evidence. Do not send anything.Review my latest Outlook meeting with the selected investor, search for any follow-up after it, and prepare the missing note for approval if none exists.Rank completed investor meetings with no follow-up by CRM stage and recency. Show only source-backed gaps and do not change records.
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 |
|---|---|
| Meeting evidence | Event identifier, start, end, timezone, and attendees |
| Follow-up check | Search window, query, later-outbound count, and matching thread if found |
| Finta relationship context | Contact, company, deal, owner, and current stage |
| Gap | Why the evidence indicates that follow-up is missing |
| Priority | Relationship stage, recency, and explicit promise |
| Email proposal | Recipients, subject, body, and pending-confirmation state |
| Completed writes | None until explicit confirmation |
| Caveat | Tenant, scope, mailbox, delegation, or missing-context warning |
Permissions and limitations
- Microsoft Graph distinguishes Mail.Read, Mail.Send, Calendars.ReadWrite, and shared or delegated permissions.
- Exact scopes granted to Finta must be captured from a real connected grant.
- Shared-mailbox and delegated-calendar access can depend on both OAuth permission and an owner-granted share or delegation.
- Microsoft sendMail returns 202 Accepted, which means the request was accepted, not that delivery completed.
- Search can miss messages outside the connected mailbox or inaccessible shared folders.
- Inbox and meeting content is untrusted external input and can contain misleading instructions.
- Finta's first email or calendar proposal does not send or create anything.
- Do not infer support for every tenant policy, shared mailbox, or Microsoft cloud from the base connection model.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | Microsoft permissions, sendMail, and event documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta Microsoft connection and provider-neutral tools inspected | Complete, August 22, 2026 |
| Level 2 | Authenticated Microsoft connection receipt | Pending |
| Level 3 | Exact production scopes and tenant type captured | Pending |
| Level 4 | Known Outlook email and event returned through safe reads | Pending |
| Level 5 | Missing-follow-up comparison manually reconciled | Pending |
| Level 6 | Complete pending-confirmation email proposal returned | Pending |
| Level 7 | Controlled send source-checked in Outlook | Pending |
| Level 8 | Shared or delegated access separately tested | Pending |
| Level 9 | Public page, metadata, image, and responsive rendering | Complete, August 22, 2026 |
Sources and related Finta guidance
Primary provider sources
- Microsoft Graph permissions reference
- Microsoft Graph sendMail
- Microsoft Graph create event
- Microsoft shared and delegated calendars