Automation for assistants and chiefs of staff · Runs after a meeting is transcribed
Post-meeting tasks
Tracked tasks logged from meeting notes and follow-up emails drafted for review. Your assistant runs it after a meeting is transcribed and tells you when something needs your attention.
Post-meeting tasks — Sep 17
Automation run • Sep 17
Post-meeting tasks
Output
Hi Sol, here is the summary from this morning's Harbor & Pine leadership sync on Q4 goals with Maya Calder and Lena Vale. Two tasks were added to Linear, and one follow-up email draft is waiting in your Google Workspace drafts folder.
Decisions made
- Q4 goals will prioritize wholesale expansion and Portland warehouse fulfillment readiness.
- The hiring timeline for the Portland store manager will hold steady, with Lena Vale leading final candidate interviews.
Tasks created in Linear
- Update Q4 goals document: Assigned to Sol Varga. Due date: September 21, 2026. Includes milestones for wholesale onboarding and warehouse inventory targets.
- Review Portland fulfillment checklist: Assigned to Lena Vale. Due date: September 24, 2026 (estimated date, as none was stated). Cross-reference staffing needs with Owen Reed.
Open question
- Whether the Driftline Supply Co proposal requires revised shipping terms before October 1.
Draft email waiting in Google Workspace drafts
To: Maya Calder (maya@example.com), Lena Vale (lena@example.com) Subject: Follow-up from Q4 goals sync
Hi Maya and Lena,
Following up on our discussion this morning, I have recorded our agreed milestones for the Q4 goals doc and created the Linear task for Lena's fulfillment checklist review. I will share the revised goals document by September 21 for your review.
Best, Sol
Automation steps. Your assistant follows these 6 steps each time it runs, using your connected email and calendar and tasks.
- 01
After each meeting, read the transcript and pull out the decisions, every action item with an owner and due date, open questions, and anything promised to someone.
- 02
Create a task in my task tracker for each action item, with the owner, due date and enough context to stand on its own.
- 03
Where the owner is unclear, assign it to me; where no date was said, set a sensible one and mark it an estimate.
- 04
Don't duplicate a task an earlier meeting already created.
- 05
Draft the follow-up emails I said I'd send.
- 06
Then give me a short recap with links to the tasks.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only create Linear tasks for action items assigned to me.
- Draft follow-up emails only when external partners attend the meeting.
- Do not set estimated due dates when a specific deadline was not 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
Creates tasks in your tracker on its own. Every follow-up 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 and tasks. Connect Google Workspace or Microsoft 365 for your email and calendar and Linear, Notion, Todoist, monday.com, or Trello for your tasks to Fieldwork. It also uses your meeting notes when connected.
More automations for assistants and chiefs of staff.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate Post-meeting tasks in the job library, and click Add. If Google Workspace or your task tracker like Linear are not connected yet, the setup card prompts you to link them first. It starts running automatically whenever a recorded meeting transcription finishes.
- What does it do on its own versus waiting for me?
- It logs action items directly into your task tracker without needing prior approval. It never sends messages or emails on its own, so all drafted follow-up emails wait safely in your drafts folder for your review and send.
- Where will I receive the meeting recap?
- The recap and task confirmations arrive as a message in your conversation with your assistant, and can also be emailed to you. When a meeting produces no decisions or action items, the assistant stays quiet or shares a brief note.
- How does it decide who owns a task or when it is due?
- It extracts owners and dates directly from the conversation transcript. If an owner is not clearly stated, it assigns the task to you, and if no date was spoken, it applies an estimated due date marked clearly for review.
Security first
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.