Google WorkspaceMicrosoft 365

Automation for investors · Runs as new mail arrives in your inbox

Intro thank-yous

A personal thank-you note drafted to anyone who introduced a founder. Your assistant runs it as new mail arrives in your inbox and tells you when something needs your attention.

Intro thank-yous — Sep 17

F
Fieldwork<noreply@mail.fieldwork.ai>Thu, Sep 17, 2:02 PM
to me
Fieldwork

Automation run • Sep 17

Intro thank-yous

Output

Hale, an email from Ellis Dune at Covebend Ceramics arrived following your 1:00 PM introductory call today. Google Workspace calendar confirms the meeting took place, and your notes in Affinity show a pass.

I traced the thread back to Maya Calder at Harbor & Pine, who made the initial introduction. A draft thank-you note is waiting in your Google Workspace drafts folder for review. Nothing has been sent.

Meeting summary

  • Founder: Ellis Dune, Covebend Ceramics
  • Introduced by: Maya Calder, Harbor & Pine
  • Meeting time: September 17, 2026, 1:00 PM Portland time
  • Outcome: Pass (outside Larchmont Ventures fund mandate)
  • Status: First thank-you draft for this introduction

Proposed draft to Maya Calder

To: Maya Calder (maya@example.com) Subject: Re: Intro: Ellis Dune (Covebend Ceramics) <> Hale Morrow (Larchmont Ventures)

Hi Maya,

Thank you for connecting me with Ellis Dune at Covebend Ceramics. We spoke earlier today, and I was impressed by Ellis's focus on regional craft and durable supply partnerships.

We are going to pass on an investment from Larchmont Ventures right now, as early stage artisanal goods sit outside our fund scope. I let Ellis know and offered to stay in touch as the business expands. I appreciate you thinking of us, and I will see you at our next board review.

Best, Hale

View conversation

© Fieldwork AI Inc.

Automation steps. Your assistant follows these 4 steps each time it runs, using your connected email and calendar.

  1. 01

    When mail suggests I've met a founder someone introduced me to, confirm the meeting happened from my calendar and the thread.

  2. 02

    Tell a pass apart from moving forward, and skip it if I declined before meeting.

  3. 03

    Trace back to who made the introduction and draft a short thank-you in the original thread: one genuine thing I liked about the founder, a brief honest reason if I'm passing, and a line keeping the door open.

  4. 04

    Each introduction gets thanked once.

Adjust the automation in chat

Tell your assistant what to do differently and it sets up that version for you.

  • Only draft thank-yous for introductions from our limited partners.
  • Wait until I log a deal stage in Affinity before preparing the draft.
  • Draft the thank-you note only when we decide to move forward with the founder.

Results arrive as a message from your assistant. Each run posts to your conversation with your assistant, and can email you too. The automation keeps a log in your knowledge base and reads it before each run to see what has changed.

What starts this automation

Runs as new mail arrives in your inbox. It reads the mailbox you choose when you add it.

Only useful reports

When nothing needs attention, the run says so in a line or stays quiet. When there are findings, you get them with a link to the full run.

What it does on its own

Drafts the thank-you note in thread on its own. Every email waits for you to send. An automated run has no tool that sends, posts, shares, or deletes anything.

This automation reads your email and calendar. Connect Google Workspace or Microsoft 365 to Fieldwork. The automation uses whichever you connect. It also uses your CRM when connected.

Google WorkspaceMicrosoft 365

Questions about this automation.

How do I set this up?
Open your assistant on the Agents page in Fieldwork, locate Intro thank-yous in the library, and select Add. If your Google Workspace or Microsoft 365 account is not linked yet, you can connect it right on the card. It starts monitoring your incoming mail right away.
Does Fieldwork send the thank-you email for me?
No, it never sends emails or contacts anyone on your behalf. It prepares a draft in the original email thread inside your email drafts folder, leaving you in complete control to review, edit, and send it.
Where do results arrive?
Updates appear directly in your Fieldwork chat conversation, and you can also choose to have them emailed to you. When incoming emails do not match an introductory meeting, the assistant remains quiet.
How does the assistant determine who made the introduction?
It traces the original conversation thread in Google Workspace or Microsoft 365 to pinpoint the person who introduced you. It then checks your calendar and CRM, such as Affinity, to verify the meeting took place and ensures each introduction is only thanked once.

Security first

  • SOC 2SOC 2 Type IIAudit underway
  • ISO 27001ISO/IEC 27001Certification underway
  • ISO 42001ISO/IEC 42001AIMS in operation
  • App Defense AllianceCASA Tier 2Assessment passed
  • GDPR compliantGDPRUK and EU compliant
  • No training on your data

    Neither we nor our model providers train on your data. Inference runs with zero retention wherever the provider supports it.

  • Access

    Agents only see what the person asking can see. Conversations, files, apps and connections stay private until shared, and admins have no way into conversations.

  • Encryption and isolation

    Data is encrypted at rest and in transit. Each user's code runs in its own microVM, and secrets reach models by name only.

  • Continuity

    Continuous backups, replicated to a second region. Data is exported on request and deleted within 30 days of a contract's end.

Security at Fieldwork