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

Microsoft Teams
⚙

Calendly

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

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

Save and Activate the Scenario
After configuring Microsoft Teams, Calendly, 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 Calendly integration works as expected. Depending on your setup, data should flow between Microsoft Teams and Calendly (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 Calendly
Calendly + Jira + Microsoft Teams: When an invitee is created in Calendly, a Jira issue is created to track follow-up tasks. A notification is then sent to a Microsoft Teams channel to alert the team.
Calendly + Google Sheets + Microsoft Teams: When a new invitee is created in Calendly, their information is logged in a Google Sheet. A reminder message is then sent via Microsoft Teams before the appointment.
Microsoft Teams and Calendly 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 Calendly
Automate meeting scheduling with Calendly in Latenode. Trigger workflows based on new bookings or cancellations. Automatically update CRMs, send personalized follow-ups, or manage team calendars, freeing up valuable time. Latenode adds flexible logic and integrations Calendly lacks, all visually and affordably.
Related categories
See how Latenode works
FAQ Microsoft Teams and Calendly
How can I connect my Microsoft Teams account to Calendly using Latenode?
To connect your Microsoft Teams account to Calendly 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 Calendly accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically post meeting details to Microsoft Teams?
Yes, you can! Latenode lets you create workflows to post new Calendly meeting details directly to a Microsoft Teams channel, keeping everyone informed and saving time. Leverage our no-code editor with JS support!
What types of tasks can I perform by integrating Microsoft Teams with Calendly?
Integrating Microsoft Teams with Calendly allows you to perform various tasks, including:
- Send a Teams notification for each new Calendly booking.
- Create Teams meetings directly from Calendly event details.
- Update a Teams channel when a Calendly event is canceled.
- Automatically invite Teams channel members to Calendly events.
- Log Calendly meeting data in a dedicated Teams channel.
Can Latenode trigger workflows based on Teams message content?
Yes, Latenode can trigger workflows based on the content of Microsoft Teams messages, allowing for dynamic automation based on team communications.
Are there any limitations to the Microsoft Teams and Calendly integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations might require JavaScript knowledge.
- Rate limits imposed by Microsoft Teams and Calendly still apply.
- Initial setup requires understanding of both platforms' API structures.