Generate Images from SharePoint List Items with Make and RenderForm

If you repeatedly make the same banner with different text and pictures, store the changing values in SharePoint and let a template renderer produce the image.

This is deterministic image generation, not generative AI. The layout stays fixed. Only the fields you map are replaced.

What the workflow does

The reliable shape is:

SharePoint list item -> Make scenario -> RenderForm template -> image URL -> SharePoint item

RenderForm's current API documentation accepts a template identifier and a data object, then returns a request ID and rendered-file URL. Make documents a SharePoint Watch Items module.

1. Design the SharePoint list

Create explicit columns rather than one large instruction field: Headline, Subtitle, Source image URL, Status, Rendered image URL and Error detail. Use Status values of Draft, Ready, Processing, Complete and Error.

The status is the automation gate. It prevents every small edit from generating another image.

2. Build the RenderForm template

Create the layout in RenderForm and give each editable component a clear identifier. Test it with long and short sample values.

Record the template ID and exact property names. RenderForm's API uses mappings such as headline.text and photo.src. Your identifiers depend on the template.

Keep the API key in Make's secured connection or credential field. Do not store it in SharePoint, a browser URL or the article body. RenderForm also documents signed requests for cases where a generated URL must be exposed without revealing the API key.

3. Create the Make scenario

1. Add Microsoft SharePoint Online > Watch Items.
2. Choose the site and list, and filter for Status = Ready.
3. Update the item to Processing before rendering.
4. Add the RenderForm module if it is available. Otherwise use Make's HTTP app to call POST https://get.renderform.io/api/v2/render.
5. Map the SharePoint fields to the template properties.
6. Store the returned href in Rendered image URL and set Status to Complete.
7. Add an error handler that records the error and sets Status to Error.

4. Test before scaling

Test missing images, oversized text, special characters and an invalid template ID. Confirm that a failed render is visible in SharePoint and does not leave an item stuck at Processing.

Check licensing, operations and retention on the live vendor pages before estimating cost. The old article quoted plan allowances that can change and should not be treated as current.

Power Automate can also watch the list and call the API through an HTTP-capable route, but licensing and policy depend on your environment. If Make is already approved, it may be quicker. If your organisation standardises on Power Platform, assess the connector and data-policy implications first.

Want help designing the status model and failure handling? Join Power Automate Builders.