Outlook - Fetch Emails
Reads the emails from a folder in your mailbox. You supply the address and the folder path, the rest is done.
View template- Connect
- Microsoft 365
- Over HTTP
Connect Outlook to Business Central
A good share of what ends up in Business Central arrives by mail. Today somebody opens the mailbox, saves the attachment, types it in and drags the mail into a done folder. Those are exactly the three motions AutoFlow can take over.
The connection
What AutoFlow does with Outlook
Orders, invoices, dispatch notes, order confirmations: a lot of it arrives as mail with an attachment, and the path from there into Business Central is currently a person. The mailbox is not the problem — the path out of it is.
AutoFlow reaches the mailbox over Microsoft Graph. A process fetches the mail from a folder, takes the attachments and afterwards moves the mail to wherever you keep handled post. What happens between fetching and filing is what you build in the editor — that is the part that looks different in every company.
What it does
What AutoFlow and Outlook exchange
The Outlook interface in Microsoft Graph is a large one: anything you can do there, you can build in AutoFlow. For the most common cases there are ready-made templates in the gallery.
Out of Business Central
- Move an email into another folder of the same mailbox
- And with it, record what the process has already handled
Into Business Central
- Read emails from a folder in an Exchange Online mailbox
- Take an email's attachments and use them in the process
- Address the folder by its path, nested folders included
Connected by subflow
Ready-made subflow templates are waiting in the gallery: take one, enter your credentials, and the subflow is there as a step in your own processes. You can start with it today.
What you need
What has to exist on your side
- A mailbox in Exchange Online The connection runs over Microsoft Graph. An on-premises Exchange takes a different route — talk to us.
- An app registration with read access to the mailbox Set up once in Entra ID and stored in AutoFlow as the credential set MS-GRAPH. That is exactly what the three templates reach for.
How it's built
The connection is ready in the gallery
Read, take the attachments, file away — the three motions are in the gallery as separate subflows. You take them, enter your mailbox and folders, and call them from your own process.
Outlook - Get Email Attachments
Fetches the attachments of an email. The piece between “the mail is here” and “the document is in the system”.
View templateOutlook - Move Email
Moves an email into a different folder. That is how the process remembers what is done, without a table of its own.
View templateQuestions we get asked
Do I need dedicated steps in the editor?
The three subflows are your steps. You take them from the gallery and from then on drop them into any process that needs the mailbox, exactly like any other step.
Can an incoming mail trigger an automation?
Yes. You build a scheduled process that checks the folder at whatever interval you choose — every five minutes, say — and starts whatever should happen for each new mail. You set the interval, and it can differ per mailbox.
How does the process know which mail it has already seen?
By the folder. Processed mail moves on, and whatever is in the inbox folder is outstanding. That is why the third template matters as much as the first — and it happens to be the version a person can follow without opening a log.
I want to turn emailed invoices into documents. Is this that?
That is what AutoFlow Receive is for — the finished solution that reads documents out of mailboxes, EDI channels and PDFs and creates them in Business Central. This connector is the layer underneath: the building blocks for whatever else you want to do with a mailbox.
What happens if the folder does not exist?
The process stops with a message naming the folder it looked for and the mailbox. A typo in the path should be recognisable as a typo, not pass silently as an empty result.
Try it yourself
Starting with AutoFlow costs nothing
You can build and test in the sandbox as long as you like, without limits. And two active flows stay free forever in your production tenant — not a trial that runs out.
- Unlimited testing in the sandbox
- 2 active flows free forever
- No credit card needed