SharePoint in Agent Builder

The SharePoint step lets an agent create folders and upload files in a document library on a site you pick, and list what is already in a folder. It has three actions. Ensure folder and Upload file change the library. List folder reads it. There is no action that downloads a file. A file in someone's own OneDrive is a different step: OneDrive in Agent Builder. The step has no trigger of its own. A schedule, an email, or another system's alert starts the run, and this step files or lists once that run is going.

Syncing a library into the knowledge base is a different feature. That copy lives under Train, and the guide is Sync SharePoint. Signing this step in does not copy files into Train, and a Train connection does not sign the agent in. How the three places to connect differ is in Integrations overview.

app.centrus.ai/app/agents/workflow-builder

Agents

Build modular AI workflows with reusable nodes

File the certificate

1,240 / 10,000 creditsValidateResetRunsSettingsUpdate & Publish

Job finished

Job status changed

List the certificates

List attachments

Each file

Batch size 1

File the PDF

Upload file · Documents / Riverside House

2

AI builderMap

1. 1SharePoint in the Integration group of the Nodes panel.
2. 2The step on the canvas. Its summary is the action, then the site, library and folder, Upload file · Documents / Riverside House.
3. 3Connection: the Microsoft account this agent uses. With more than one account, Account picks which sign-in this step uses.
4. 4Actions: the one action this step performs. Upload file is selected.
5. 5Site and Library in SharePoint details. The folder path is under that library.

Centrus works alongside SharePoint. The files stay in the library, and the agent creates folders and uploads on the account you sign in. It does not replace the library, and it does not replace the job system that produced the certificate.

Open the agent in Agent Builder and find SharePoint in the Integration group of the Nodes panel, under OneDrive. Drag it onto the canvas and connect the step before it to its left-hand side. Until you choose an action, its summary reads No actions selected. Once you have chosen one, the summary is the action's name, then the site, the library and the folder when those are set, joined with slashes. For example Upload file · Meridian FM / Documents / Certificates/Riverside House. It does not read 1 action enabled, which is what an Outlook or Gmail step shows.

Job finished

Job status changed

SharePoint

No actions selected

2

1. 1SharePoint in the Integration group. Drag it onto the canvas.
2. 2The new step. It reads No actions selected until you choose an action in its Details panel.

On a phone, Agent Builder shows the canvas only. The Nodes panel is hidden on screens narrower than 768 pixels and the Details panel on screens narrower than 1,024 pixels, so you can follow an agent's steps on a phone but need a tablet or computer to add a SharePoint step or change its settings.

09:41

Centrus

Agents

Build modular AI workflows with reusable nodes

Chase overdue invoices

Save and Publish

Job finished

Job status changed

File the PDF

Upload file · Riverside House

The SharePoint connection belongs to this agent alone. It is separate from Train, so connecting a library there does not connect the agent, and connecting the agent does not start a sync. One connection covers every SharePoint step on the agent, so you only sign in once per agent. An agent can hold more than one Microsoft account. Each SharePoint step then picks which account to use, and after that you pick the site and the document library on the step.

You sign in with Microsoft. There is no customer ID or secret to copy, and there is no Copy from existing agent, because that list is only for connections that use a key. The person who signs in needs a Microsoft 365 account that can open the site, such as accounts@meridianfm.co.uk. Microsoft's page asks you to pick an account. Centrus asks Microsoft for permission to read and change files that account can open, which is wider than the one library you pick afterwards, to see the sites that account can see, and to read the signed-in profile. Later runs use that sign-in, so a Monday schedule can file a PDF without anyone sitting at the screen.

1. 1Save the agent with Save draft. Until it has been saved once, the Connection section reads Save this workflow as a draft first, then connect the account. and Connect is greyed out.
2. 2Select the SharePoint step. In the Details panel, open Connection and click Connect.
3. 3Centrus leaves Agent Builder and opens Microsoft's account page. Choose the account, then accept the permissions.
4. 4You return to the agent. A message reads SharePoint connected for this agent, and Connection reads Connected, followed by that account's address.
5. 5In SharePoint details, choose Site, then Library. Site stays on Connect SharePoint first until the sign-in has finished. Library stays on Pick a site first until a site is chosen. Changing the site clears the library.

