Agent setup guide
Outlook Inbox Triage
Sorts every new Outlook email, saves reply drafts in Outlook and pings Slack on urgent ones.
What it does
Sorts every new Outlook email, saves reply drafts in Outlook and pings Slack on urgent ones.
- Starts from each new email in your Outlook Inbox (checked on your plan's schedule interval).
- AI sorts it into needs reply, urgent, FYI or junk (flagging likely phishing), and writes a two-sentence summary with the asks and any deadline.
- For urgent and needs-reply emails, saves a reply draft in your Outlook Drafts folder, in your voice, with [placeholders] wherever a fact or decision is yours.
- Urgent emails also ping your Slack channel with the summary and a link to open the email.
- FYI and junk emails are left untouched.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Outlook Mail (Microsoft 365 or Outlook.com) and Slack, connected in Settings → Integrations.
What it doesn't do
- It never sends email: drafts only, you send from Outlook.
- It doesn't move, label, flag or delete emails.
- The draft is a new email to the sender with “Re:” in the subject, not a reply inside the original thread.
- It doesn't read attachments, and it isn't instant (checked on your plan's schedule interval).
- It works with Outlook only; a Gmail version waits for the Gmail inbox connector.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.
Before you start
- A paid plan: agents run live, and the Free plan only runs Dry Runs.
- An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
- These apps, connected in Settings → Integrations: Outlook Mail and Slack.
- The app it watches, connected in Settings → Integrations (the agent starts from an app event).
- About 15 minutes.
Set it up step by step
Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.
1. Connect your AI provider
The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
2. Connect Outlook Mail
Connect your Microsoft 365 or Outlook.com mailbox in Settings → Integrations → Outlook Mail (some companies need an IT admin to approve Fluxo Flow first).
3. Connect Slack
Connect your Slack workspace (Settings → Integrations → Slack).
4. Describe yourself and your inbox
Open “Sort the email and draft a reply” and replace the placeholder.
| Setting | What to enter | In step |
|---|---|---|
| About you and your inbox | Replace the placeholder with who you are and your role, what's urgent for you (key customers, your boss, topics), senders you consider junk, and how you sign emails. It starts as “[DESCRIBE WHO YOU ARE, YOUR ROLE, WHAT COUNTS AS URGENT, WHO IS JUNK FOR YOU AND HOW YOU SIGN EMAILS HERE]” until you replace it. | “Sort the email and draft a reply” |
5. Pick your Outlook account
Pick your mailbox on the trigger and in “Save a reply draft in Outlook”.
| Setting | What to enter | In step |
|---|---|---|
| Outlook account (inbox) | The Microsoft 365 or Outlook.com mailbox whose Inbox is triaged. Pick your connected Outlook Mail account. | “New email in Outlook” |
| Outlook account (drafts) | The same mailbox, used to save reply drafts. Pick your connected Outlook Mail account. | “Save a reply draft in Outlook” |
6. Pick the Slack account and channel
Open “Ping you in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace urgent emails are posted to. Pick your connected Slack account. | “Ping you in Slack” |
| Slack channel (or DM) for urgent emails | A private channel only you watch works best, e.g. #my-urgent-email. | “Ping you in Slack” |
7. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
8. Switch the trigger on
Open the trigger and click “Activate app trigger”: new Inbox emails are checked on your plan's schedule interval.
How it works
The agent is a normal workflow with 8 steps (1 AI step). You can open, edit and monitor it like any other workflow.
- New email in Outlook — Starts on “New email” in Outlook Mail (an app event). Starts a run for each email arriving in your Outlook Inbox (checked on your plan's schedule interval; emails already there are skipped).
- Sort the email and draft a reply — AI step (runs on your AI provider key). AI sorts the email into needs reply, urgent, FYI or junk, summarises it and drafts a reply for the ones that need one.
- What kind of email? — Decision: picks the branch to follow. FYI and junk need nothing; urgent emails also ping Slack; urgent and needs-reply emails get a draft in Outlook.
- No reply needed — Kept in the run history. Branch: FYI or junk. FYI and junk emails are left as they are; the run history keeps the category and summary.
- Ping you in Slack — Slack: Post a message. Branch: Urgent. Posts the urgent email's sender, subject, summary and a link to open it in Outlook.
- Pinged — Kept in the run history. The run history keeps the alert.
- Save a reply draft in Outlook — Outlook Mail: Create a draft. Branch: Urgent / Needs reply. Saves the drafted reply in your Outlook Drafts folder, addressed to the sender, for you to check and send.
- Draft saved — Kept in the run history. The run history keeps the email's category, summary and the draft.
Test it with Dry Run
Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.
Sample data fields
subject, id, conversation_id, internet_message_id, from, from_name, to (a list), cc (a list), received_at, preview, body, has_attachments, is_read, web_link.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
Go live
- Open the trigger and click “Activate app trigger”: new Inbox emails are checked on your plan's schedule interval.
- Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
- The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
- When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.
Questions
Will it send emails for me?
No. It only saves drafts in your Outlook Drafts folder; you read, edit and send them yourself.
Does it move or label emails?
No. Your inbox stays exactly as it is; the category is in the Slack alert and the run history.
Troubleshooting
- “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
- A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
- An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
- Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
- No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
- A step failed: open the run in History and check that step in the Trace tab for the error and what it received.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .