> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams.md).

# Microsoft Teams

Learn how to use the Microsoft Teams node in n8n. Follow technical documentation to integrate Microsoft Teams node into your workflows.

Use the Microsoft Teams node to automate work in Microsoft Teams, and integrate Microsoft Teams with other applications. n8n has built-in support for a wide range of Microsoft Teams features, including channels, chats, channel and chat messages, chat members, online meetings, and tasks.

On this page, you'll find a list of operations the Microsoft Teams node supports and links to more resources.

{% hint style="info" %}
**Credentials**

From version 2 of the node, the **Authentication** dropdown offers three options:

* **Teams OAuth2**: the Microsoft Teams-specific OAuth2 credential (default). Its default scopes cover every resource on this page, including `Chat.ReadWrite` for chat members and chat messages, from n8n 2.39.0, `OnlineMeetings.ReadWrite` for online meetings, and, from n8n 2.41.0, `TeamworkTag.Read` for team tag mentions.
* **Microsoft OAuth2 (Graph)**: a generic Microsoft Graph credential that you can reuse across other Microsoft nodes. When you select this option, grant the credential the scopes this node needs. Refer to [Default scopes for Microsoft Teams](/integrations/builtin/credentials/microsoft.md#default-scopes-for-microsoft-teams) for the full list.
* **Service Principal (App-Only)**: app-only access through a Microsoft Entra app registration, with no signed-in user. Some resources need a signed-in user and aren't available with this credential. Refer to [Service Principal credential support](#service-principal-credential-support) on this page, and to [Microsoft Entra Service Principal credentials](/integrations/builtin/credentials/microsoftentraserviceprincipal.md) for setup and the required application permissions.

If you connected a Teams OAuth2 credential before n8n 2.39.0, reconnect it so it picks up `OnlineMeetings.ReadWrite`. If the credential uses **Custom Scopes**, add the scope to **Enabled Scopes** instead.

Refer to [Microsoft credentials](/integrations/builtin/credentials/microsoft.md) for guidance on setting up authentication.
{% endhint %}

{% hint style="info" %}
**Government Cloud Support**

If you're using a government cloud tenant (US Government, US Government DOD, or China), make sure to select the appropriate **Microsoft Graph API Base URL** in your Microsoft credentials configuration.
{% endhint %}

{% hint style="info" %}
**This node can be used as an AI tool**

This node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](/build/integrate-ai/ai-examples/use-ai-for-parameters.md).
{% endhint %}

{% hint style="info" %}
**Human-in-the-loop for AI tool calls**

This node can be used as a human review step for AI Agent tool calls. When configured this way, the AI Agent will pause and request human approval through this service before executing tools that require oversight. Learn more in [Human-in-the-loop for AI tool calls](/build/integrate-ai/ai-examples/human-in-the-loop-for-tools.md).
{% endhint %}

## Operations <a href="#operations" id="operations"></a>

{% hint style="info" %}
**Feature availability**

* The Chat Member and Online Meeting resources, and the Channel Message **Get**, **Get Many Replies**, and **Reply** operations, are available from n8n 2.39.0.

* The Chat Member **Add** and **Remove** operations, the Channel Message and Chat Message **Delete** and **Undo Delete** operations, the Online Meeting **Create or Get**, **Delete**, and **Update** operations, and Online Meeting support for the **Service Principal (App-Only)** credential are available from n8n 2.40.0.

* The Chat resource is available from n8n 2.41.0.

* The Activity Notification resource is available from n8n 2.42.0.
  {% endhint %}

* Activity Notification
  * Send

* Channel
  * Create
  * Delete
  * Get
  * Get Many
  * Update

* Channel Message
  * Create
  * Delete
  * Get
  * Get Many
  * Get Many Replies
  * Reply
  * Undo Delete

* Chat
  * Create
  * Get
  * Get Many

* Chat Member
  * Add
  * Get Many
  * Remove

* Chat Message
  * Create
  * Delete
  * Get
  * Get Many
  * Send and Wait for Response
  * Undo Delete

* Online Meeting
  * Create
  * Create or Get
  * Delete
  * Get
  * Update

* Task
  * Create
  * Delete
  * Get
  * Get Many
  * Update