Centrus does not store a password. Microsoft accepts or refuses the sign-in. If you close Microsoft's page before you finish, nothing is saved and Connection stays Not connected. If Centrus cannot open Microsoft at all, you see Failed to start SharePoint connection. If the request fails after that, you see Failed to connect SharePoint. Try Connect again, and if it persists ask whoever looks after your Microsoft 365 sign-in.

Several accounts. After the first account is connected, open Settings in the toolbar. Under Integrations, Add another account starts a second Microsoft sign-in and leaves the first account in place. Each row can be renamed, made primary, or disconnected on its own. On the step, Account appears once the agent has two or more SharePoint accounts, or if the step still points at an account that has been disconnected. Primary account (default) follows whichever row is marked primary in Settings. A named row, such as john.martin@meridianfm.co.uk, locks this step to that account. The list on the step shows the primary row with (primary) after the address. The site list reloads for the account the step is using.

Whose account a run uses. Integration mode, in Settings, is shown to the agent's owner and to an organisation administrator. Agent-level is the default, and it is the mode this step is built for: every SharePoint step uses the account connected on the agent, whoever starts the run. Per-user is only offered when the agent starts from chat. The control is greyed out for a schedule, for Email received, and for a system alert, because a scheduled run has no triggering user. SharePoint is not one of the systems that can use a person's own chat connection. If you switch the agent to Per-user anyway, the Connection section still shows the agent's account and adds a note that this step always uses that connection, because SharePoint has no per-user credentials. A run in that mode still fails. The message says the action is not supported, and it talks about sending and creating drafts, which are Outlook and Gmail actions, not SharePoint. Keep an agent that uses SharePoint on Agent-level. For how sharing and this switch fit together, see Share an agent.

Sharing and copying the agent. When you share an agent, its SharePoint connection stays on the agent. People you share it with cannot see or copy the sign-in. Their runs use the agent's account, site and library. When you duplicate an agent, the steps are copied and the connection is not. The copy says to connect again. Sign in again on the copy, or add the accounts under Settings.

Disconnecting. Disconnect on the step removes SharePoint from this agent. The confirmation reads SharePoint disconnected from this agent. Every SharePoint step on the agent stops until someone signs in again. Other agents keep their own accounts, and a Train connection is left as it is. To drop one account and keep another, disconnect that row under Settings, then Integrations, rather than using Disconnect on the step.

Select the step and open Actions in the Details panel. On a step in the agent's main flow the list is a set of radio buttons, one action only. The line under the title reads What this step does with the connected SharePoint account. There is no search box. The three names, in order, are Ensure folder, Upload file and List folder. The canvas summary becomes the action's name, then the site, library and folder when you have set them.

The fields sit in SharePoint details, under the actions. The line there says to pick the site and document library, then an optional folder. An empty folder path uses the library root. You can build the path from Step data references, or from {{ item.json.field }} inside a loop. Site and Library appear for all three actions. File name appears only for Upload file.

Site lists sites that account follows, plus a search that returns up to 100, sorted by name. A handful of Microsoft system sites are left out. If that search and the followed list are both empty, the list falls back to the root site. You pick a name. The step stores the id, so a later rename of the site in SharePoint does not change what was saved until you pick again. Library lists the document libraries on that site, and it stays disabled until a site is chosen. Changing Site clears Library.

Folder path (optional) is the path under the library root, with slashes between segments, such as Certificates/Riverside House. Leave it blank to use the library root. The help under the box says folders are created when they are missing. That is true for Ensure folder and for Upload file. It is not true for List folder: a path that is not there makes the list fail, and nothing is created. Characters \ / : " * ? < > | in a segment are turned into spaces before the folder is created or the file is named.

Ensure folder creates any missing segment and, if the folder is already there, uses that folder rather than making a second one. It is safe to run on every pass. An empty path returns the library root and creates nothing. You do not have to put it in front of Upload file. Upload file creates a missing Folder path itself before it uploads. Use Ensure folder when you want the folder even if there is no file to upload, or when a later step needs the folder's address.

