The flow
Starts it 1Service 11
The steps in the order they run, from what starts it.
- 1Download fileMicrosoft Share Point ToolService
- 2Update fileMicrosoft Share Point ToolService
- 3Upload fileMicrosoft Share Point ToolService
- 4Create item in a listMicrosoft Share Point ToolService
- 5Create or update item (upsert)Microsoft Share Point ToolService
- 6Delete an itemMicrosoft Share Point ToolService
- 7Get an itemMicrosoft Share Point ToolService
- 8Get many itemsMicrosoft Share Point ToolService
- 9Update item in a listMicrosoft Share Point ToolService
- 10Get listMicrosoft Share Point ToolService
- 11Get many listsMicrosoft Share Point ToolService
- 12Microsoft SharePoint Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 12
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 12 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.