BusyBot
Search all guides

Reference · Credentials

Connect Microsoft Teams to BusyBot

Used by 1 BusyBot node.

Type microsoftTeamsOAuth2Api 10 fields

Fields

FieldTypeRequiredNotes
Client ID
clientId		 string Yes The Application (client) ID from your Azure AD app registration.
Client Secret
clientSecret		 password Yes The client secret from your Azure AD app registration.
Tenant ID
tenantId		 string No The Azure AD tenant ID.
Scope
scope		 string No OAuth2 scopes to request.
Authorization URL
authorizationUrl		 string No The Microsoft Identity Platform authorization endpoint.
Access Token URL
accessTokenUrl		 string No The Microsoft Identity Platform token endpoint.
Microsoft Graph API Base URL
graphApiBaseUrl		 string No The Microsoft Graph API base URL.
Access Token
accessToken		 password No OAuth2 access token. Required for API calls.
Refresh Token
refreshToken		 password No OAuth2 refresh token. Required for automatic token renewal. Leave blank only if the token never expires.
Token Expiry (Unix timestamp)
expiresAt		 string No Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Setting up Microsoft Teams OAuth2 API

  1. In Microsoft Teams OAuth2 API, create the credential this connection needs — the values listed in the table above. These are issued from your own Microsoft Teams OAuth2 API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Microsoft Teams OAuth2 API.
  3. Paste each value into the matching field and save.
  4. Add the Microsoft Teams Trigger node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Microsoft Teams credentials?

One node: Microsoft Teams Trigger. Create the credential once and select it in that node.

What does a Microsoft Teams credential need?

10 fields: Client ID, Client Secret, Tenant ID, Scope, Authorization URL, Access Token URL, Microsoft Graph API Base URL, Access Token, Refresh Token, Token Expiry (Unix timestamp). Required: Client ID, Client Secret. The values come from your own Microsoft Teams account.

How are Microsoft Teams secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Does Microsoft Teams use OAuth?

Yes. This credential connects through OAuth (fields: Client ID, Client Secret, Tenant ID, Scope, Authorization URL, Access Token URL, Microsoft Graph API Base URL, Access Token, Refresh Token, Token Expiry (Unix timestamp)): you approve access in Microsoft Teams, and the resulting tokens are stored encrypted like every other credential.

Nodes that use Microsoft Teams OAuth2 API

One credential works across every node below — create it once and reuse it.