Can I use Microsoft Entra ID (Azure Active Directory)’s API with n8n?

Yes, with n8n, you can programmatically interact with Microsoft Entra ID (Azure Active Directory)’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.

Can I use Token Metrics’s API with n8n?

Yes, with n8n, you can programmatically interact with Token Metrics’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.

Is n8n secure for integrating Microsoft Entra ID (Azure Active Directory) and Token Metrics?

Yes, it is safe to use n8n to integrate Microsoft Entra ID (Azure Active Directory) and Token Metrics. n8n offers various features to ensure the safe handling of your data. These include encrypted data transfers, secure credential storage, RBAC functionality, and compliance with industry-standard security practices (SOC2 compliant). For hosted plans, data is stored within the EU on servers located in Frankfurt, Germany. You can also host it on your own infrastructure for added control. Learn more about n8n’s security practices here.

Back to Integrations

Microsoft Entra ID (Azure Active Directory)

Token Metrics

Microsoft Entra ID (Azure Active Directory) node

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

Save yourself the work of writing custom integrations for Microsoft Entra ID (Azure Active Directory) and Token Metrics and use n8n instead. Build adaptable and scalable Cybersecurity, and AI workflows that work with your technology stack. All within a building experience you will love.

Get started

See n8n in action

How to connect Microsoft Entra ID (Azure Active Directory) and Token Metrics

Step 1: Create a new workflow
Step 2: Add and configure nodes
Step 3: Connect
Step 4: Customize and extend your integration
Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration: Create a new workflow and add the first step

Step 2: Add and configure Microsoft Entra ID (Azure Active Directory) and Token Metrics nodes using the HTTP Request nodes

You can find the Microsoft Entra ID (Azure Active Directory) node in the nodes panel and drag it onto your workflow canvas. It will be added as the HTTP Request node with a pre-configured credential type. To add the Token Metrics app to the workflow, select the HTTP Request node and use a generic authentication method. The HTTP Request node makes custom API calls to Microsoft Entra ID (Azure Active Directory) and Token Metrics. Configure Microsoft Entra ID (Azure Active Directory) and Token Metrics nodes one by one: input data on the left, parameters in the middle, and output data on the right.

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration: Add and configure Microsoft Entra ID (Azure Active Directory) and Token Metrics nodes using the HTTP Request node

Step 3: Connect Microsoft Entra ID (Azure Active Directory) and Token Metrics

A connection establishes a link between Microsoft Entra ID (Azure Active Directory) and Token Metrics (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration: Connect Microsoft Entra ID (Azure Active Directory) and Token Metrics

Step 4: Customize and extend your Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect Microsoft Entra ID (Azure Active Directory) and Token Metrics with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration: Customize and extend your Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

Step 5: Test and activate your Microsoft Entra ID (Azure Active Directory) and Token Metrics workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Microsoft Entra ID (Azure Active Directory) and Token Metrics or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration: Test and activate your Microsoft Entra ID (Azure Active Directory) and Token Metrics workflow

Build your own Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

Create custom Microsoft Entra ID (Azure Active Directory) and Token Metrics workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Supported API Endpoints for Microsoft Entra ID (Azure Active Directory)

Users
Groups
Applications
Groups Members

List Users

Retrieve a list of user objects.

GET

/users

Create User

Create a new user.

POST

/users

Get User

Retrieve the properties and relationships of user object.

GET

/users/{userId}

Update User

Update the properties of a user object.

PATCH

/users/{userId}

Delete User

Delete a user.

DELETE

/users/{userId}

To set up Microsoft Entra ID (Azure Active Directory) integration, add the HTTP Request node to your workflow canvas and authenticate it using a predefined credential type. This allows you to perform custom operations, without additional authentication setup. The HTTP Request node makes custom API calls to Microsoft Entra ID (Azure Active Directory) to query the data you need using the URLs you provide.

See the example here

Take a look at the Microsoft Entra ID (Azure Active Directory) official documentation to get a full list of all API endpoints

List Groups

Retrieve a list of group objects.

GET

/groups

Create Group

Create a new group.

POST

/groups

Get Group

Retrieve the properties and relationships of a group object.

GET

/groups/{groupId}

Update Group

Update the properties of a group object.

PATCH

/groups/{groupId}

Delete Group

Delete a group.

DELETE

/groups/{groupId}

See the example here

Take a look at the Microsoft Entra ID (Azure Active Directory) official documentation to get a full list of all API endpoints

List Applications

Retrieve a list of application objects.

GET

/applications

Create Application

Create a new application.

POST

/applications

Get Application

Retrieve the properties and relationships of an application object.

GET

/applications/{applicationId}

Update Application

Update the properties of an application object.

PATCH

/applications/{applicationId}

Delete Application

Delete an application.

DELETE

/applications/{applicationId}

See the example here

Take a look at the Microsoft Entra ID (Azure Active Directory) official documentation to get a full list of all API endpoints

List Group Members

Retrieve a list of the members of a group.

GET

/groups/{groupId}/members

Add Group Member

Add a member to a group.

POST

/groups/{groupId}/members/$ref

Get Group Member

Retrieve a member of a group.

GET

/groups/{groupId}/members/{memberId}

Remove Group Member

Remove a member from a group.

DELETE

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

Update Group Member

Update the properties of a group member.

PATCH

/groups/{groupId}/members/{memberId}

See the example here

Take a look at the Microsoft Entra ID (Azure Active Directory) official documentation to get a full list of all API endpoints

Supported API Endpoints for Token Metrics

To set up Token Metrics integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Token Metrics to query the data you need using the API endpoint URLs you provide.

List tokens

Get the list of coins and their associated TOKEN_ID supported by Token Metrics.

GET

/v2/tokens

These API endpoints were generated using n8n

n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the Token Metrics official documentation to get a full list of all API endpoints and verify the scraped ones!

Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

How to connect Microsoft Entra ID (Azure Active Directory) and Token Metrics

Step 1: Create a new workflow and add the first step

Step 2: Add and configure Microsoft Entra ID (Azure Active Directory) and Token Metrics nodes using the HTTP Request nodes

Step 3: Connect Microsoft Entra ID (Azure Active Directory) and Token Metrics

Step 4: Customize and extend your Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

Step 5: Test and activate your Microsoft Entra ID (Azure Active Directory) and Token Metrics workflow

Build your own Microsoft Entra ID (Azure Active Directory) and Token Metrics integration

Supported API Endpoints for Microsoft Entra ID (Azure Active Directory)

Supported API Endpoints for Token Metrics

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n

These API endpoints were generated using n8n