×
Microsoft Graph REST API
MS Graph REST API

Overview

The Microsoft Graph REST API plugin adds a generic node for performing nearly any Graph REST API call.

Functionality

The Security Flow Microsoft Graph REST API plugin provides the ability to call nearly any REST API end-point through the NL-MS-Graph-REST-API node.

Instance Configuration Parameters

Property
Description

Instance Name

Name for the Microsoft Graph REST API plugin instance.


Unique ID

A system-wide unique identifier for this plugin instance used to locate the service.


Authorization (OAuth2)

Application authorization used to access Microsoft Graph services. See the Authorizations (OAuth2) Screen for details on configuring an authorization.

Flow Node

This node provides the capability to call nearly any of the Microsoft Graph REST API end-points. Reference the Microsoft Graph REST API v1.0 reference for the path, request method, query parameters, and body to be configured in this node.
Property
Description

Name

The display name of the node within the flows.


Unique ID

A system-wide unique identifier for this plugin instance used to locate the service.


API Version

When specified, the API Version can be used to select a specific version. If not specified or the evaluated value is not v1.0 or beta, the version will default to v1.0.


Extra Headers

When needed, the Extra Headers must evaluate to a JSON object. The object contains the additional headers as specified by the REST API end-point. If the Extra Headers uses the {} JSON context, mustache template substitution is applied prior to generation of the final JSON object.


Path Segment

The Path Segment defines a mustache template for the URL’s path after the version. The following example sets the path for retrieving a group by ID. The path for getting groups via the MS Graph API with a str context value is /groups/{{payload.groupId}}. If the payload.groupId is 12345678-1234-1234-1234-123456789012, the final URL is https://graph.microsoft.com/[version]/groups/12345678-1234-1234-1234-123456789012, where the version comes from the selected API Version.


HTTP Method

The HTTP Method must evaluate to one of GET, POST, PUT, PATCH, or DELETE. Any other value will cause a non-recoverable failure.


Query Parameters

When needed, the Query Parameters must evaluate to a JSON object or string. When Query Parameters evaluates to an object, the object contains the query parameters (URL parameters) as key-value pairs. Values may include any value convertible to a string. Array values will result in the same key being supplied with each element as a value within the query parameters. When Query Parameters evaluates to a string, it must contain the URL parameters in the key1=value1&key2=value2&...&keyN=valueN format. If the Query Parameters uses the {} JSON context, mustache template substitution is applied prior to generation of the final JSON object.


Body Parameters

When needed, the Body Parameters must evaluate to a JSON object. The object contains the request payload as specified by the REST API end-point. If the Body Parameters uses the {} JSON context, mustache template substitution is applied prior to generation of the final JSON object.

Nevelex Labs, Main Office

Metro Office Park
2950 Metro Drive, Suite 104
Bloomington, MN 55425
Phone: +1 952-500-8921

©Nevelex Labs, LLC. 2018-2022, All Rights Reserved.

EULA