Connect Google Calendar to Finta to turn a meeting time into relationship context and a clear next action. Aurora can search events, show today's schedule, combine an investor meeting with CRM and deal records, and prepare a new event for confirmation.
Event creation remains a two-step action. The relationship-intelligence job is to connect the scheduled interaction to prior concerns, open promises, relationship ownership, and the outcome the team should seek.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Calendar access on a native connected Google account |
| Calendar write detection | Code-backed in Finta |
| Enable calendar reconnect flow | Code-backed in Finta |
| Authenticated event read | Pending |
| Exact granted calendar scopes | Pending authenticated grant evidence |
| Controlled event creation | Pending |
| Conferencing-link behavior | Pending separate verification |
A Finta user may have a connected Google email account without the calendar permission required for event creation. The account screen can prompt the user to reconnect through Enable calendar. Exact live scopes remain external to the repository and require a grant receipt.
What is documented and what Finta verified
These are Finta's current code-backed calendar and relationship tools. Live provider behavior still depends on the connected account, calendar permissions, timezone, and Google settings.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| search_calendar | Search permitted connected-calendar events | Code-backed; known-event receipt pending |
| get_todays_schedule | Review the current schedule | Code-backed; authenticated receipt pending |
| propose_calendar_event | Prepare an event and confirmation token | Code-backed two-step proposal; controlled event pending |
| search_contacts and get_contact | Load attendee relationship context | Code-backed Finta tools |
| search_deals and get_deal | Match the meeting to the active round | Code-backed Finta tools |
| search_inbox and get_email_thread | Optionally load related email context when inbox access exists | Code-backed; authenticated source receipt pending |
Setup and proof path
- Sign in to Finta and open Settings, then Account.
- Connect the correct Google account using Connect with Google or Add Google sender.
- Complete Google's consent flow and return to Finta.
- Confirm that the intended account appears under Connected email accounts.
- Check the calendar-access indicator.
- If calendar access is absent, select Enable calendar and complete the fresh Google OAuth flow.
- Confirm that the right account remains selected after reconnecting.
- Start with search_calendar against one known non-sensitive event.
- Reconcile the event time, timezone, attendees, organizer, and source identifier with Google Calendar.
- Prepare a controlled future event and verify that the first call returns a confirmation request without creating it.
- Review every attendee, time, timezone, location, and conferencing setting before a second confirmed call.
- Verify conferencing-link behavior separately before promising that every event receives a Google Meet link.
Flagship workflow
Meeting to briefing to approved next event
Calendar evidence becomes useful when it is combined with durable relationship memory and a clearly stated meeting outcome.
- Find an upcoming investor meeting.
- Match attendees to Finta contacts and the active raise.
- Retrieve prior objections, commitments, relationship ownership, and unresolved questions from available Finta records.
- Produce a pre-meeting brief that separates verified facts from missing information.
- Name the outcome the team should seek in the meeting.
- After the meeting, capture the agreed next step.
- Prepare the next event with attendees, timezone, purpose, and optional conferencing details.
- Stop at pending confirmation before creating it.
Sample prompts
Show tomorrow's investor meetings. Match each attendee to the Finta contact and active deal, then build a brief with prior context, open questions, and the outcome I should seek.Find my next meeting with the selected fund and prepare a source-backed briefing. Mark anything you cannot verify.Prepare a 30-minute follow-up meeting with the selected investor next Tuesday at 2 PM Eastern. Show the full event and attendee list for confirmation, but do not create it yet.
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 |
|---|---|
| Current event | Event identifier, start, end, timezone, organizer, and attendees |
| Relationship context | Matching contacts, deal, owner, prior concerns, and open commitments |
| Evidence ledger | Every briefing fact connected to a Finta or permitted source |
| Unverified questions | Information Aurora could not establish |
| Meeting objective | One concrete outcome and rationale |
| Next-event proposal | Title, start, end, timezone, attendees, purpose, and pending-confirmation state |
| Completed writes | None until the user confirms |
| Caveat | Permission, timezone, attendee, conference-link, or missing-context warning |
Permissions and limitations
- Google Calendar read and write operations require appropriate scopes and user access to the target calendar.
- Exact Finta production scopes remain pending because they are configured outside this repository.
- A user can sometimes read a calendar but lack permission to create or edit events on it.
- Creating an event requires valid start and end times, and timezone interpretation must remain explicit.
- Invite behavior, conference links, and notifications depend on the provider, account, calendar, and event configuration.
- Finta can propose a meeting link, but the public page must not guarantee a Google Meet link without a production test.
- The first propose_calendar_event call does not create an event.
- Calendar availability is evidence of scheduling possibility, not consent from an attendee.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | Google Calendar scope and event documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta calendar-write detection and proposal code inspected | Complete, August 22, 2026 |
| Level 2 | Authenticated Google account with calendar access | Pending |
| Level 3 | Exact granted calendar scopes captured | Pending |
| Level 4 | One known event returned and source-checked | Pending |
| Level 5 | Event time, attendees, and timezone reconciled | Pending |
| Level 6 | Complete pending-confirmation event proposal returned | Pending |
| Level 7 | Controlled confirmed event source-checked in Google Calendar | Pending |
| Level 8 | Conferencing-link behavior separately verified | Pending |
| Level 9 | Public page, metadata, image, and responsive rendering | Complete, August 22, 2026 |