Google WorkspaceMicrosoft 365

Automation for leaders · Runs after a meeting is transcribed

Leadership action recap

Decisions, assigned owners, and drafted follow-up messages after your leadership meeting. Your assistant runs it after a meeting is transcribed and tells you when something needs your attention.

Leadership action recap — Sep 17

F
Fieldwork<noreply@mail.fieldwork.ai>Thu, Sep 17, 11:05 AM
to me
Fieldwork

Automation run • Sep 17

Leadership action recap

Output

Here is the recap from this morning's Harbor & Pine leadership sync with Sol Varga, Lena Vale, and Theo Marsh. A recap email is waiting in drafts in Google Workspace for your review.

Decisions Made

  • Final interviews for the Portland store manager role will focus on Dara Finch and Ines Calloway.
  • Theo will keep the September cash forecast based on current inventory orders without extra borrowing.

Open Items

  • Approval of the Q4 goals draft is held until Sol incorporates warehouse staffing numbers from Owen Reed.

Action Items by Owner

  • Lena Vale: Schedule final interviews with Dara Finch and Ines Calloway by Friday, September 18. Status: Assigned by Maya.
  • Sol Varga: Collect warehouse staffing assumptions from Owen Reed and update the Q4 goals doc by Monday, September 21. Status: Assigned by Maya.
  • Theo Marsh: Reconcile supplier bills MT-201 and MT-202 with Mossbank Textiles by Tuesday, September 22. Status: Assigned by Maya.
  • Maya Calder: Review Sol's updated Q4 goals doc on Tuesday, September 22. Status: Owned by Maya.

Draft Follow-up Email Waiting in your Google Workspace drafts folder:

Subject: Harbor & Pine leadership recap and next steps

Hi team,

Thanks for the time today. Here are the agreed owners and target dates:

  • Lena: Complete final interviews for Dara Finch and Ines Calloway by September 18.
  • Sol: Update the Q4 goals doc with warehouse inputs by September 21.
  • Theo: Reconcile open Mossbank Textiles supplier bills by September 22.
  • Maya: Review the revised Q4 goals on September 22.

Please reply with any corrections.

Maya

View conversation

© Fieldwork AI Inc.

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

  1. 01

    After my leadership and staff meetings, pull the decisions, the action items, and above all who owns each and by when.

  2. 02

    Write an owner-by-owner recap, separating what was decided from what is still open, and draft a short follow-up to the group confirming owners and next steps.

  3. 03

    Note the items I own and the ones I assigned, so the delegation tracker can chase them.

Adjust the automation in chat

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

  • Only run this for meetings with Leadership in the calendar title.
  • Group action items by due date instead of by owner.
  • Add a section for topics that were postponed to the next meeting.

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 after a meeting is transcribed.

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

Logs action items and drafts the recap on its own. Every group message 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 meeting notes 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 this automation in the job library, and click Add. You will be prompted to connect Google Workspace or Microsoft 365, along with Granola or Fireflies if you use them for meeting notes.
What does the automation do on its own versus wait for me?
It reviews your meeting notes, organizes decisions and tasks, and saves a follow-up draft directly into your email drafts folder. It never sends the message or shares notes without your manual approval.
Where do my recap results arrive?
Recaps appear directly in your Fieldwork chat thread as soon as the transcript finishes processing, and a copy can also be sent to your inbox. If a meeting has no clear decisions or next steps, your assistant tells you briefly.
Which meeting sources can it read?
It reads recordings and transcripts from Fieldwork, or from Granola and Fireflies when those tools are connected to your account.

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