​

SharePoint integration

Connect SharePoint with your Softr applications to put the sites your team already works in behind your no-code app. Turn form submissions into list items, keep request trackers current, upload member documents straight into the right document library, and publish pages and news posts — without anyone opening SharePoint to do it by hand.

​

Overview

The Softr SharePoint integration lets your workflows work with three parts of a SharePoint site: lists, document libraries, and pages. Read and write list items to use SharePoint lists as a backend for trackers, registers, and intake logs; create folders, upload files, and browse libraries to keep documents organised as your app is used; and create, publish, and clean up site pages and news posts from a workflow. Workflows can also run the other way round: a file arriving in a document library, a folder renamed, a list item edited, or a page published can be the thing that starts a workflow off. Once you connect your Microsoft account, Softr reads your sites, lists, document libraries, pages, and list columns live. You pick them from dropdowns rather than typing IDs, and the column choices always reflect the list you selected — so a column added in SharePoint shows up in your workflow without any re-configuration.

​

Available Actions

​

List items

​

Find list items

Search a list and return the items you need. Filter by a single column value — for example every request whose Status is Open — or leave the filter blank to return the first items in the list. Max items caps how many come back (100 by default).

​

Get list item by ID

Fetch one item and use its column values in later steps. Identify it either by an item ID from an earlier step, or by a search condition — a column and value, which returns the first matching item.

​

Create list item

Add a new item to a list, setting the column values from your form fields, records, or earlier workflow steps.

​

Update list item

Change the column values on an existing item. As with Get list item by ID, you can point at the item by ID from a previous step, or find it by a column and value.

​

Delete list item

Remove an item from a list — again by ID from an earlier step, or by the first item matching a column and value.

​

Create list

Create a new list on a site, with a name and an optional description.

​

Files & folders

​

Find file or folder

Search a document library by file or folder name — a partial name works. Scope the search to a single folder, or leave the folder blank to search the whole library. Returns up to Max items results (25 by default).

​

Get file or folder by ID

Fetch a single file or folder by its ID to use its details in later steps — name, path, link, size, and when it was created and last modified.

​

Get folder contents

List the files and folders inside a folder. Leave the folder blank to list the document library root. Max items caps the result (100 by default).

​

Upload file

Upload a file into a document library — for example a document a member submitted through a Softr form. Choose a destination folder or leave it blank to upload to the library root, optionally override the file name, and decide what happens if a file with that name already exists: rename the new file, replace the existing one, or fail the step.

​

Create folder

Create a folder in a document library — inside a parent folder, or at the library root. Same-name handling matches uploads: rename, replace, or fail.

​

Delete file or folder

Delete a file or folder from a document library by its ID.

​

Pages

​

Create page

Create a new page on a site. Title is what readers see; Page file name is optional and becomes the last part of the page URL — leave it blank to derive it from the title, and .aspx is added for you if you omit it. Choose a Page layout (Article or Home), whether the result is an ordinary Page or a News post, and supply the Content as HTML, which is added as a single full-width text section. The page is created as a draft — nobody else sees it until it is published, so follow this with Publish page when the page should go live immediately.

​

Get page by ID

Fetch a page from a site — picked from a dropdown of that site’s pages — including its text content, URL, layout, page type, version, and whether it is currently published.

​

Publish page

Publish the latest version of a page, making it visible to everyone with access to the site. Pair it with Create page to publish in the same run, or use it on its own once a draft has been reviewed. The action reports the page’s real state after publishing rather than assuming success: if the page library has an approval flow, the page stays unpublished until that flow completes, and the result says so.

​

Delete page

Delete a page from a site, moving it to the site recycle bin. The result describes what was removed — file name, title, the URL it lived at, and whether it was published or still a draft.

​

Available Triggers

Every SharePoint trigger checks the site on a schedule and starts your workflow once for each change it finds. Nothing that is already there when you turn the workflow on starts it — the first run is for what happens next.

​

List items

​

List created

Starts a workflow when a new list is created on the site you pick — useful when teams spin up their own trackers and you want them announced, registered, or wired into your app without anyone remembering to say so.

​

List item created

Starts a workflow when a new item is added to the list you pick. Editing an item that is already there does not start it.

