Microsoft SharePoint n8n integrationAutomate Microsoft SharePoint with n8n.

Takes a document out of a SharePoint library and hands it to the next node as binary data, ready to be attached, read or copied somewhere else.

• Site: the site whose folders n8n retrieves, picked from the dropdown.
• Parent Folder: the folder the file is downloaded from, / (Library root) when the document sits at the top of the library.
• File: the document itself, selected by name, for example my-file.pdf.

Replaces what is already in the library instead of adding a second copy next to it. The file keeps its place, the version behind the name changes.

• Site and Parent Folder: where the file to update lives, root of the library included.
• File: the existing document to update.
• Change File Content: whether the contents get updated at all.
• Updated File Contents: the name of the input field holding the binary data, shown in the Binary tab of the Input panel on the left, often data.
• Updated File Name: optional, and the original name stays if you leave it empty.

Writes a new document into a library folder from binary data produced earlier in the workflow.

• Site: the site the folder list is retrieved from.
• Parent Folder: the destination folder, or / (Library root).
• File Name: the name the file gets once uploaded, so build it with an expression when it has to carry a date or a reference.
• File Contents: the input field carrying the binary data, the one listed in the Binary tab of the Input panel, commonly data.

Adds a row to a list that already exists. The list is never created here, only filled.

• Site: the site n8n reads the available lists from.
• List: the list the item is created in.
• Columns: the mapper where each column of that list gets its value, typed in or pulled from the incoming item with {{ $json.field }}.

One operation for both cases: the item is created, or the existing one is updated. Handy when the workflow cannot know which of the two it is dealing with.

• Site: the site holding the list.
• List: the list the item is created or updated in.
• Columns: the mapper carrying the values for that list's columns.

Removes one item from a list. There is nothing to undo afterwards, so the node usually sits behind an IF that checks a condition first.

• Site: the site the lists are read from.
• List: the list the item is deleted in.
• Item: the item to delete, selected rather than described.

Reads a single item and puts its content into the workflow, so the following nodes work on real values instead of assumptions.

• Site: the site the list belongs to.
• List: the list the item is retrieved from.
• Item: the item to get.

Reads several items at once, either the whole list or the subset that matches a formula. This is the reading operation most reporting workflows are built on.

• Site and List: the site, then the list searched for items.
• Filter by Formula: evaluated for each record, for instance fields/Title eq 'item1'. Leave it empty and all the items come back.
• Return All: on, n8n walks the pages of the API and returns everything; off, Limit caps the number of items.
• Fields: in Options, picks what the output carries, among id, webUrl, createdBy, lastModifiedDateTime and five others.

Changes the values of an item already sitting in a list, column by column, without touching the rest of the list.

• Site: the site the lists are retrieved from.
• List: the list the item is updated in.
• Columns: the mapper where the new values are set for that list's columns.

Returns the details of one list rather than its contents. Useful when the workflow needs to know about the container itself.

• Site: the site the lists are retrieved from.
• List: the list to retrieve.

Returns the lists of a site. It is also the shortest test available on this node, since Site is the only thing it needs.

• Site: the site whose lists are retrieved.
• Return All: on, every list comes back across the API pages; off, Limit sets the maximum.