Microsoft Teams Connector

Overview

The Firstbase Workflows node for Microsoft Teams lets you create and manage channel messages, chat messages, and tasks directly from your Firstbase workflows.

Common Use Cases Include:

• Post a notification in a designated Teams channel when an offboarding task completes in Firstbase
• Send a Teams chat message to an employee's manager for approval when a hardware order needs sign-off
• Create a Teams task for IT follow-up when a device return or replacement request is flagged in Firstbase

Connection Overview

This credential authenticates Firstbase Workflows against Microsoft Teams using OAuth2, where a person or dedicated account signs in through Microsoft's consent screen and grants delegated access via Microsoft Graph, the API behind Teams. Once saved, this credential can be attached to any workflow step that reads from or writes to Teams.

Recommend Prep: Set up a Dedicated Integration User account

Don't sign in with a real employee's personal Microsoft 365 account. Set up a dedicated, licensed Microsoft 365 integration user for this integration instead, as this keeps the connection working if the person who originally set it up leaves the company, and makes it easier to see exactly what this integration can see and do in Teams, separately from any one person's own mailbox and channels.

OAuth2 Setup

To connect to Microsoft Teams, you will need:

• A Client ID
• A Client Secret

Step 1 - Generate the OAuth Callback URL in Firstbase Workflows

In Firstbase Workflows, navigate to Credentials -> Create Credential -> Microsoft Teams OAuth2 API. At the top of the credential form, copy the generated OAuth Callback URL.

Step 2 - Register an application

Open the Microsoft Application Registration Portal (https://aka.ms/appregistrations) and select Register an application. Enter a Name for your app. Under Supported account types, select "Accounts in any organizational directory (Any Azure AD directory - Multi-tenant) and personal Microsoft accounts." 

Paste the OAuth Callback URL copied from Firstbase Workflows into the Redirect URI (optional) field, selecting Web as the platform. Select Register.

Step 3 - Copy the Client ID

On the app's Overview page, copy the Application (client) ID.

Step 4 - Add the Graph API permissions this app will use

In the app registration, select API permissions -> Add a permission -> Microsoft Graph -> Delegated permissions, and add whichever permissions your workflows need (for example Team.ReadBasic.All to list teams, Channel.ReadWrite.All for channel management, ChannelMessage.Send to post to channels, or Chat.ReadWrite for one-to-one/group chat messages). 

Select Grant admin consent if your tenant requires it before delegated permissions can be used.

Step 5 - Generate a client secret

Select Certificates & secrets -> + New client secret. Enter a description (e.g. "Firstbase Workflows"), select Add, then copy the Secret's Value immediately (Microsoft only shows it once). Copy and save for later use.

Important: If your organization's Microsoft 365 accounts are managed by an Entra administrator, you may see a message requiring admin approval when connecting. An Entra admin will need to grant consent for this app before the connection will work.

Setup in Firstbase Workflows

This can be saved as a global credential, reusable across workflows, or scoped to a single workflow.

Step 1 - Navigate to Workflows

In the Firstbase platform, as an admin, click the Workflows tab.

Step 2 - Create the new credential

In Workflows, click Credentials -> Create Credential (top right) -> Type "Microsoft Teams" -> select Microsoft Teams OAuth2 API. 

Enter the information you collected above into the corresponding fields, then complete the Connect my account step and click Save. You now have a Microsoft Teams connection ready for building workflows.

Step 3 - Using the credential in a workflow

Add the Teams node (or the Teams Trigger node, to start a workflow when something changes in Teams) to your workflow, and select the Microsoft Teams credential you just created. Choose a Resource, then the Operation you need under that resource. 
 

Important: Reading channel messages (Get Many Messages) uses a metered Microsoft Teams API. If your tenant isn't configured for it, Microsoft returns an HTTP 402 error.

Questions? Reach out to your Firstbase Solutions Engineer or Customer Success Manager