Google WorkspaceMicrosoft 365

Automation for finance · Runs after a meeting is transcribed

Post-call commitments

Agreed deliverables and follow-up emails drafted immediately after each call. Your assistant runs it after a meeting is transcribed and tells you when something needs your attention.

Post-call commitments — Sep 17

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

Automation run • Sep 17

Post-call commitments

Output

Theo, here are the commitments captured from your 10:00 AM finance sync with Rhea Quill, based on your transcript in Granola.

Your commitments

  • Update September cash forecast: Add supplier bill MT-201 and update wholesale receivables for Harbor & Pine. For Rhea Quill. Deadline: Friday, September 18, 2026 (estimated, none stated).
  • Follow up on Ternlight Outpost invoice: Send a payment request for invoice HP-1041 ($600). For Rhea Quill. Deadline: Today, September 17, 2026 (estimated, none stated).

Draft email (waiting in drafts)

To: June Moss (june@example.com) Subject: Harbor & Pine invoice HP-1041

Hi June,

I am checking in on Harbor & Pine invoice HP-1041 for $600, which was due on September 7, 2026. Could you let me know when we might expect payment? If you need another copy of the invoice, I can provide one.

Thanks, Theo

Proposed Slack message (proposed below)

Channel or recipient: Maya Calder (direct message)

Hi Maya, Rhea and I reviewed cash projections this morning. I will share the updated cash forecast reflecting the Mossbank bill tomorrow.

Items to circle back on

  • Hourly billing review: You agreed to review Rhea's August advisory hours once she sends the breakdown. No date was set.

Nothing has been sent or posted. Your email draft is saved in Google Workspace.

View conversation

© Fieldwork AI Inc.

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

  1. 01

    When a meeting transcript is ready, pull out every commitment I personally made, separate from what others took on, and only those I actually agreed to.

  2. 02

    For each, capture the deliverable, who it's for, and the deadline, inferring a date if none was said and marking it an estimate.

  3. 03

    Quote numbers and dates exactly.

  4. 04

    Draft the follow-up emails and messages I said I'd send.

  5. 05

    Send me one consolidated note: my commitments first, then the drafts, then anything I said I'd circle back on.

Adjust the automation in chat

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

  • Only pull commitments from meetings with external partners.
  • Do not draft Slack messages for internal check-ins.
  • Always set estimated deadlines to three business days out when none was mentioned.

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

Captures your commitments and drafts follow-up messages. Every draft 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, team chat when connected.

Google WorkspaceMicrosoft 365

Questions about this automation.

How do I set up post-call commitments?
Open your assistant on the Agents page in Fieldwork, select this automation from the job library, and click Add. The setup card will prompt you to connect your calendar in Google Workspace or Microsoft 365 and your meeting notes in Granola or Fireflies if they are not linked yet. It runs right after each meeting transcript is ready.
What does the automation handle on its own, and what requires my review?
It reads your meeting transcript, identifies promises you agreed to make, and creates message drafts. It never sends emails, posts to Slack, shares documents, or changes your calendar. Every email draft stays in your drafts folder until you choose to send it.
Where do my commitments and drafts arrive?
Your summary arrives as a message in your conversation with your assistant, and Fieldwork can also email it to you. If a call has no commitments or follow-ups to record, your assistant stays quiet.
How does it know which commitments are mine rather than someone else's?
The automation reviews the transcript for deliverables you personally accepted or promised to deliver during the conversation. Commitments taken on by other attendees are excluded so your summary only lists what you need to follow up on.

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