SharePoint Images in Power Automate

Key insights

• Image column problem: SharePoint image columns often do not appear in Power Automate’s dynamic content.
  That happens because the standard Get item output lacks the image metadata you need.
• Core workaround: create a flow that uses Get item to fetch the list record, then call Send an HTTP request to SharePoint.
  This custom API call exposes the image field JSON that the standard actions hide.
• API call details: build the REST request with _api/lists/getbytitle() and include the internal field name for the image column.
  Find the internal column name in list settings or the Get item output to target the correct property.
• Extract the file info: parse the returned JSON to get the fileName or the serverRelativeUrl.
  Use that value with Get file content using path to retrieve the actual image binary.
• Use the image: once you have file content, attach it to emails or insert it into documents and approvals.
  Test the flow end‑to‑end and reuse the same pattern in other flows.
• Practical tips: the image column stores structured JSON (fields like type, fileName, and serverRelativeUrl) so inspect outputs with a Compose action.
  Images uploaded via Power Apps can be large (up to about 90 MB), so pick the right retrieval action and test for performance.

Overview of the video

The YouTube video from Pragmatic Works, presented by Andrew Perez, walks viewers through a practical fix for a common integration problem between SharePoint and Power Automate. The short tutorial explains why an Image column does not appear as ordinary dynamic content and then shows a reliable workaround. Consequently, the video focuses on using a small sequence of actions and a direct SharePoint API call to extract image metadata and retrieve the actual image file.

Along the way, the presenter demonstrates an instant cloud flow that reads a list item, performs an HTTP call to SharePoint, and then uses file actions to attach images to emails. Therefore, the pattern is useful when you need real image bytes rather than the JSON metadata that Power Automate often exposes. The approach is practical for scenarios like product photos, inspection evidence, or profile images where embedding the actual file matters.

The core problem explained

SharePoint’s modern Image column stores image details as structured JSON instead of a simple URL, and that is why the value does not show up in Power Automate’s dynamic content panel. Specifically, the standard Get item output lacks the readable metadata most actions expect, so the image file name and server path are hidden. As a result, flows that only use built-in connectors can’t directly pull the file binary from that JSON without extra steps.

Moreover, certain actions and templates, such as some Word templates or third-party connectors, still fail to accept the Image column value directly. Consequently, users who try to paste the JSON into a document or email may only see text, not an embedded picture. The video emphasizes that understanding how SharePoint stores the image is key to choosing the right retrieval method.

Step-by-step pattern shown

First, Andrew Perez creates an instant cloud flow and uses Get item to fetch the SharePoint record. Next, he adds a Send an HTTP request to SharePoint action to call the REST API and request the image column metadata by name, because the standard output does not include it. He explains how to build the correct _api/lists/getbytitle() call and why locating the column’s internal name matters for a successful request.

Then, the demo extracts the file name from the returned JSON using a simple compose expression so the flow can identify the image path. After that, it uses Get file content using path to retrieve the image bytes from SharePoint and finally attaches the file to an email action. The presenter runs a test and shows the final email with the image attached, confirming the pattern works end to end.

Finally, the video points out that this sequence—pull item, call API, parse JSON, get file content, attach—can be reused in other flows. Therefore, viewers can adapt the same steps to different lists or image fields by changing the API path and internal column name. The presenter also highlights small practical checks, such as verifying server-relative URLs and testing with different list structures.

Trade-offs and common challenges

Relying on a direct API call to SharePoint introduces both benefits and trade-offs, and the video touches on several of them. On the plus side, the API call gives precise access to metadata and file locations that connectors omit, but it also adds complexity because flows must handle raw JSON and potential permission constraints. Consequently, administrators should understand that this method needs correct site permissions and sometimes higher maintenance than purely connector-based solutions.

Performance and limits are other considerations: retrieving many images or very large files in a single flow can slow processing and approach connector or service limits. Additionally, using the REST API ties flows more closely to SharePoint’s internal structure, which means column internal names or storage locations might change over time and break the flow. Therefore, teams should balance immediate functionality against long-term maintainability.

Practical recommendations

For teams implementing this pattern, the video suggests practical best practices such as caching column internal names in a configuration list and building clear error handling for missing files. Also, it helps to test with a few representative items to confirm server-relative paths and to consider size limits before scaling up. In addition, documenting the API calls and parsing logic reduces risk when updates are needed later.

In conclusion, the Pragmatic Works tutorial supplies a clear, reusable pattern to extract images from a SharePoint Image column into Power Automate flows. While the approach trades simplicity for control, it solves a frequent blocker for automation projects and can be adapted with proper permissions, monitoring, and governance in place.

Keywords

SharePoint image column Power Automate, Get image from SharePoint in Power Automate, SharePoint image column to Flow, Power Automate handle SharePoint image field, Fix SharePoint image column Power Automate, SharePoint online image column flow tutorial, Convert SharePoint image column to file Power Automate, Power Automate retrieve image from SharePoint list