Power Platform Community Forum Thread Details

I am attempting to build a Power Automate workflow that automatically sends email notifications to both my internal SLTP team and an external vendor (CSI) whenever a client uploads a file to a designated OneDrive folder.

The target folder is: SLTP External Share → SLTP ABF Direct Client Portal → Files From Client-2026

This workflow is critical for ensuring timely notification to CSI, as they do not receive native alerts when files are uploaded to OneDrive and rely on email communication to begin their processing.

Steps Taken

Created an automated cloud flow using:
- Trigger: OneDrive for Business – When a file is created (properties only

Configured the folder path as

/SLTP External Share/SLTP ABF Direct Client Portal/Files From Client-2026/

Added actions to:
- Send internal notification email to SLTP team
- Send external notification email to CSI inbox

Tested the flow by uploading files into the target folder

Expected Outcome

When a file is uploaded into the Files From Client-2026 folder:

The flow should trigger automatically

An email should be sent to:
- Internal SLTP team (for visibility)
- CSI (to begin processing)

Actual Outcome

The flow fails at the trigger step

No emails are sent

Run history shows a failure on the trigger

Error Messages

Action 'When_a_file_is_created_(properties_only)' failed

Invalid fileId
clientRequestId: 1a220b4d-3f4d-4f0d-a420-3fa00ed8a7ab
serviceRequestId: 6f951ea2-5098-1000-c281-e6648b5dc8e4

Additional details from the flow configuration:

 
 
"host": {
"connectionReferenceName": "shared_onedriveforbusiness",
"operationId": "OnNewFileV2"
},
"parameters": {
"folderId": "/SLTP External Share/SLTP ABF

Categories:

Building flows

@DM-17062001-0

The Invalid folderId error happens because the trigger expects a folder ID internally, not a folder path. When you type or paste the path manually instead of selecting the folder through the folder picker UI, Power Automate stores the raw path string as the folderId, which is invalid.

The fix is straightforward. Delete the trigger and recreate it. When you get to the folder field, use the folder picker (the browse button) to navigate to and select the folder rather than typing the path manually. This way Power Automate stores the actual internal folder ID behind the scenes, which is what the OneDrive connector needs.

One important note for your setup: the folder name "SLTP External Share" suggests this may be a shared folder that belongs to someone else's OneDrive. The OneDrive for Business connector only reliably monitors folders in your own OneDrive. If the folder is shared from another user's OneDrive, the trigger will not work regardless of the path. If that is the case, the proper solution is to move the folder into a SharePoint document library and use the SharePoint trigger instead, which is built for shared collaborative scenarios.

https://manueltgomes.com/reference/power-automate-trigger-reference/onedrive-for-business-when-a-file-is-created-properties-only-trigger