How to connect Microsoft Teams and Salesforce
Create a New Scenario to Connect Microsoft Teams and Salesforce
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 Salesforce will be your first step. To do this, click "Choose an app," find Microsoft Teams or Salesforce, 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 Salesforce Node
Next, click the plus (+) icon on the Microsoft Teams node, select Salesforce from the list of available apps, and choose the action you need from the list of nodes within Salesforce.

Microsoft Teams
⚙

Salesforce

Authenticate Salesforce
Now, click the Salesforce node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Salesforce settings. Authentication allows you to use Salesforce through Latenode.
Configure the Microsoft Teams and Salesforce 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 Salesforce 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
⚙

Salesforce
Trigger on Webhook
⚙
Microsoft Teams
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Microsoft Teams, Salesforce, 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 Salesforce integration works as expected. Depending on your setup, data should flow between Microsoft Teams and Salesforce (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 Salesforce
Salesforce + Jira + Microsoft Teams: When a new opportunity is won in Salesforce, a new issue is created in Jira. A notification is then sent to a specified channel in Microsoft Teams to inform the team about the new project.
Salesforce + Outlook + Microsoft Teams: When a new lead is created in Salesforce, a welcome email is sent via Outlook to the lead. Simultaneously, a notification is sent to the sales team in a Microsoft Teams channel.
Microsoft Teams and Salesforce 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 Salesforce
Sync Salesforce data with other apps using Latenode. Automate lead qualification and task creation based on CRM events. No more manual data entry: build workflows that trigger actions across your stack. Use Latenode's visual editor and flexible scripting to create custom logic and scale automation without code limits.
Similar apps
Related categories
See how Latenode works
FAQ Microsoft Teams and Salesforce
How can I connect my Microsoft Teams account to Salesforce using Latenode?
To connect your Microsoft Teams account to Salesforce 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 Salesforce accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create a Teams channel for new Salesforce opportunities?
Yes, you can! Latenode's visual editor simplifies this automation. Benefit from instant team collaboration and improved opportunity management.
What types of tasks can I perform by integrating Microsoft Teams with Salesforce?
Integrating Microsoft Teams with Salesforce allows you to perform various tasks, including:
- Post Salesforce case updates to a specific Teams channel.
- Send daily Salesforce report summaries to a Teams chat.
- Create Salesforce leads from new Microsoft Teams meeting attendees.
- Trigger Salesforce tasks when a new message is posted in Teams.
- Update Salesforce records based on Teams poll responses.
Can I use custom logic with Microsoft Teams integrations?
Yes! Latenode supports JavaScript code blocks for tailored Microsoft Teams automations.
Are there any limitations to the Microsoft Teams and Salesforce integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Salesforce data transformations may require JavaScript coding.
- File size limits apply when transferring files between Teams and Salesforce.
- Real-time data sync depends on the polling interval selected.