SharePoint - Upload File

What it does

Upload one HighLevel File Upload value to an approved SharePoint document library, preserving the original filename when File Name is left blank.

Upload File is the one action with a binary transit exception. The file bytes pass through a stateless Merxence-operated Cloudflare Worker only for transfer to the Microsoft upload session; the application does not persist the file or Microsoft token.

When to use it

Save a file submitted through HighLevel into SharePoint.
Move a workflow file into the organization's Microsoft 365 document system without creating vendor file storage.

Save a file submitted through HighLevel into SharePoint.

Requirements

A connected Microsoft 365 connection for this HighLevel Location.
The Drive ID of the approved SharePoint document library.
Exactly one HighLevel File Upload download value.
A file no larger than 250 MiB; existing destination names are not overwritten.

Inputs

Action inputs
Input	Type	Required	Description	Example value
`Document Library (Drive ID)`	string	Yes	Microsoft Graph Drive ID for the SharePoint document library. The Drive ID identifies the library itself and can be reused across workflow actions.	`b!exampleDriveId123`
`Destination Folder Path`	string	No	Destination folder inside the selected document library, for example Archive/2026. Do not include the document library name. Leave empty to use the document library root.	`Archive/2026`
`File Upload Value`	string	Yes	Map one HighLevel File Upload custom field using the Custom Value Picker, or supply its LeadConnector HTTPS download link. One file; maximum 250 MiB.	`HighLevel File Upload custom value (one file)`
`File Name`	string	No	Optional. Leave blank to preserve the original uploaded filename.	`Example-Brief.pdf`

Example values

Document Library (Drive ID): b!exampleDriveId123
Destination Folder Path: Archive/2026
File Upload Value: HighLevel File Upload custom value (one file)
File Name: Example-Brief.pdf

Example workflow

Example action workflow

HighLevel workflow trigger
The business event that starts the workflow.
SharePoint - Upload File
Run the SharePoint operation with the approved Drive ID and action-specific inputs.
Use the confirmed result
Map only the documented outputs required by the next workflow step.

A proven pattern is: HighLevel Form/File Upload → Upload File → SharePoint → use the returned Item ID, Item Name, and Web URL in later steps.

Outputs

Action outputs
Output	Type	Description	Example value	Use in later steps
`Success`	boolean	Confirms that the action completed successfully.	`true`	Use as a completion checkpoint before relying on other outputs.
`Item ID`	string	Microsoft Graph DriveItem ID of the resulting file or folder.	`example-uploaded-file-id`	Map into Get Item, Move Item, Rename Item, Delete Item, or other ID-based steps.
`Item Name`	string	Current name of the file or folder.	`Example.png`	Use for confirmation, messages, or later naming logic.
`Item Size`	numerical	Verified uploaded item size in bytes.	`68`	Use to confirm the resulting uploaded size.
`Web URL`	string	SharePoint web link for the resulting file or folder.	`https://example.invalid/Documents/Example.png`	Use when a later step or staff member needs the SharePoint link.
`Parent Item ID`	string	DriveItem ID of the resulting parent folder.	`example-parent-folder-id`	Use when later logic needs the resulting parent folder ID.

How to use outputs in later HighLevel steps

Success: Use as a completion checkpoint before relying on other outputs.
Item ID: Map into Get Item, Move Item, Rename Item, Delete Item, or other ID-based steps.
Item Name: Use for confirmation, messages, or later naming logic.
Item Size: Use to confirm the resulting uploaded size.
Web URL: Use when a later step or staff member needs the SharePoint link.
Parent Item ID: Use when later logic needs the resulting parent folder ID.

Use Item ID for later SharePoint actions and Web URL when staff need the resulting document link. Item Size is verified against the uploaded SharePoint item.

Permissions required

Microsoft Graph application permission Sites.Selected on the customer-owned Entra app.
The SharePoint site containing the document library must grant the app at least write access for this operation.
The action does not require tenant-wide SharePoint access merely for discovery or name matching.

Common errors

Authentication unavailable / 401: This HighLevel Location does not have a usable Microsoft connection. Verify the Location connection before changing SharePoint permissions.
403: The Entra app lacks access to the selected SharePoint site or the granted role is too narrow for the operation. Verify Sites.Selected consent and the site's write grant.
404: The Drive ID, folder path, or Item ID does not resolve in the connected tenant and approved site. Recheck the administrator's Drive ID map and the exact path or Item ID.
409: A destination name or state conflicts with an existing SharePoint item. Inspect the destination and choose the intended duplicate/conflict behavior before retrying.
429: Microsoft Graph throttled the request. Retry later and avoid high-volume loops without bounds.

Product/action version

Product version: Pre-launch technical release · 2026-10-04
Action version: 1.5
Implementation reference: Integration commit 8440a0f · src/modules/workflows/actions/sharepoint-upload-file.json · code/sharepoint_upload_file.1.5.js

Last updated

2026-10-07