Use Power Automate to automatically create SharePoint News Links from an RSS feed

[utterances-bot]

Use Power Automate to automatically create SharePoint News Links from an RSS feed

There’s a blog for that A somewhat common complaint I’ve heard from organizations I’ve worked with is that folks within the organization frequently are unaware of press releases, blogs, or other information the organization is publicly sharing.

https://pnp.github.io/blog/post/use-power-automate-to-automatically-create-sharepoint-news-links/

[cameronstewart]

Throws and error on Correct to include a valid reference to 'Get_Thumbnail' for the input parameter(s) of action 'Initialize_variable'.

[cameronstewart]

Worked it out, was just how variables were named.

[augustlevinson]

Is there a way to always have the same image as a default in the thumbnail? In those cases there is no thumbnail in the original post.

[crgklr]

@cameronstewart Can you elaborate? Im stuck and getting the same error

[KnutPetterDimmen]

@crgklr you have to name the Send an HTTP request to SharePoint action "Get Thumbnail"

[auslagger]

Im guessing this only works if the page is public?

i have a RSS feed for a members only area/site given its not public, im assuming this wont work as microsoft cant 'get' the images or content

[NashSUPINFO]

Hello, when i run the test, i get an error 400 : A node of type 'StartArray' was read from the JSON reader when trying to read the start of an entry. A 'StartObject' node was expected. for the Create News Link.

Also do u have a For each for the compose ? Power Automate created one automatically for me.

[jakemannion]

It appears (for me, anyways) that encoding the URL before calling SharePoint's api is no longer needed / viable.

Put the method described in this article in place a few years ago (THANK YOU) and it ran fine for a year or two. Went to revive it today, and it would not run unless I skipped the encoding and %27 wrapping steps.

Endpoint call working today looks like:

_api/SP.Publishing.EmbedService/EmbedData?url='YOUR PRIMARY LINK HERE, UNENCODED'&version=1&bannerImageUrl=true

[Tyr03]

It appears (for me, anyways) that encoding the URL before calling SharePoint's api is no longer needed / viable.

Put the method described in this article in place a few years ago (THANK YOU) and it ran fine for a year or two. Went to revive it today, and it would not run unless I skipped the encoding and %27 wrapping steps.

Endpoint call working today looks like:

_api/SP.Publishing.EmbedService/EmbedData?url='YOUR PRIMARY LINK HERE, UNENCODED'&version=1&bannerImageUrl=true

Very interesting thanks. Could you elaborate a bit cause I don't really get that part :

I skipped the encoding and %27 wrapping steps.

What step did you removed and wich one did you modify for the endpoint call ?

[ILSua]

Legend. Thanks for this. And perfect detail to replicate. Appreciate you.

[jakemannion]

What step did you removed and wich one did you modify for the endpoint call ?

Went to take a look yesterday and could not find the modification I alluded to. Waiting on a DLP adjustment so I can re-edit the flows in question. Will report back if my earlier comment about reshaping the SP endpoint URL was nonsense (or not).