## Waiting for a response

By choosing the **Send and Wait for a Response** operation, you can send a message and pause the workflow execution until a person confirms the action or provides more information.

### Response Type <a href="#response-type" id="response-type"></a>

You can choose between the following types of waiting and approval actions:

* **Approval**: Users can approve or disapprove from within the message.
* **Free Text**: Users can submit a response with a form.
* **Custom Form**: Users can submit a response with a custom form.

You can customize the waiting and response behavior depending on which response type you choose. You can configure these options in any of the above response types:

* **Limit Wait Time**: Whether the workflow will automatically resume execution after a specified time limit. This can be an interval or a specific wall time.
* **Append n8n Attribution**: Whether to mention in the message that it was sent automatically with n8n (turned on) or not (turned off).

### Approval response customization <a href="#approval-response-customization" id="approval-response-customization"></a>

When using the Approval response type, you can choose whether to present only an approval button or both approval *and* disapproval buttons.

You can also customize the button labels for the buttons you include.

### Free Text response customization <a href="#free-text-response-customization" id="free-text-response-customization"></a>

When using the Free Text response type, you can customize the message button label, the form title and description, and the response button label.

### Custom Form response customization <a href="#custom-form-response-customization" id="custom-form-response-customization"></a>

When using the Custom Form response type, you build a form using the fields and options you want.