Upload file sends one file from each incoming item. The file has to already be on that item, for example from a BigChange Download attachment step or from Outlook Download attachments. An item with no file is skipped. If every item is skipped, the summary reads No files to upload, and how many were skipped. Leave File name blank to keep the incoming file's name. If the name you type has no extension, the original extension is added. A name that is already in the folder is not overwritten. The step tries the name, then the same name with (1) before the extension, then (2). If all three are taken, the upload fails and the files already there stay. The name Microsoft stored can therefore differ from the name you typed, and that stored name is what the step passes on.

List folder returns the files and folders directly inside that folder, not the folders inside those folders. With no number set on the step, it asks for 100 and will not return more than 200. There is no box for that number on the main path. The step passes on one item. The files and folders sit in a list on that item, each with a name, a type of file or folder, a size, an address, and when it was last changed. It does not hand each file to the next step on its own, and it does not download the bytes. To fetch a file from a personal OneDrive, use OneDrive in Agent Builder.

What the step passes on. Ensure folder adds the folder id, its address and the path it created or found. Upload file adds the file's address in SharePoint and the name Microsoft stored, and it drops the file bytes so they are not carried further. List folder adds the list described above, on a single item. Later steps reach those fields through Step data references. To do something once per file in a list that arrived as one item, you need a step that splits that list first. A Loop walks items it is given. It does not open the list inside one item by itself. Loops are covered in Conditions, loops and approvals.

As a tool for an Intelligence step. Connect a SharePoint step to the Tools side of an Intelligence step and Actions becomes a searchable list where you can tick several. The line changes to Choose the tools this assistant can call. It fills the fields on the call. The AI decides when to call each one and fills in the fields itself. The canvas summary is the first action, then a count if there are more, such as List folder · Documents / RAMS +1.

Question from chat

From chat

Check the folder

GPT-5.6 Terra

Library tools

List folder · Documents / RAMS +1

1

1. 1The SharePoint step attached to the Intelligence step as a tool.
2. 2Actions: the SharePoint actions the AI may call. Here, list a folder and upload a file.
3. 3Pause for approval: each call the AI makes waits for someone to approve it in the Runs panel.

Pause for approval sits under Require approval on every SharePoint step, but it only applies to calls an AI makes, so it has no effect on a step in the main flow. To ask someone before a main-flow step uploads a file, put an Approval step in front of it.

SharePoint has no trigger of its own. Nothing in the library starts a run when a file arrives or a folder changes. The run starts somewhere else, and the SharePoint step is one of the steps after that. Three starts cover almost every facilities library: a Schedule Trigger (every Monday at 07:00, for a check of who is missing a document), Email received (a certificate lands in a folder, and the next steps file the attachment), or another system's alert, such as a BigChange webhook when a job is finished. Setting up a schedule is part of the trigger's own panel. Email is covered in Start an agent when an email arrives. A BigChange alert is covered in BigChange REST in Agent Builder. The general picture for every system is in Start an agent from a system alert.

Job finished

Job status changed

File the PDF

Upload file · Riverside House

1. 1Connection on the BigChange webhook. This is the BigChange REST connection, not SharePoint. SharePoint has no trigger of its own.
2. 2Event types: the events that start a run. Only Job status changed is ticked.
3. 3Set this up in BigChange: the steps to follow in BigChange and the address to paste there.
4. 4Simulate webhook: runs the agent once with a sample alert. An upload in the steps after it still changes SharePoint.

What the SharePoint step should read from the start. A BigChange webhook hands on the id of the record that changed, not the site name and not the file. Follow it with Get job if you need the site, then List attachments and Download attachment so the PDF is actually on the item. Upload file can do nothing with an id alone. A schedule hands on the time it fired, so the SharePoint step usually follows a step that already knows which folder to list. An email trigger hands on the new message. Outlook Download attachments then puts each file on its own item, and Upload file files those items in one visit. A filter that does not match does not start a run and does not use a credit. The trigger itself is free. Each run it starts costs 1 credit, like any other run.

Alerts only start runs once the agent is published. Run now works on a draft. A simulated BigChange alert is a real run: Ensure folder and Upload file still change the library, and the run uses credits. Try the writes with a dry run first, as described under Test before it goes live.

Job finished

Job status changed

Read the job

Get job

List the certificates

List attachments

Each file

Batch size 1

Download the PDF

Download attachment

Ensure the folder

Ensure folder · Riverside House

File the PDF

Upload file · Riverside House

