Automation for assistants and chiefs of staff · Runs as new mail arrives in your inbox
Meeting slip alerts
Alerts when a client declines or moves an important meeting. Your assistant runs it as new mail arrives in your inbox and tells you when something needs your attention.
Meeting slip alerts — Sep 17
Automation run • Sep 17
Meeting slip alerts
Output
Pia, June Moss from Ternlight Outpost just declined her upcoming meeting with Maya Calder. Google Workspace records confirm her status changed to declined, and no new time has been proposed.
Here are the details from incoming mail and Google Calendar:
- Client: Ternlight Outpost
- Contact: June Moss (june@example.com)
- Meeting title: Harbor & Pine Wholesale Review
- Scheduled time: Friday, September 18, 2026, at 10:00 AM Portland time
- Status change: June Moss declined the invitation today at 2:14 PM.
- Organizer: Maya Calder
- Note from client: No note or replacement time was included in the decline notification.
Calendar status check: Google Calendar shows the meeting remains on Maya Calder's schedule for tomorrow morning, but June Moss is listed as declined. No conflicting hold or alternative invite appears on the calendar.
Recommended next steps for review:
- Confirm if Maya wants to offer alternative windows early next week.
- Check with Cal Brook to see if June reached out separately about wholesale orders.
Nothing has been removed or rescheduled on the calendar, and no email draft was created.
Automation steps. Your assistant follows these 4 steps each time it runs, using your connected email and calendar.
- 01
As mail arrives, spot declines and reschedules of client meetings.
- 02
Check the calendar to confirm the meeting actually slipped, so a stale or already-resolved change doesn't raise an alarm.
- 03
Identify the event, who proposed the change and which client it belongs to, and alert me once per change.
- 04
Skip internal meetings.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only alert me for meetings with wholesale accounts.
- Ignore declines if the client proposes a new time within the same week.
- Also check Cal Brook's calendar for client reschedules.
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
Monitors mail and alerts you when meetings change. Modifies nothing on your calendar. 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.
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 Meeting slip alerts in the job library, and choose Add. If your Google Workspace or Microsoft 365 account is not connected yet, the card will guide you to link it first.
- Can it move or cancel the meeting for me?
- No, it only monitors mail and checks calendar statuses. It never alters your calendar events, sends replies, or deletes invitations, leaving all scheduling decisions to you.
- Where do the alerts arrive?
- Notifications appear as messages in your conversation with your assistant and can also be emailed to you. When incoming emails contain no meeting changes, it stays quiet.
- How does it verify that a meeting actually slipped?
- When an email suggests a decline or time change, it inspects your calendar directly to confirm whether the attendee is marked as declined or moved. This ensures you do not receive false alarms for resolved changes or outdated messages.
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.