Upload a file to SharePoint
Uploads a file to a SharePoint site and returns its URL. You supply the site, the document and the target folder; the subflow does the rest.
View template- Connect
- Documents
- Microsoft 365
- Over HTTP
Connect SharePoint to Business Central
The documents already live in SharePoint — somebody just puts them there by hand today. AutoFlow takes over the path from the posted document into the right folder.
The connection
What AutoFlow does with SharePoint
SharePoint is already in place in most companies — as an archive, as customer folders, as the drive everybody uses. What is missing is the path into it: documents are created in Business Central and end up in SharePoint because somebody exports, renames and uploads them.
AutoFlow turns that path into a process. The document is posted, the PDF is rendered, the file lands in the right folder, and the link to it sits on the document. You build it in the editor, not in code.
What it does
What AutoFlow and SharePoint exchange
The SharePoint interface in Microsoft Graph is a large one: anything you can do there, you can build in AutoFlow. The most common cases are here.
Out of Business Central
- Render a posted document as a PDF and file it
- Build the target folder from document data — customer, year, document type
- Create missing folders as it goes, rather than failing on a missing path
- Write the link to the filed document back onto the record
- Set column values on the file, so the library stays filterable
- Fetch filed documents back out and use them in the next step
Into Business Central
- A scheduled process looks into a library and works through what it finds
- Read files and their column values and take them into Business Central
- React to documents that appear, a signed order confirmation for instance
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
- Microsoft 365 with SharePoint Online The connection runs over the Microsoft Graph API. An on-premises SharePoint Server takes a different route — talk to us.
- An app registration with write access Set up once in Entra ID, with access to the library you file into. Not to the whole tenant.
- A folder structure you have decided on The process files where you tell it to. Deciding that rule is the actual work — and the conversation you were going to have anyway.
How it's built
A template to start from
The subflow is ready in the gallery. You take it, enter your library, and the connection stands.
Built with it
Processes built on this connection
File invoices to SharePoint automatically
When a sales invoice is posted, AutoFlow renders the PDF, files it in the right SharePoint folder and writes the link back onto the document.
Read the use caseQuestions we get asked
Do I need dedicated steps in the editor?
No. The connection runs on HTTP calls inside a subflow, and the subflow already exists. You wire it in once and call it from any process that needs to file something.
What happens if the folder does not exist yet?
It gets created. A process that fails on a missing path is useless in the first month after go-live — and just as useless afterwards.
Does this work with a different document store?
Yes. The process is the same; only the call at the end points somewhere else. Azure Blob Storage, another DMS or a network share with an API all work to the same pattern.
What happens at a Business Central update?
Nothing. The logic does not sit in the BC core as an object extension; it sits beside it as configuration. There is nothing to recompile at update time.
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