File the certificate puts a job's certificate PDF into a folder for that site when the job is finished. Job finished is a BigChange webhook with Job status changed ticked, and the status filter in BigChange set to the completed statuses. Read the job uses Get job so the agent has the site, for example Riverside House on job J-10482, a boiler service for Northgate Housing, with Dylan Hughes as the engineer. List the certificates uses List attachments. Download the PDF, Ensure the folder and File the PDF sit inside the Loop, so each file is fetched, the folder Certificates/Riverside House is created if it is missing, and the PDF is uploaded with File name left blank. The first pass creates the folder. Later passes find it and leave it. The list and the job read cost 1 credit each. Each file costs three more, for the download, the folder and the upload. The BigChange side of the webhook is in BigChange REST in Agent Builder.

Certificates inbox

Outlook · Inbox/Certificates

Take the files

Download attachments

File the attachment

Upload file · Documents / Inbox

Save email attachments files what arrives in Inbox/Certificates. The trigger watches that folder on accounts@meridianfm.co.uk. Take the files is Outlook Download attachments, which puts each attachment on its own item. File the attachment is Upload file, with Site set to Meridian FM, Library set to Documents and Folder path set to Inbox. File name is left blank, so a gas certificate from Liam Carter keeps its original name. Every attachment on that email is uploaded in the one visit, because each one is already its own item. Each matching email costs 3 credits: 1 for the run, 1 for the download and 1 for the upload, however many attachments were on the message. The email trigger is free. The trigger itself is covered in Start an agent when an email arrives.

Monday at 07:00

Weekly · Mon at 07:00

List the RAMS

List folder · Documents / RAMS

Check who is missing

GPT-5.6 Terra

Email Sarah

1 action enabled

Weekly missing document checks a folder every Monday at 07:00 and emails Sarah Price if a site has no file. List the RAMS uses List folder, with Site Meridian FM, Library Documents and Folder path RAMS. The step returns one item, and the file names are in the list on that item. Check who is missing reads that list and compares it with the sites the team expects, such as Riverside House and 12 High Street. Email Sarah sends the names that are absent. Nothing in SharePoint is changed. The list costs 1 credit however many names come back, up to the cap under Limits and good to know. The check costs at least 2. The email costs 1. The schedule is free.

A dry run is the safe way to try a SharePoint step. Open Runs in the toolbar, click Run now and choose Dry run (no actions performed). List folder calls SharePoint for real, so you see the real names in the folder. Ensure folder and Upload file are skipped. Nothing is created and nothing is uploaded. The ensure summary says it would have run that action and that it was not performed, and it shows an internal name rather than Ensure folder. The upload summary says it would have uploaded the file or files to SharePoint and that it was not performed. Run for real performs every action, including the writes.

{
  "items": [
    {
      "name": "Riverside House RAMS.pdf",
      "type": "file",
      "size": 184320
    },
    {
      "name": "Harbour View RAMS.pdf",
      "type": "file",
      "size": 201114
    }
  ]
}

Open a step in the run to see its output. A skipped upload names the file it would have sent and does not include an address, because nothing was stored. The panel shows the first 50 items of each output, and later steps still receive all of them. A dry run costs 1 credit for the whole run. For a published agent, Run now on Run for real creates folders and uploads files, so try Ensure folder and Upload file with a dry run first. A simulated BigChange alert is not a dry run. For Run now, dry runs and the Runs panel in full, see Test an agent before it goes live.

A SharePoint step costs 1 automation credit each time it runs successfully, whatever the action and however many files Upload file sends in that one visit. A step that fails costs nothing. When the step is a tool, each call the AI makes costs 1 credit. SharePoint has no trigger. A run started by a schedule, by Email received, or by another system's alert still costs 1 credit for the run, like any other run, and that trigger itself is free.

Inside a Loop, the step is charged on every pass, so a Loop over 40 certificates that ensures a folder and uploads each file costs 80 credits for those two steps, before the download. One Upload file visit is usually cheaper when every file is already an item in front of it, as in the email example, because that visit is 1 credit however many items it sends. One List folder is 1 credit however many names come back. For allowances, limits and how to see what each run cost, see Automation credits and usage limits.