You can customize each form element with the settings outlined in the [n8n Form trigger's form elements](/integrations/builtin/core-nodes/n8n-nodes-base.formtrigger.md#form-elements). To add more fields, select the **Add Form Element** button.

You'll also be able to customize the message button label, the form title and description, and the response button label.

## Mentions

{% hint style="info" %}
**Feature availability**

Mentions on the Microsoft Teams node are available from n8n 2.41.0.
{% endhint %}

The Channel Message **Create** and **Reply** operations and the Chat Message **Create** operation have a **Mentions** field. Each row in the field @mentions one person or one team tag, and n8n adds the mention to the message for you. On a channel message, set **Mention Type** to **User** or **Team Tag** first. A chat message mentions users only, because a team tag belongs to a team. Refer to Microsoft's [`chatMessageMention` resource type](https://learn.microsoft.com/en-us/graph/api/resources/chatmessagemention) for how Microsoft Teams stores a mention.

Don't type the name into **Message** as well, or it shows up twice.

**Mention Placement**, an option in the operation's **Options** collection, sets where the mentions go. **Start of Message**, the default, gives `@Jane please review this`. **End of Message** gives `please review this @Jane`.

{% hint style="warning" %}
**Mentions make the message HTML**

A mention makes Microsoft Teams render the message as HTML, even when **Content Type** is **Text**. Line breaks you type into **Message** stop showing as line breaks, so use `<br>` instead.
{% endhint %}

### Mention a user

In a **Mentions** row on Channel Message **Create** or **Reply**, set **Mention Type** to **User**. Chat Message **Create** has no **Mention Type**, because its rows are users already. Then fill in the **User** field:

* **From List**: search your Microsoft Entra directory and pick the user. Entries pair the display name with the user principal name (UPN), such as `Jane Smith (jane@contoso.com)`, because display names aren't unique in a tenant. Guest users work here too.
* **By ID**: enter the user's object ID, such as `7e2f1174-e8ee-4859-b8b1-a8d1cc63d276`, or their UPN or email address, such as `jacob@contoso.com`. For a guest user, use the object ID: a guest's UPN contains `#EXT#`, which this field rejects.

n8n looks the user up in Microsoft Entra before it sends the message, so the mention shows their directory display name rather than the text you entered.

### Mention a team tag

A team tag belongs to a team, so tag mentions work on channel messages only. Set the operation's **Team** to the team that owns the tag, then add a **Mentions** row, set **Mention Type** to **Team Tag**, and fill in the **Team Tag** field:

* **From List**: pick one of the team's tags. Each entry shows how many members carry it, such as `Engineering (4 members)`.
* **By ID**: enter the tag ID that `GET /v1.0/teams/<team-id>/tags` returns. The tag must belong to the team you selected, or the node fails when it looks the tag up.

Mentioning a tag notifies everyone who carries it. The Microsoft Teams node mentions a team's existing tags and can't create new ones.

### Mention permissions

User mentions need the `User.Read.All` permission and team tag mentions need `TeamworkTag.Read`. The **Teams OAuth2** credential requests both by default. Add them by hand if the credential uses **Custom Scopes**, or if you authenticate with **Microsoft OAuth2 (Graph)**. A Microsoft Entra admin must consent to them.

If you connected a Teams OAuth2 credential before n8n 2.41.0, reconnect it so it picks up `TeamworkTag.Read`. Without the scope, a team tag mention fails with a permission error.

Mentions aren't available with the **Service Principal (App-Only)** credential, which can't run any of the three operations that support them. Refer to [Service Principal credential support](#service-principal-credential-support).

## Delete and restore messages

The Channel Message and Chat Message **Delete** operations soft delete a message: Microsoft Teams hides it from the channel or chat but keeps it, so the **Undo Delete** operation of the same resource can restore it. Both operations run as the signed-in user. You can delete and restore your own messages. Whether you can delete other people's messages depends on your role in the team and on your organization's Microsoft Teams messaging policies. When Microsoft Teams doesn't allow it, the operation fails with a permission error.

Both operations take a **Message ID**. To find it, copy the message link in Microsoft Teams: the message ID is the number at the end of the link's path, before the `?`. A chat message also needs the **Chat**. A channel message also needs the **Team** and **Channel**. To delete or restore a reply in a channel, add the **Parent Message ID** option and enter the ID of the message the reply belongs to, which is the `parentMessageId` parameter in the reply's link.

Deleting and restoring channel messages needs the `ChannelMessage.ReadWrite` scope, which the **Teams OAuth2** credential requests by default from n8n 2.40.0. A credential you connected before n8n 2.40.0 doesn't have it, so **Delete** and **Undo Delete** fail with a 403 error until you reconnect the credential. If the credential uses **Custom Scopes**, add the scope to **Enabled Scopes** before you reconnect.

`ChannelMessage.ReadWrite` needs admin consent. If you aren't a Microsoft Entra administrator, ask one to grant admin consent for the app's new permissions first, for example by reconnecting the credential themselves and selecting **Consent on behalf of your organization**. If you reconnect without that consent, Microsoft stops at **Approval required** and the credential is left without a token, so every operation fails, not only the delete.

Chat messages use the `Chat.ReadWrite` scope, which the credential already includes. With the **Microsoft OAuth2 (Graph)** credential, add the scopes yourself.

The **Delete** and **Undo Delete** operations aren't available with the **Service Principal (App-Only)** credential, because Microsoft Graph offers them only for a signed-in user. Refer to [Service Principal credential support](#service-principal-credential-support).

## Chats and chat members

The Chat resource (available from n8n 2.41.0) works with the signed-in user's chats. **Get Many** lists them, **Get** returns one chat that you pick from the list or give by ID, and **Create** starts a new one. A chat ID starts with `19:`. You find it after `conversations/` in the address bar of the Teams web app, or in the `id` field of a Chat **Get Many** result. n8n adds you to a new chat automatically, so list only the other people under **Other Participants**. **Chat Type** sets what you create:

* **One-on-One**: a chat between you and one other person. If you already have a chat with that person, Microsoft Teams returns the existing chat instead of creating a new one.
* **Group**: a chat with one or more other people. You can give it a **Topic**, and add or remove members later with the Chat Member operations.

For each participant, pick the user from the list or enter their user principal name or object ID. Set **Role** to **Guest** for a guest account in your tenant, because Microsoft Teams rejects a guest as an owner. For a person from another organization, enter their object ID and their organization's **Tenant ID**.

The Chat Member **Remove** operation takes the member's membership ID, not their user ID. Pick the member from the list, or use the `id` field from a Chat Member **Get Many** result. Microsoft Teams refuses to remove a member from a one-on-one chat, and refuses to remove the last owner of a group chat.

The Chat and Chat Member resources aren't available with the **Service Principal (App-Only)** credential. Refer to [Service Principal credential support](#service-principal-credential-support).

## Service Principal credential support

The **Service Principal (App-Only)** credential has no signed-in user, so the Microsoft Teams node can't run operations that act as one. The list below states what's available for each resource. For the unavailable resources and operations, the node hides their fields and shows a notice when you select this credential. A workflow that still uses one of them fails with an error before the node sends any request.

* **Activity Notification**: Send. It needs the `TeamsActivity.Send` application permission and a companion Teams app installed for the recipient. Refer to [Send an activity notification](#send-an-activity-notification).
* **Channel**: all operations.
* **Channel Message**: Get, Get Many, and Get Many Replies. Create and Reply aren't available, because app-only Microsoft Graph only supports migration import for channel messages. Delete and Undo Delete aren't available either, because Microsoft Graph offers them only for a signed-in user. Use an OAuth2 credential for these four operations.
* **Chat**: not available. App-only Microsoft Graph has no signed-in user whose chats it could list, get, or create.
* **Chat Member**: not available. The node's chat picker lists the signed-in user's chats, which app-only access can't do, so the node blocks the whole resource, including chats given by ID.
* **Chat Message**: not available. The node sends and reads chat messages as the signed-in user.
* **Online Meeting**: all operations, run on behalf of the user you select in the **Organizer** field, which the node shows when you select this credential. Pick the organizer from the list, or enter their user principal name or object ID. The app registration needs the `OnlineMeetings.ReadWrite.All` application permission (`OnlineMeetings.Read.All` is enough for Get), `User.Read.All` to pick the organizer from the list or by user principal name, and a Microsoft Teams application access policy that lets the app act on the organizer's meetings. Without the policy, the operations fail with a 403 error. Refer to [Allow app-only online meetings](/integrations/builtin/credentials/microsoftentraserviceprincipal.md#allow-app-only-online-meetings) for the setup.
* **Task**: all operations. Get Many always lists the tasks of a plan: the node hides the **Tasks For** option, so **Group Member** isn't available. The node also hides the **Team** picker, and the **Plan**, **Bucket**, and **Assigned To** fields accept an ID only.

Refer to [Microsoft Entra Service Principal credentials](/integrations/builtin/credentials/microsoftentraserviceprincipal.md) for the application permissions each operation needs.

## Send an activity notification

{% hint style="info" %}
**Feature availability**

The Activity Notification resource is available from n8n 2.42.0.
{% endhint %}

The Activity Notification **Send** operation posts a notification to one user's activity feed, the **Activity** tab in Microsoft Teams. It doesn't send a chat or channel message, so it also works with the **Service Principal (App-Only)** credential, which can't send messages. Use it to ping a person from an unattended workflow, for example when an approval is due.

Microsoft Teams only shows the notification if the recipient has a companion Teams app that names your credential's client ID. Without it, Microsoft Graph rejects the request with an HTTP 403 error. An administrator sets the app up once per tenant, then installs it for each recipient. Refer to [Set up the companion Teams app](#set-up-the-companion-teams-app).

### Fields

| Field                 | Description                                                                                                                                                                                                                                                                               |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Recipient**         | The user who gets the notification. **From List** searches your Microsoft Entra directory. **By ID** takes the user's object ID or user principal name (UPN), such as `jacob@contoso.com`. Give a guest user by their object ID: a guest's UPN contains `#EXT#`, which the field rejects. |
| **Headline**          | The bold first line of the notification. Keep it short so it fits on one line.                                                                                                                                                                                                            |
| **Preview Text**      | The second line. Teams shows the first 150 characters.                                                                                                                                                                                                                                    |
| **Topic**             | The third line, in grey. Name the item the notification is about, for example the workflow or the order.                                                                                                                                                                                  |
| **Topic Link**        | The Microsoft Teams link that opens when the user selects the notification. It must be an `https` link on a Microsoft Teams domain, such as `https://teams.microsoft.com/l/chat/0/0?users=someone@contoso.com`. Refer to [Topic Link](#topic-link).                                       |
| **Chain ID** (option) | A number that links related notifications. A new notification with the same Chain ID replaces the earlier one in the activity feed. Leave it at `0` to send the notification without a chain.                                                                                             |

The node calls Microsoft Graph's [`sendActivityNotification`](https://learn.microsoft.com/en-us/graph/api/userteamwork-sendactivitynotification?view=graph-rest-1.0) for the user with the `systemDefault` activity type. On success it returns `{ "success": true }`. Team and chat recipients, and custom activity types, aren't supported.

### Set up the companion Teams app

Complete these steps once per tenant. A Microsoft Entra administrator grants the permission, and a Teams administrator publishes and installs the app.

The companion app must name the client ID of the app registration your credential authenticates as. For the **Service Principal (App-Only)** credential, that's its **Application (Client) ID**. For a **Teams OAuth2** or **Microsoft OAuth2 (Graph)** credential, it's the **Client ID** of your own app registration. On n8n Cloud, the Teams OAuth2 credential can connect through an app registration that n8n manages, and that client ID isn't shown, so use a Service Principal credential or a credential with your own app registration instead.

#### Grant the Microsoft Graph permission

* **Service Principal (App-Only)**: in the [Microsoft Entra admin center](https://entra.microsoft.com/), open the app registration, select **API permissions** > **Add a permission** > **Microsoft Graph** > **Application permissions**, add `TeamsActivity.Send`, and grant admin consent. Refer to [Add application permissions](/integrations/builtin/credentials/microsoftentraserviceprincipal.md#add-application-permissions). To pick the recipient **From List**, also add `User.Read.All`.
* **Teams OAuth2**: the credential requests the delegated `TeamsActivity.Send` scope by default from n8n 2.42.0. If you connected the credential before n8n 2.42.0, reconnect it so it picks up the scope. If the credential uses **Custom Scopes**, add `TeamsActivity.Send` to **Enabled Scopes** first.
* **Microsoft OAuth2 (Graph)**: add `TeamsActivity.Send` to the credential's **Scope** field and reconnect.

#### Build the app package

The package is a flat zip file of three files: `manifest.json`, a 192x192 PNG named `color.png`, and a 32x32 PNG named `outline.png`. The only part that matters to Microsoft Graph is `webApplicationInfo.id`, which must be your client ID. The app needs no bot, tab, or other capability.

{% code title="manifest.json" %}

```json
{
	"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.17/MicrosoftTeams.schema.json",
	"manifestVersion": "1.17",
	"version": "1.0.0",
	"id": "<new-guid>",
	"developer": {
		"name": "Contoso",
		"websiteUrl": "https://www.contoso.com",
		"privacyUrl": "https://www.contoso.com/privacy",
		"termsOfUseUrl": "https://www.contoso.com/terms"
	},
	"name": {
		"short": "n8n Notifications"
	},
	"description": {
		"short": "Lets n8n workflows post to your Teams activity feed.",
		"full": "Companion app that lets an n8n Microsoft Teams credential send activity feed notifications."
	},
	"icons": {
		"color": "color.png",
		"outline": "outline.png"
	},
	"accentColor": "#FF6D5A",
	"webApplicationInfo": {
		"id": "<application-client-id>",
		"resource": "api://<application-client-id>"
	}
}
```

{% endcode %}

Replace `<new-guid>` with a new GUID for the app, for example from `uuidgen`, and `<application-client-id>` with your client ID in both places. Then zip the three files without a folder:

```bash
zip -j n8n-notifications.zip manifest.json color.png outline.png
```

#### Publish the app to your organization's catalog

In the [Teams admin center](https://admin.teams.microsoft.com/), go to **Teams apps** > **Manage apps**, select **Actions** > **Upload new app**, and upload the zip file. Only an administrator can do this: app-only access can't publish to the catalog, which is why n8n can't set the app up for you.

#### Install the app for each recipient

Install the app in the recipient's personal scope with Microsoft Graph. You can send the requests from [Graph Explorer](https://developer.microsoft.com/en-us/graph/graph-explorer): open **Modify permissions** and consent to `AppCatalog.Read.All` and `TeamsAppInstallation.ReadWriteForUser` before sending. Any tool that calls Microsoft Graph as your app registration works too, with the `TeamsAppInstallation.ReadWriteForUser.All` application permission.

First, look up the app's catalog ID. It differs from the `id` in the manifest, which Microsoft Graph calls `externalId`:

```http
GET https://graph.microsoft.com/v1.0/appCatalogs/teamsApps?$filter=externalId eq '<manifest-id>'
```

Then install the app for the recipient, using the `id` from the response as `<catalog-app-id>`:

```http
POST https://graph.microsoft.com/v1.0/users/<user-id>/teamwork/installedApps
Content-Type: application/json

{
	"teamsApp@odata.bind": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/<catalog-app-id>"
}
```

An HTTP 409 response means the app is already installed for that user. Repeat the install for every user who should receive notifications.

#### Allow time for the install to propagate

The install takes time to propagate. Until it does, Microsoft Graph keeps returning the "not installed" HTTP 403 error. In n8n's tests, the first notification went through about five minutes after the install. A 403 right after the install doesn't mean the install failed.

### Topic Link

Teams opens the **Topic Link** when the user selects the notification. Microsoft Graph accepts only Microsoft Teams links, so the notification can't link to the n8n execution or to any other website. The node checks the link before it sends the request. Links on the Teams domains of the sovereign clouds, such as `teams.microsoft.us`, work too.

The link must also open something real, or Teams shows an error when the user selects the notification. Use one of these:

* A chat link such as `https://teams.microsoft.com/l/chat/0/0?users=someone@contoso.com`, which opens a chat with that person.
* A channel, message, or meeting link that you copy from Teams, which opens that item.

Refer to Microsoft's [deep links to Teams chats, channels, and messages](https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-link-teams) for the link formats.

### Common errors

| Error                                                                           | Cause                                                                                                                                                                 | Fix                                                                                                                                                                                                                                     |
| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `The companion Teams app is not installed for this recipient`                   | Microsoft Graph returned HTTP 403. The recipient has no installed app that names your client ID under `webApplicationInfo.id`, or the install hasn't propagated yet.  | Complete [Set up the companion Teams app](#set-up-the-companion-teams-app). Check that `webApplicationInfo.id` matches the credential's client ID. A bot app with the same ID doesn't count. Allow about five minutes after installing. |
| `The app registration is missing the TeamsActivity.Send application permission` | Microsoft Graph returned HTTP 403 to a Service Principal credential. The app registration lacks the `TeamsActivity.Send` application permission or its admin consent. | Add the permission and grant admin consent. As an alternative, add the `TeamsActivity.Send.User` resource-specific permission to the companion app's manifest and install the updated app for the recipient.                            |
| `The credential is missing the TeamsActivity.Send permission`                   | Microsoft Graph returned HTTP 403 to an OAuth2 credential. The token lacks the delegated `TeamsActivity.Send` scope.                                                  | Reconnect the credential. With **Custom Scopes**, add the scope to **Enabled Scopes** first. On a **Microsoft OAuth2 (Graph)** credential, add it to **Scope**.                                                                         |
| `The Topic Link is required`, `The Topic Link must be a Microsoft Teams link`   | The node checked the link before sending. It's empty, not `https`, or not on a Microsoft Teams domain.                                                                | Enter a Teams deep link. Refer to [Topic Link](#topic-link).                                                                                                                                                                            |
| `The recipient was not found`                                                   | Microsoft Graph returned HTTP 404 for the user ID or UPN.                                                                                                             | Check the value, or pick the user **From List**. Give guest users by object ID.                                                                                                                                                         |

## Templates and examples <a href="#templates-and-examples" id="templates-and-examples"></a>

[Browse Microsoft Teams node documentation integration templates](https://n8n.io/integrations/microsoft-teams) or [search all templates](https://n8n.io/workflows/)

## Related resources <a href="#related-resources" id="related-resources"></a>

Refer to [Microsoft Teams' API documentation](https://learn.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0) for more information about the service.

## What to do if your operation isn't supported

If this node doesn't support the operation you want to do, you can use the [HTTP Request node](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest.md) to call the service's API.

You can use the credential you created for this service in the HTTP Request node:

1. In the HTTP Request node, select **Authentication** > **Predefined Credential Type**.
2. Select the service you want to connect to.
3. Select your credential.

Refer to [Custom API operations](/integrations/builtin/custom-api-actions-for-existing-nodes.md) for more information.