SharePoint Integration

Business Background

The SharePoint integration in Titan Flow enables you to upload files directly from Salesforce, a web portal, or after signing a contract to your SharePoint document libraries. This integration helps organizations reduce Salesforce file storage costs and share documents with users who do not have access to Salesforce.

You can easily connect your Microsoft account and automate file uploads to SharePoint, ensuring a secure and reliable document management process across both platforms.

Titan Solution

The SharePoint integration in Titan Flow provides a direct, no-code connection between Salesforce and SharePoint. It allows users to automatically upload and store files as part of any Flow process, whether triggered by Salesforce records, web portals, or e-signature actions. By removing the need for third-party middleware or manual uploads, Titan delivers a secure and efficient document management experience across both systems.

When to Use this Integration

Use the SharePoint integration if you want to:

• Store Salesforce files in SharePoint to save Salesforce storage space.
• Make files accessible to users outside Salesforce.
• Automate document uploads as part of Flow processes.

Before You Begin

Ensure you have:

• A valid Microsoft 365 account with access to SharePoint Online.
• Access permissions to the desired site, library, and folder in SharePoint.
• A Titan license that includes Titan Flow.

SharePoint File Upload with Titan Flow

How to Guide

Learn how to connect Titan Flow to SharePoint and upload your files automatically.

Authentication Setup

You can authenticate your SharePoint account from either the Titan Dashboard or directly within your Flow project.

Option 1: Authenticate from Titan Dashboard 

1. Go to Titan Dashboard > Settings > Integrations.
2. Find SharePoint in the list.
3. Click Authenticate.

4. Sign in with your Microsoft account when prompted.

After successful authentication, the integration status will display Authenticated.

You can revoke access at any time using the Revoke button.

Option 2: Authenticate from the SharePoint Action node

1. In your Flow project, add a SharePoint action node.

2. On the SharePoint API Call screen, click Authenticate.

3. Sign in with your Microsoft account to complete the setup.

Note: You can authenticate from either location, but revoking access is only available from the Titan Dashboard under Settings > Integrations.

How SharePoint Authentication Works

This diagram shows how Titan securely connects to Microsoft when you authenticate with SharePoint. Titan receives a short-lived authorization code from Microsoft, exchanges it for a refresh token, and securely stores that refresh token. Titan then uses the refresh token to generate access tokens as needed, allowing your flows to make SharePoint requests without requiring re-authentication.

Add the SharePoint Action Node in Flow

Configure the SharePoint Node in your Flow to set up File Uploads.

1. Open your Flow project in Titan Builder.
2. Click +, choose SharePoint, and select Next.

3. In the Select Action dropdown, choose Upload Files. 
4. Under Select Files Variables, use the dropdown to select the files variables that contain the files you want to upload.
5. Click Add Var to create a new Files Variables in the Files section of the Custom Variables modal. This step is optional.
6. You can also rename the node at the top of the window to make it easier to identify in your Fow.
   This step is optional; the default node name is SharePoint API Call.

7. Click the Configurations tab in the SharePoint action node. 
8. Under Site Name, use the dropdown to select the SharePoint site connected to your authenticated Microsoft account. 
9. Under Library Name, choose the document library where the file should be uploaded. The list displays all available libraries within the selected site. 
10.  In the Folder Name, choose where to store your uploaded file.  
    • Root – Uploads the file to the root directory of the selected library.
    • Field – Uses a variable value (for example, from Salesforce or a Titan form) to dynamically determine the folder name.
    • Static – Lets you type the folder name directly. 
      
      You can also create a path to a subfolder by typing the full path. For example, entering “UploadToSharePoint/2025” will store the file within the “2025” folder located in the “UploadToSharePoint” directory.
      
      Tip: Folder names are case-sensitive. Make sure the path matches the folder structure in SharePoint exactly.
11. Under Store File(s) Link(s) To, choose a static variable to store the returned file links. This step is optional.
12. Under Store ID(s) Link(s) To, choose a static variable to store the returned file IDs. This step is optional.
    • The returned File Link and File ID can be stored in variables for later use (for example, to update Salesforce records).
13. Click Update to save your configuration.

Error Handling

Integration Logs

Known Limitations

• Manual path entry is supported but not recommended.
• Some libraries or folders with special characters in names may not display correctly.
• If a SharePoint site or folder is deleted, uploads fail until the configuration is updated.

Troubleshooting