Latenode

How to Set Out of Office in Teams, Schedule It, and Remove It Later

This template runs once a day. JavaScript compares today's date with the start and return you set, then calls Microsoft Graph to turn mailbox automatic replies on or off so Teams shows the right status. On the start day it also posts a short message in a Teams channel. Connect Microsoft Teams. Put the Graph token in that JavaScript node.

Updated Sep 16, 2026Est. run: 4sEst. cost: $0.0003
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Turns automatic replies on at the start date you set
  • Clears automatic replies on the return date
  • Posts a short away message in Microsoft Teams on the start day
  • Keeps the Graph token in the JavaScript node and Teams access on the Teams connection

How it works

1
Trigger

Run once a day

The scenario starts on the daily schedule you set.

2
Action

Set or clear automatic replies

JavaScript turns mailbox automatic replies on at the start date and off at the return date through Microsoft Graph. Put the Graph token in that JavaScript node.

3
Action

Post in Teams on the start day

On the day you leave, Microsoft Teams sends a channel message with your return date.

Setup guide

1

Create a Microsoft Graph token

In Azure, grant mailbox settings read and write access and issue a token for the mailbox that should show as out. Put that token in the JavaScript node or in Latenode secrets that node can read.

2

Connect Microsoft Teams

Add a Microsoft Teams connection with permission to post in the channel that should hear you are away.

3

Set start date, return date, and message

Add a daily schedule. In JavaScript, store the start date, return date, and automatic-reply text. On the start date, turn replies on and send the Teams channel message. On the return date, turn replies off. Other days, stop after the date check. Run on a test start date and confirm replies and the channel message.

Requirements

A Microsoft 365 mailbox Microsoft Graph can update automatic replies on
A Graph token with mailbox settings access, stored in the JavaScript node or secrets
A Microsoft Teams channel Latenode can post to
The start date and return date you want

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.

More templates

You might also like

Browse all templates →

123FormBuilder to Insightly: Create leads from form submissions

Manually copying form responses into your CRM wastes time and risks errors. This integration captures each New Submission event from 123FormBuilder and uses it to Create a Lead in Insightly, mapping the respondent's name, email, and custom fields directly into a new lead record. Marketing managers and sales teams can eliminate data entry and get leads into Insightly instantly for follow-up. By connecting 123FormBuilder's form capture with Insightly's CRM, you keep your sales pipeline fed without manual work.

8s~$0.002

Create a Pipeline deal from a new Discord channel message

Sales teams often miss leads buried in Discord conversations. This scenario captures every new message in a chosen Discord channel and creates a corresponding deal in Pipeline, using the message text as the deal description and the author's username as part of the deal name. Sales managers and business development reps can log inbound signals from team discussions directly into Pipeline CRM without manual data entry. The connection turns Discord into a lead source, so no opportunity slips through the cracks.

8s~$0.002

Create a Pipeline deal when a new HubSpot deal is added

Manually copying deal data from HubSpot to Pipeline wastes time and risks errors. This automation triggers on the New Deal event in HubSpot and then runs the Create Deal action in Pipeline, mapping the deal name, amount, and associated contact email and name. Sales operations teams and CRM administrators who use both HubSpot and Pipeline can eliminate duplicate data entry. HubSpot captures the initial deal, and Pipeline receives a matching record immediately, so both systems stay aligned without manual work.

8s~$0.002