Team automation · Runs 1 day before a meeting with “1:1” in its title
Prepare me for my one-on-ones.
Open items from last time, recent work, and topics to discuss. This automation runs 1 day before a meeting with “1:1” in its title. Fieldwork emails you the report when something needs attention.
Prepare me for my one-on-ones — Sep 17
Automation run • Sep 17
Prepare me for my one-on-ones
Output
Two Harbor & Pine priorities remain open for your 1:1 with Lena tomorrow, September 18 at 9:02 AM Portland time.
Since the September 11 meeting:
- Lena’s work: The Fall buying plan now separates purchase priorities from quantities awaiting supplier confirmation.
- Issue Lena raised: Unconfirmed lead times still prevent a firm buying recommendation. No confirmed arrival dates were found in the available notes or correspondence.
- Maya’s promise: Maya agreed to approve the buying budget. No approval was found, so this remains open pending confirmation.
Questions to ask:
- Which supplier confirmations are blocking your next decision?
- What budget decision do you need from me today?
- What should we resolve before the next buying review?
Notes page updated: After reading Lena’s existing page in the Fieldwork knowledge base, I carried forward the budget approval and supplier confirmations, recorded the buying-plan progress, and added these three questions.
Automation steps. The agent follows these 4 steps each time it runs, using your connected email and calendar.
- 1
Read my notes page for the person in my upcoming one-on-one.
- 2
Check what has happened since we last met: their work, issues they raised, and anything I promised to do.
- 3
Summarize open items, new developments, and two or three questions to ask.
- 4
Update the page with what you found.
Adjust the automation in Chat
Tell the agent what to do differently and ask it to set up that version with the same trigger.
- Set this up two days before meetings titled Lena 1:1.
- Include outstanding promises from the last two meetings.
- Limit the preparation to three discussion topics.
Fieldwork emails the report. Each email links to the full run as a conversation in Fieldwork. The automation asks the agent to keep a log in your knowledge base and read it before each run to check what has changed.
What starts this automation
Runs 1 day before a meeting with “1:1” in its title. At setup, choose the lead time and which meeting titles to match.
Only useful reports
When nothing needs attention, the run skips the email. When there are findings, you get a report with a link to the full conversation.
No messages sent
An automated run has no tool that sends, posts, or replies. The agent can update notes and its log in your Fieldwork knowledge base.
This automation reads your email and calendar. Connect Google Workspace or Microsoft 365 to Fieldwork. The automation uses whichever you connect.
More automations for team.
Questions about this automation.
- How do I set it up?
- Connect your email and calendar and identify the person’s notes page in the Fieldwork knowledge base. It triggers one day before meetings with 1:1 in the title.
- What permissions does it need?
- It needs access to the relevant notes and correspondence, plus write access to save the page update. It sends no messages and changes no calendar events.
- Can I change the timing or focus?
- Ask in chat to set up an adjusted automation with a different offset, title filter, or discussion focus. It cannot run by hand.
- Where does the report arrive?
- The report arrives by email with a link to the full conversation. If nothing needs attention, neither email nor push is sent.
Security first
Your data stays yours. Your data is never used to train any AI model - not ours, not a provider's. Fieldwork is GDPR compliant and certifying against SOC 2 and ISO 27001, with encryption in transit and at rest, and org-level access controls throughout.
Try Fieldwork
$50 / user / mo introductory pricing. AI quota included.
- ✓Down from $99 / user / mo
- ✓All platform features
- ✓Early access, no card required