Loading...

How to rename files in SharePoint with Power Automate

How to rename files in SharePoint with Power Automate

the issue

Although SharePoint and Power Automate are heavily interwoven, there is no “rename file” action in Power Automate - if the file lives in a SharePoint library. Out of the box that is only possible for files living in OneDrive.

I recently saw a cry for help on twitter and decided to share here how my solution looks like.

In order to change a filename, we will need to use SharePoint REST API, which is accessible to us in Power Automate via the Send an HTTP request to SharePoint action.

the Power Automate flow

Power Automate flow to rename a file

  1. To make things easy, we start with a For selected file trigger. (In a real-world scenario, you’d typically rename a file after something else has happened.)

  2. We then Get file properties (not needed as we already have the ID from the For selected file trigger, but if you run this after another action you will need the file properties to get the ID so that you can rename the right file).

  3. We now need to use the Send an HTTP request to SharePoint action:

    • Site Adress: choose from Dropdown
    • Method: Get
    • Uri: _api/lists/getbytitle('<DisplayName of your Library goes here>')

    This will re turn the ListItemEntityTypeFullName property, which we will need for the next step.

  4. As a last step, use another Send an HTTP request to SharePoint action:

    • Site Adress: choose from Dropdown
    • Method: Post
    • Uri: _api/lists/GetByTitle('<DisplayName of your Library goes here>')/Items(@{outputs('Get_file_properties')?['body/ID']})
    • Headers:
      • Content-type: application/json
      • IF-MATCH: *
      • X-HTTP-METHOD: PATCH
    • Body:
{'__metadata':
{'type':'@{outputs('Send_an_HTTP_request_to_SharePoint_to_get_type')?['body']?['d']?['ListItemEntityTypeFullName']}'},
'FileLeafRef':'<your new filename goes here>'}

For the type, we are selecting the ListItemEntityTypeFullName property from the output of the previous action. You could also use Parse JSON action to obtain that value.

Conclusion

Once again, the Send an HTTP request to SharePoint action in Power Automate is a lifesaver for everything that doesn’t work with the built-in actions. Also, no additional license than your Microsoft 365 license is required to use it.

Resources

To learn more about SharePoint REST, use these resources:

Feedback & what’s next?

I’d love to know what are your renaming-scenarios and also what you use the Send an HTTP request to SharePoint action for! Let me know on twitter. If you found this blog post useful, please also subscribe to my newsletter - news coming about every 2 months, I promise to not spam you!

Published on:

Learn more
Luise Freese: Consultant & MVP
Luise Freese: Consultant & MVP

Recent content on Luise Freese: Consultant & MVP

Share post:

Related posts

Power Automate Cloud Flow | Disable an action

Did you know you can disable a flow action without removing it entirely by turning on the Enable Static Result toggle? When the flow runs, thi...

12 hours ago

How to Use the “Search Rows (Preview)” Action in Power Automate for Smarter Dataverse Queries

If you often build automation flows in Power Automate, you’ve probably used the “List rows” action to pull data from Microsoft Dataverse. It’s...

1 day ago

10 Types of For Loops Structures in Power Automate

For loops are one of the basic structures in coding. There are however many different types of loops. How can we implement various types of lo...

6 days ago

Power Automate – HTTP and Teams webhook trigger flows are moving to new URLs

As of August 2025, Power Automate flows and Agent flows (Copilot Studio) with HTTP triggers or Teams Webhook triggers that have logic.azure.co...

6 days ago

Power Automate – Automate browsers using direct control without extensions

We are announcing the ability to automate browsers using direct control without extensions in Power Automate. This feature will reach general ...

8 days ago

Power Automate: How to change the run history from 28 days

By default, Power Automate will retain the history of the runs for 28 days. I don’t have direct confirmation of this, but since 28 days transl...

13 days ago

Power Automate for desktop – Assign custom names to actions in desktop flows

We are announcing the ability to assign custom names to actions in desktop flows in Power Automate for desktop. This feature will reach genera...

14 days ago

Power Automate – Enable version control for desktop flows

We are announcing the ability to enable version control for desktop flows, allowing users to identify changes and their origins with version c...

14 days ago

Power Automate – Quantify time and money savings delivered by automations

We are announcing the ability to quantify time and money saved by automations delivered at flow, environment, and tenant level in Power Automa...

16 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy