Inbox summary for a team mailbox
Starting pointBuilds on the shipped template “Outlook Email Workflow” (6 nodes), which you can find in the template library.
Give a team a morning read of what arrived in its shared inbox, with nothing in the mailbox changed.
- Get the mail folders and find the Inbox by its name.
- Get the latest messages from that folder.
- A policy rule redacts personal identifiers before an LLM node writes the summary.
- An output step delivers the summary to the team.
Where the approval sits. Reading alone needs no approval. The redaction and the choice of recipients are the controls here.
Supplier-query routing suggestion
DesignedSuggest which person should answer each supplier question, without moving or answering anything.
- Get messages from the shared accounts folder.
- An agent reads each one and suggests an owner from a list you supply.
- A human-input step shows the suggestions to the team lead, with approve and reject branches.
- Approved suggestions go to the owners as output. Mail is not moved.
Where the approval sits. The lead approves the assignment list, and the people who receive it do the actual work in Outlook.
Folder structure check before an automation
DesignedConfirm the folders a later workflow depends on still exist and are named as expected.
- Get the mail folders for the mailbox.
- A code node sets them beside the list the team agreed.
- Missing or renamed folders go to the mailbox owner in a human-input step.
- The result is recorded as output. Nothing is changed in Outlook.
Where the approval sits. The approval here confirms the owner has seen the differences. There is no write to approve.
- Shipped template
- A governed template with its approval step already in it ships in the platform.
- Starting point
- A shipped template runs the same actions. It is an integration test with no approval step, so you add the gate.
- Designed
- Design intent. It uses the actions listed above plus generic nodes, and nothing has been built as a template.