How to connect Microsoft Teams and Slack bot
Create a New Scenario to Connect Microsoft Teams and Slack bot
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Microsoft Teams, triggered by another scenario, or executed manually (for testing purposes). In most cases, Microsoft Teams or Slack bot will be your first step. To do this, click "Choose an app," find Microsoft Teams or Slack bot, and select the appropriate trigger to start the scenario.

Add the Microsoft Teams Node
Select the Microsoft Teams node from the app selection panel on the right.

Microsoft Teams
Configure the Microsoft Teams
Click on the Microsoft Teams node to configure it. You can modify the Microsoft Teams URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Slack bot Node
Next, click the plus (+) icon on the Microsoft Teams node, select Slack bot from the list of available apps, and choose the action you need from the list of nodes within Slack bot.

Microsoft Teams
⚙

Slack bot

Authenticate Slack bot
Now, click the Slack bot node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Slack bot settings. Authentication allows you to use Slack bot through Latenode.
Configure the Microsoft Teams and Slack bot Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Microsoft Teams and Slack bot Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

Slack bot
Trigger on Webhook
⚙
Microsoft Teams
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Microsoft Teams, Slack bot, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Microsoft Teams and Slack bot integration works as expected. Depending on your setup, data should flow between Microsoft Teams and Slack bot (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Microsoft Teams and Slack bot
Microsoft Teams + Jira + Slack bot: When a new channel message is posted in Microsoft Teams that mentions a critical bug, a Jira issue is automatically created. Then, a Slack bot sends a message to a designated channel confirming the creation of the Jira ticket and provides a link to it.
Slack bot + Google Calendar + Microsoft Teams: Schedule meetings via a Slack bot command. The meeting details are then automatically synced to a shared Google Calendar, and the event is also added to a Microsoft Teams channel calendar, ensuring everyone is aware of the scheduled event.
Microsoft Teams and Slack bot integration alternatives
About Microsoft Teams
Use Microsoft Teams in Latenode to automate notifications and approvals. Instead of manual updates, automatically post messages based on triggers from other apps (like CRM or databases). Streamline workflows and improve team communication by connecting Teams to your automated processes without complex coding.
Similar apps
Related categories

About Slack bot
Use Slack bot within Latenode to automate notifications and actions based on real-time triggers. Update databases, post alerts, or start complex workflows directly from Slack commands. Latenode lets you visually build and scale these interactions without code, adding custom logic and connecting to any API with ease.
Related categories
See how Latenode works
FAQ Microsoft Teams and Slack bot
How can I connect my Microsoft Teams account to Slack bot using Latenode?
To connect your Microsoft Teams account to Slack bot on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Microsoft Teams and click on "Connect".
- Authenticate your Microsoft Teams and Slack bot accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I forward Teams messages to a Slack channel?
Yes, you can easily forward Teams messages to Slack using Latenode. Leverage our visual editor for no-code setup or add custom JS logic for complex routing. Centralize key information streams.
What types of tasks can I perform by integrating Microsoft Teams with Slack bot?
Integrating Microsoft Teams with Slack bot allows you to perform various tasks, including:
- Post Microsoft Teams channel messages to a Slack channel.
- Send Slack messages when new Microsoft Teams users are added.
- Create summary reports in Slack based on Teams activity.
- Trigger Teams notifications from specific Slack channel events.
- Archive Teams messages to a file storage via Slack command.
How scalable are Microsoft Teams automations on Latenode?
Latenode offers scalable automation via robust infrastructure. Handle increasing volumes of Microsoft Teams and Slack bot data smoothly with advanced queuing and error handling.
Are there any limitations to the Microsoft Teams and Slack bot integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex formatting from Teams may not perfectly translate to Slack.
- File size limits apply when transferring files between the platforms.
- Real-time sync may experience slight delays during peak usage.