• Two connections. The agent's Microsoft account and a SharePoint library synced in Train are separate. Connecting one does not connect the other. See Sync SharePoint.
• The signed-in account, then one library. The sign-in can read and change files that account can open, not only the library you pick. Site and Library choose where this step works. A personal OneDrive, with a download action, is OneDrive in Agent Builder.
• Several accounts, one picker. Account appears when the agent has two or more SharePoint accounts. Primary account (default) follows the primary row in Settings. A schedule has no person behind it, so it always uses the account on the agent.
• Per-user integration mode. SharePoint has no per-user credentials. The Connection note says the step still uses the agent's account. The run does not: every SharePoint action fails in that mode, and the message talks about sending mail. Keep the agent on Agent-level.
• List size. On the main path there is no box for how many names to return. The step asks for 100, and will not return more than 200. It lists only the folder you named, not the folders inside it. A read whose result is over 8 MB fails, and the message states the size and the limit.
• Names. An upload does not replace a file that is already there. It tries the name, then (1), then (2), and then it fails. Ensure folder reuses a folder that is already there. \ / : " * ? < > | in a segment or a file name become spaces.
• No size of its own. The upload sends the whole file in one request. The step does not state a maximum. A file Microsoft refuses comes back as Failed to upload file, with Microsoft's message after it.
• One file on the item. Upload file takes the file on each incoming item, and only that file. A step that leaves several files on one item uploads the first. Outlook Download attachments avoids that by handing on one item per file.

• SharePoint not connected for this agent. Open the step's Connection section and click Connect. If you have duplicated the agent, the copy needs its own sign-in. A Train connection does not count.
• SharePoint account "primary" is no longer connected to this agent. The word in quotes is the account reference stored on the step, and it may be a longer id for an account you added later. The Account list also warns This node's account is no longer connected to this agent. Choose Primary account (default) or another account, or sign that one in again.
• Save this workflow as a draft first, then connect the account. Click Save draft, then Connect.
• Failed to start SharePoint connection. Centrus could not open Microsoft. Try Connect again. Failed to connect SharePoint means the request itself failed.
• You land on the agents list instead of the builder. The sign-in did not finish. The page address may include sharepoint_error. The builder does not explain that word. Open the agent and click Connect again.
• The action is not supported in per-user mode. The agent is on Per-user. SharePoint cannot run in that mode. Switch Integration mode to Agent-level. The message names an internal action id and mentions sending and creating drafts. You can ignore both and use the action's name from Actions.
• The site is not set, or the library is not set. SharePoint details has no Site or no Library. Connect SharePoint, pick a site, then pick a library. The message uses a dash and tells you to pick them on this node. Saving the agent can show the same gap before you run: the step has no SharePoint site set, or no document library set.
• No files to upload. The items in front of Upload file had no file on them. Put a download step in front, such as BigChange Download attachment or Outlook Download attachments. No file content provided to upload is the same gap, reported once the step has already tried to send.
• Failed to create folder, Failed to upload file, or Failed to list folder. Microsoft refused the call. The message includes Microsoft's reason. For an upload, three copies of the name may already exist, because the step will not overwrite and it stops after (2). For a list, the folder path may not exist: List folder does not create it.
• Failed to list document libraries. The site was picked but its libraries could not be loaded. Check the account under Account, pick the site again, or sign in again.
• A SharePoint site id is required, or a SharePoint library id is required. The action ran without the id the picker stores. Pick Site and Library again rather than typing a name into a field.
• No actions selected. The step has no action yet. Choose one under Actions.
• A list stops early. List folder stops at 100 names on the main path, and at 200 at most. It does not look inside subfolders. Narrow the folder rather than expecting every file on the site.
• The summary shows an internal name. A finished List folder or Ensure folder can say sharepoint_list_folder or sharepoint_ensure_folder. That is the action you chose. A repeated upload in the same run can say the upload was already performed. The file went up on the first attempt.
• An alert never starts the agent. SharePoint does not listen for alerts. Check the schedule, the Email received trigger, or the other system's webhook on the same agent. The agent must be published. See Start an agent from a system alert.

The SharePoint step has 3 actions. One reads the library and two change it. There is no download. They call Microsoft Graph at https://graph.microsoft.com/v1.0, as the Microsoft account connected on the agent. Where an action calls more than one path, the table gives the main one.