SharePoint
Databases & spreadsheets
Turn form submissions into list items, upload documents, and publish pages automatically.
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.
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
- Find list itemsSearch 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 IDFetch 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 itemAdd a new item to a list, setting the column values from your form fields, records, or earlier workflow steps.
- Update list itemChange 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 itemRemove an item from a list — again by ID from an earlier step, or by the first item matching a column and value.
- Create listCreate a new list on a site, with a name and an optional description.
- Find file or folderSearch 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 IDFetch 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 contentsList 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 fileUpload 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 folderCreate 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 folderDelete a file or folder from a document library by its ID.
- Create pageCreate 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.
- Get page by IDFetch 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 pagePublish 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 pageDelete 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.
Example use cases
Usecase
Description
- Form submissions to a listCapture every Softr form entry — requests, applications, incident reports — as a new item in a SharePoint list.
- Request tracker in a portalFind list items for the signed-in member and show them in your Softr app, then update the item when a status moves.
- Document intakeUpload files members submit through your app straight into the right document library and folder.
- Per-client foldersCreate a folder for each new client record so their documents have a home from day one.
- Client-facing document listList a folder's contents, or search a library by name, to show clients only the documents that concern them.
- Clean-up after cancellationWhen a request is withdrawn, find the matching list item by reference and delete it, along with its uploaded files.
- Announcements from your appPublish a SharePoint news post when something happens in Softr — a release goes out, a policy changes, a client signs.
- Page per project or clientCreate a draft page from a template of your own HTML when a project starts, then publish it once someone reviews it.
- Retire outdated pagesOn a recurring schedule, get a page, check whether it is still current, and delete the ones that have gone stale.
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.
- 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.
