How to Use sFiles and Power Automate Together

How do sFiles and Power Automate work together?

Your sales team uploads a contract from an Opportunity. Legal needs to review it, and the rep needs to know when it's approved. Usually, that means an email, a document link, and a follow-up when nobody responds.

With sFiles, the rep can upload the contract to SharePoint without leaving Salesforce. A Power Automate flow can watch that library and send an approval request when the document is marked ready.

The contract stays in SharePoint. The rep works with it through sFiles, and the reviewer opens the same file from the approval request, provided they have access.

The examples below show workflows you can set up. You'll need to configure the Power Automate flow and the matching sFiles settings.

sFiles vs. Power Automate: what does each do?

sFiles gives your team a place to work with SharePoint documents inside Salesforce. Power Automate handles steps such as sending an approval request or posting a notification after something happens to a file.

1. Send contracts for approval from Salesforce

An account manager uploads a contract to an Opportunity and marks it ready for legal review. Instead of emailing the contract and following up manually, a Power Automate flow sends the request to the reviewer.

Configure document type and review-readiness fields in sFiles so the flow knows which files need approval. The flow can choose the reviewer using your routing rules and include a link to the SharePoint file in the request.

When the reviewer responds, have Power Automate save the result in a SharePoint column such as ReviewStatus. Add that column to the sFiles file list, and the rep can see the result when they refresh.

A status column shows the decision; it doesn't restrict access. If you need to control publication, use SharePoint content approval. Record which version was approved so later edits don't keep the previous approval.

2. Let the onboarding team know when the paperwork is ready

When an account manager uploads the signed statement of work, the implementation team needs the documents and enough detail to start. A generic "new file uploaded" message isn't much help.

With sFiles, the account manager can upload the documents from the Salesforce record and mark the package ready. A Power Automate flow can check for the required files, add or update an entry in a SharePoint onboarding list, and send a Teams message with the account details and document links.

The account manager keeps working in Salesforce. The implementation team gets links to the files in Teams and can open them in SharePoint, without waiting for someone to forward an email.

3. Remind the right person before a document expires

Insurance certificates and supplier documents often need replacing long after they were uploaded. Add the expiry date to a SharePoint column so your team doesn't have to open each file to check.

With sFiles, you can ask users for the expiry date during upload or map it from a Salesforce field. A scheduled Power Automate flow can check those dates and send reminders to the person responsible.

For example, send a reminder 60 days before expiry, another at 30 days, and an escalation when the document is overdue. Include a link to the Salesforce record or SharePoint file that the recipient can access. They can upload the replacement through sFiles.

Save which reminders have already been sent, and stop them when a document is replaced. Keep the expiry date current. Run the date check on a schedule rather than keeping a single flow waiting for months.

4. Start a review when a Salesforce record changes

Sometimes the file is already uploaded, but the project isn't ready for review yet. You may want the review to start only after an Opportunity changes stage or a project meets its delivery requirements.

With sFiles Enterprise, Salesforce Flow can use our Update SharePoint Columns action to update a field on a specific SharePoint document. Power Automate can watch for that change and start the review or notification.

For example, a Salesforce Flow checks that a project is ready for delivery, finds the handoff document, and sets WorkflowState to Ready. Power Automate then sends the document to operations and posts a Teams message. Pass the correct SharePoint item ID, and use a request ID to help prevent the same change from starting duplicate reviews.

Update SharePoint Columns requires sFiles Enterprise. Record folders and the Set up SharePoint Folder Flow action are included in Standard and Enterprise. Mapping a Salesforce value during upload doesn't automatically keep existing documents up to date when that value changes.

5. Send portal uploads to your review team

Customers and partners can submit documents through Salesforce Experience Cloud with sFiles Enterprise. You can then use Power Automate to send each submission to the person who needs to review it.

For example, a partner uploads a certification document for an application. Set up the flow to check the application details, assign a reviewer, update the review status, and notify the internal team.

Staff can open the documents from the Salesforce application record. When something is missing, a follow-up email can send the partner back to the portal to upload it.

Use the application ID from your configuration, not one the partner can edit. Keep internal review notes and routing fields out of the portal view. Portal upload access is separate from general SharePoint access, and internal notifications should only go to authorized staff.

Which SharePoint columns should you use?

Power Automate needs to know what a document is, which record it belongs to, and whether it's ready for the next step. SharePoint columns can hold that information.

With sFiles, you can fill those columns from Salesforce values and choose which ones users can see or edit. These are example names, not required sFiles fields. Start with the ones your workflow needs.

A value copied during upload isn't automatically kept in sync. Decide which values can stay as they were at upload and which need another update when the record or document changes.

How to set up your first sFiles and Power Automate workflow

Start with one process, such as sending a contract for review and showing the result in sFiles. Use one Salesforce object and one SharePoint library until that process works reliably.

1. Connect the record to SharePoint.

   In sFiles, configure the object's SharePoint location, record folders, upload fields, and visible columns. Test with someone who will use the process.

2. Decide when a document is ready.

   Choose the required fields and a submission status. A file may have been uploaded before the person has finished entering its details.

3. Set up the SharePoint trigger.

   For a review that starts when the status changes, consider When a file is created or modified (properties only). Choose the library and set conditions so the flow proceeds only when the file has the required details and is ready.

4. Add the approval or notification.

   Save the result back to SharePoint. Before processing a file, check its current status and request ID. Configure the flow to handle overlapping runs safely, and keep its own updates from starting the same approval again.

5. Test what happens when something goes wrong.

   Try incomplete uploads, duplicate events, revised documents, rejected approvals, and users without access. Test a failed step and how you'll recover it. Check what appears in sFiles after a refresh.

Metadata may not be ready at the moment a file is created, and flows may not start immediately. Test the timing in your library. For a notification that only needs a link and document details, you don't need to transfer the whole file.

Before you turn it on for the whole team

Test access for everyone involved. The flow runs using its connection account, which may have different access from the person receiving the message. Check both. Sending someone an approval request or Teams link doesn't give them permission to open the file.

Make sure someone owns the flow. Decide who maintains its connections, fixes failed runs, and updates the sFiles configuration. If approvals can take weeks, plan for timeouts and recovery: a cloud-flow run has a 30-day limit, including time spent waiting for approval.