Power Automate: SharePoint - Get file properties Action
Returns a SharePoint file's library column values. Needs the integer item ID, not the file identifier.
Welcome to my Power Automate hub, where I share what I have learned building real cloud flows for work and for fun. If you have ever stared at a flow that almost works, this is where you fix it. You will find practical, hands-on guides that go beyond the basics and tackle the messy parts of automation. I cover advanced error handling patterns so your flows fail gracefully, and I dig into API rate limits and throttling, including batch operations and throttling mitigation, so your flows keep running when you scale up. I walk through building a website monitor from scratch, handling CSV files without losing your mind, and troubleshooting dynamic content when the values you expect simply are not there. My best practices for SharePoint across multiple environments save painful mistakes, and my approval workflow guide makes one of the most requested features easy to understand.
Returns a SharePoint file's library column values. Needs the integer item ID, not the file identifier.
Returns the trigger's entire output object, headers included. The body sits one level down.
Subtracts an interval from a timestamp you supply. Returns a string; months clamp to month end.
Returns the body output of a named action. Names use underscores for spaces and are case-sensitive.
Detects which column changed on a list item and reads the old value from version history. Requires versioning.
Joins an array into a single string with the delimiter you choose. An empty array returns an empty string.
Returns the current timestamp minus a number of time units. Always counts back from now in UTC.
Returns the full message behind a message ID: body, sender, mentions, and reactions. The body arrives as HTML.
Splits a string or array into pieces of a fixed size. The last chunk is often shorter.
Converts a base64-encoded string into binary file content. The content type changes; the base64 does not.
A connection stores credentials; a connection reference is a named pointer to one, living inside a solution.
Convert a solution flow from a direct connection to a connection reference and unlock the new designer.