This action allows you to make a custom, authenticated HTTP call to the microsoft graph API.
NOTE: This is not like any of the other Sharepoint cards; this card shows some of what goes on behind the scenes on other cards. If you have no experience working with API calls this may be a challenge, however this card is highly customizable. Good luck, and it may help if you refer to the documentation!
Options
Relative URL (text): the address on the web server you are attempting to interact with. Relative URL means that you don’t have to explicitly specify the protocol at the beginning of the URL (such as “http://“). This suggests to the web server that the interaction is occurring on the server (in this instance).
Example: sites/<baseUrl>.sharepoint.com,<SomeID>,<ID>/lists/<ListID>/items
Query (object or text): JSON object that determines the action taken at the URL.
Example: {"name":"something-urgent"}Headers (object): JSON that determines the content type of the request. This will usually be a replica of the example below.
Example: {"Content-type":"application/json"}
Output Data
Status Code (Number): the success or failure of your HTTP request. Here is a list of all status codes.
Headers (object): a more detailed context for the response/status code that doesn’t relate to the output body. Not all headers that appear in a response header are response headers, meaning that some are unlikely to be useful to you.
The response headers are dependent on the HTTP request you choose in options.
- Body (object): depending on the HTTP request you chose in Options, you may receive some data back. That data, such as the data from a GET request, will be contained in this Body object.
))
