Skip to content

Latest commit

 

History

History
158 lines (103 loc) · 6.98 KB

File metadata and controls

158 lines (103 loc) · 6.98 KB

Power Automate SharePoint HTTP Request Cookbook

(in the making)

power-automate-sharepoint-http-request-cookbook license power-automate-sharepoint-http-request-cookbook forks power-automate-sharepoint-http-request-cookbook stars power-automate-sharepoint-http-request-cookbook issues power-automate-sharepoint-http-request-cookbook pull-requests

· Report Bug · Request Feature · Submit Expression ·


Index

Here are the sections that we have so far:


Introduction

I'm compiling a list of all SharePoint endpoints that I find helpful, and I think you may too. I'm focusing on Power Automate with the Send an HTTP request to SharePoint action, but you can use them with other tools.

If you have any questions on how to use them, please go to Power Automate: Get dynamic information from SharePoint, where I do my best to explain the concepts and provide examples.


Concepts

Here are some essential things to understand before going forward.

What is an endpoint?

It's a good question :). Of course, I'm going to oversimplify since this reference isn't intended for CS majors but for everyone that wants to automate their tasks using Power Automate. Still, an endpoint is something that facilitates the communication between two entities.

We're using SharePoint (the first entity), where we want to fetch data using Power Automate (the second entity). Power Automate will use an URL (the "endpoint") to bring the information.

In our case, the endpoints are URLs with a structure that return information, so we can't change them. When we "ask" something (send a request using the "Power Automate: Send an HTTP request to SharePoint Action") we get information from SharePoint in JSON format (see next section).

Since Power Automate provides the “Power Automate: Send an HTTP request to SharePoint Action” some of the complexity is hidden, so we consider the endpoint as everything that comes after "https://<your site>.sharepoint.com/", like:

power-automate-sharepoint-http-request-cookbook pull-requests

Behind the scenes, the request will be sent to SharePoint like this, for example:

https://manueltgomescom.sharepoint.com/sites/Test/_api/web/lists/

Again, I'm oversimplifying this but what's important is that you understand the overall concept.

Back to the index

What is JSON?

It's a pretty broad question, and there are millions of pages, videos, and other resources explaining what it is. I won't replicate them here, but it would be helpful to understand at least the fundamentals to take full advantage of the information provided by the endpoints.

Back to the index


Lists

Here you can find some endpoints related to lists.

Get all lists for a SharePoint site

The endpoint is quite simple.

power-automate-sharepoint-http-request-cookbook pull-requests

_api/web/lists/

You'll get something like this:

power-automate-sharepoint-http-request-cookbook pull-requests

Back to the index

Find a list

If you don't know the ID of the list, you can still find it by name:

power-automate-sharepoint-http-request-cookbook pull-requests

\_api/web/lists/getbytitle('employee')

Please note that we're searching for one list with that name. If the list doesn't exist, the Flow will fail. So please be sure that the list exists or that you deal with errors accordingly.

Back to the index

Get the columns for a list

power-automate-sharepoint-http-request-cookbook pull-requests

_api/web/lists/getbytitle('employee')/Fields

Back to the index


🙏 Thanks to

Thanks to everyone that reached out. If you submit anything, you'll get your name here :).

Back to the index


💪 Contributing

Submissions are always welcome, so please Submit a new recipe. I'll check it, but please accompany it always with a bit of explanation so that people know how to use it and what kind of information we're looking for.


Made in ☀️ Portugal with ❤️