Overview

The Microsoft MS Graph node allows you to interact directly with the Microsoft Graph API.

This enables you to automate actions within:

• Entra ID (Azure AD)

• Outlook / Mail

• Teams

• SharePoint

• OneDrive

? Perfect for building automations around users, groups, emails, and files.

When to Use This Node

Use this node when you want to:

• Retrieve users from Entra ID

• Manage groups and memberships

• Send or read emails

• Work with Teams or channels

• Access SharePoint or OneDrive files

• Build custom Microsoft integrations

Configuration

The MS Graph node consists of 3 main sections:

1. Authentication

To connect with Microsoft Graph, you need an Azure App Registration.

Required Fields

Tenant ID

Your Azure tenant ID.

Client ID

The Application (client) ID from Azure.

Client Secret

The secret created in your App Registration.

Permissions

Make sure your app has the correct API permissions in Azure, for example:

• User.Read.All

• Group.Read.All

• Mail.Read

• Mail.Send

? Admin consent is usually required.

How It Works

Flowmage automatically:

• Requests an access token

• Uses it in API calls

• Refreshes it when needed

2. Request

This is where you define your API call.

HTTP Method

Choose the request type:

• GET → Retrieve data

• POST → Create data

• PATCH → Update data

• DELETE → Remove data

Version

Choose the Graph API version:

• v1.0 → Stable (recommended)

• beta → Experimental

Resource

Defines the endpoint.

Examples:

• users

• groups

• me/messages

• teams

Query Parameters

Optional filters and selections.

Examples:

$select=id,displayName,mail
$filter=accountEnabled eq true

API Endpoint Preview

Flowmage automatically builds the full endpoint:

https://graph.microsoft.com/v1.0/users

Continue on Error

If enabled, the flow continues even when the request fails.

3. Headers

Add custom headers if needed.

Example:

ConsistencyLevel: eventual

? Required for advanced queries like $count.

4. Body

Used for POST or PATCH requests.

Content Type

Usually:

application/json

Example Body (Create User)

{
  "accountEnabled": true,
  "displayName": "John Doe",
  "mailNickname": "johndoe",
  "userPrincipalName": "johndoe@company.com",
  "passwordProfile": {
    "forceChangePasswordNextSignIn": true,
    "password": "TempPass123!"
  }
}

How It Works

1. Flow reaches the MS Graph node

2. Flowmage authenticates with Azure

3. API request is executed

4. Response is returned

5. Data becomes available for next nodes

Output / Variables

The response is available using your Output ID.

Example:

@know.value@

? Example (loop users):

@know.value[0].displayName@

Example Use Cases

Get All Users

Method: GET  
Resource: users  
Query: $select=id,displayName,mail

Get Single User

Resource: users/@trigger.userId@

Send Email

Resource: users/@userId@/sendMail  
Method: POST

Add User to Group

POST /groups/{groupId}/members/$ref

Common Mistakes

❌ Missing Permissions

API returns 403.

✅ Add correct permissions + admin consent

❌ Wrong Resource Path

Endpoint not found.

✅ Double-check Graph endpoint structure

❌ Using Beta Without Need

Unstable behavior.

✅ Use v1.0 when possible

❌ Missing Headers for Advanced Queries

Query fails.

✅ Add:

ConsistencyLevel: eventual

Pro Tips

• Use $select to reduce response size

• Use $filter to limit results

• Combine with loops for bulk processing

• Use variables for dynamic endpoints

• Enable logging when debugging

Summary

The Microsoft MS Graph node gives you full access to the Microsoft ecosystem via API.

With flexible request configuration and automatic authentication, you can build powerful automations for users, emails, files, and more.