​

List item created or updated

Starts a workflow when an item is added to the list, and again whenever an existing item changes. Use the changeType field to tell the two apart.

​

Files & folders

The three file triggers take an optional File types — a comma-separated list of extensions such as pdf, docx — so a workflow that only handles contracts is not woken by every image someone drops into the library. Leave it blank to watch every file type.

​

File added to folder

Starts a workflow once for each file added to the folder you pick; leave the folder blank to watch the document library root. Files added to a subfolder do not start it — use File added to folder or subfolders for those. Editing a file that is already there does not start it, and neither does a file moved in from somewhere else, because SharePoint keeps the date it was originally created. New folders never start it.

​

File added to folder or subfolders

The same trigger, widened: it starts once for each file added anywhere beneath the folder you pick, however deeply nested, including files added straight to that folder.

​

File created or updated

Starts a workflow when a file is added to the folder you pick, and again whenever a file already in it changes. Use the changeType field to tell the two apart. Subfolders are not included. Bear in mind SharePoint also counts renaming a file, checking it in or out, and restoring an earlier version as a change, so not every run means the contents differ — compare modifiedAt or size against what you saw last if that matters. Several edits between two checks arrive as a single run carrying the file’s latest state.

​

Folder created or renamed

Starts a workflow once for each folder added directly to the folder you pick, and again whenever one of those folders is renamed. changeType tells the two apart, and a rename also gives you the old name in previousName, so you can find the folder in your own records. A folder created and renamed between two checks arrives as a single creation under its final name — there is no earlier name to report, because nobody had seen the folder before. Folders created deeper down do not start it, and neither do files — pick one of the file triggers for those. A folder moved in from somewhere else does not start it either, because SharePoint keeps the date it was originally created; renaming it afterwards does. Deleting a folder never starts it, and neither does adding a file inside a folder you are watching, even though SharePoint updates that folder’s modified date.

​

Pages

​

Page created or updated

Starts a workflow for every page on the site you pick — a site keeps them all in one place, so there is nothing further to narrow it to. changeType tells a new page from a changed one. Saving a draft counts as a change, as does editing the draft of a page that is already live, and publishing. Check published if your workflow should only act on what visitors can see, or publishingLevel if you are following the editing lifecycle — the two disagree for a live page that is currently checked out for editing. Several edits between two checks arrive as a single run carrying the page’s latest state, so a long editing session does not start it once per keystroke. The page’s content is not included: use Get page by ID with the ID from the trigger when you need the body.

​

Key Benefits

• Your SharePoint site as a backend: Power Softr apps from the lists and libraries your team already maintains — no migration, no duplicate source of truth.
• Always in sync with your site: Sites, lists, libraries, pages, and columns are read live from SharePoint, so dropdowns never drift out of date when someone adds a column, a library, or a page.
• Right value, right column type: Filter values are matched against the column’s real type — text, number, date, or yes/no — so filtering works the way it does inside SharePoint.
• Work by ID or by condition: Get, update, and delete items either by an ID carried from an earlier step or by a column value, so workflows work even when nothing upstream knows the item’s ID.
• Documents where they belong: Files uploaded through your app land in the correct library and folder, with predictable handling when a name is already taken.
• Both directions: Write into SharePoint from your app, and start workflows from what happens on the site — a file arriving, a folder renamed, a list item edited, a page published.
• Creations and changes, told apart: Triggers that cover both label every run with changeType, and a renamed folder carries its old name, so a workflow can branch without keeping its own history.
• Draft, then publish: New pages start as drafts, so a workflow can assemble a page or news post and only make it visible once you are ready — in the same run or a later one.

​

Example Use Cases

​

How to Connect Softr with SharePoint

1. Open your Softr app and go to Workflows.
2. Create a new workflow and add a SharePoint action, or start it with a SharePoint trigger.
3. Click Connect SharePoint and sign in with the Microsoft account that has access to the site you want to use.
4. Authorize Softr to access your SharePoint sites.
5. Pick the Site, then the List, Document library, or Page the action should work with.
6. Map fields from your Softr forms, records, or previous workflow steps to the list columns — or choose the file to upload, or write the page content.
7. Save and activate your workflow.