Automation · Runs as new mail arrives in your inbox
Auto inbox
New mail sorted into colored labels as it arrives. Your assistant runs it as new mail arrives in your inbox and tells you when something needs your attention.
Auto inbox — Sep 17
Automation run • Sep 17
Auto inbox
Output
A new email from Ada Fern at Mossbank Textiles arrived about Alder Wool Throw lead times. I labeled the thread Supplier and left it in your inbox. Two automated marketing newsletters were labeled Updates and archived.
Ada is asking for our color breakdown before confirming production timing. A draft reply is waiting in your drafts in Google Workspace for your review.
Draft reply to Ada Fern
To: ada@example.com Subject: Re: Alder Wool Throw replenishment lead times
Hi Ada,
Thanks for following up. Lena and I are reviewing the Alder Wool Throw numbers during our buying call this morning. I will send over our breakdown across Ember Stripe, Fog Stripe, and Pine Stripe right after that meeting so you can confirm the schedule for Harbor & Pine.
Best, Maya
Pattern notice
Over the past two weeks, three supplier threads about fabric deliveries waited more than 48 hours for a reply. If you want, I can start flagging those threads in our morning summary.
Automation steps. Your assistant follows these 1 steps each time it runs, using your connected email and calendar.
- 01
Keep my inbox sorted as mail arrives, so I can see at a glance what needs me: label each new message as needing a reply, needing action, worth reading, a newsletter, transactional or noise.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Never archive emails that come from our wholesale stockists.
- Do not draft replies to messages where I am only copied.
- Label any message mentioning shipping delays as Urgent.
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
Labels new mail on its own. Never archives, moves, deletes or sends anything. 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.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate Auto inbox in the job library, and choose Add. The card helps you connect Google Workspace or Microsoft 365 if your email is not linked yet.
- What does it do on its own versus wait for me?
- It applies your labels and archives obvious clutter as mail lands in your inbox. When a message requires an answer, it prepares a draft in your drafts folder, but it never sends messages or deletes anything.
- Where do results arrive?
- Updates appear in your conversation with your assistant and can also be emailed to you. When incoming mail does not need your attention or clear action, the assistant stays quiet.
- How does it decide which labels to use?
- It reviews your existing folders and past sorting habits in Google Workspace or Microsoft 365, applying your real categories rather than creating generic ones.
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.