Back to blog

How to Set Slack Out of Office Automatically from Google Calendar

Sync Slack out-of-office status from Google Calendar, check Enterprise-only options, and configure notifications and return dates separately.

An open mountain-hut doorway frames a hiker leaving along an alpine trail, with boots and a coat inside.

You can automatically set a Slack out-of-office status from Google Calendar by connecting Slack’s Google Calendar app and enabling status syncing. The general integration documents OOO or PTO in the event title as its out-of-office trigger. Slack also offers a dedicated out-of-office feature on Enterprise plans, with its own calendar-sync setting and a longer message for colleagues.

Before you leave, check notifications separately. A status tells people you are away; it does not, by itself, establish that Slack will stop interrupting you. Choose the simplest setup that communicates your absence and protects the time you intend to take off.

Which Slack out-of-office option do you need?

There are several ways to communicate time away, and they do different jobs:

  • A custom Slack status is a message and emoji. You can set an expiry or schedule a future start and end.
  • The Google Calendar app can update a status from eligible events on your primary calendar.
  • Slack’s dedicated Enterprise out-of-office option adds a longer message and a notice when colleagues mention you in a channel.
  • Paused notifications protect you from alerts. Active or away presence is another separate setting.

For a single vacation with fixed dates, a scheduled custom status and an appropriate notification pause may be sufficient. Calendar automation is useful when the absence is already recorded in Google Calendar or its dates may change.

If you open Slack briefly while away, your absence message and notification settings can still make it clear that colleagues should expect a reply after your return.

Sync an OOO status with Slack’s Google Calendar app

If Google Calendar is not installed in your workspace, install the app or ask an administrator to approve it. In Slack desktop, open Agents & tools, choose Apps, and open Google Calendar. Connect your Google account from the app’s Home tab, then open Settings and enable Status Sync. Slack’s calendar automation guide explains the connection process.

Create the absence on your primary Google Calendar. For the general integration, use an event title containing OOO or PTO, such as OOO — annual leave. Slack’s Google Calendar help page documents this title-based trigger and limits status syncing to the primary calendar.

That help page says eligible events are accepted or mark your availability as Busy. It also says manually set statuses are not overwritten and overlapping events can prevent status updates. Check the actual event and clear a stale custom status before assuming the connection is broken. Slack’s documentation has differing descriptions of some eligibility and overlap behavior across its surfaces, so test a simple absence first rather than relying on a complicated overlap.

Do not assume a shared team PTO calendar will update your personal Slack status just because the app can show its events. Receiving calendar reminders and enabling personal status syncing are different settings.

This route is useful when a standard out-of-office label is enough. If you need a specific return message or notification policy, configure those explicitly instead of expecting an event title to control everything.

Use Slack’s dedicated Enterprise out-of-office feature

Slack’s dedicated out-of-office guide lists this feature for Enterprise plans. If your workspace offers it, open your profile picture, select Update your status, and choose Out of office. Set when it should clear, add an optional message, and select Pause notifications if you want that protection.

The longer message can identify a return date and a backup contact. Slack displays the details on your profile and above the direct-message field; when someone mentions you in a channel, Slack sends that person a private notice. That is different from automatically answering every incoming DM.

For calendar-driven activation, open Google Calendar in Slack, then Home and Settings, and enable out-of-office syncing. Slack documents a future calendar out-of-office event as a way to schedule this status in advance. Use the dedicated setting when available; do not assume it is identical to the general Status Sync checkbox.

If the Enterprise option is missing, a custom status is still a practical alternative. You do not need a dedicated absence feature simply to tell colleagues that you are on leave.

Create a real Google Calendar out-of-office event

On an eligible work or school Google account, open Calendar on a computer and choose Create, then Out of office. Enter the dates, or turn off All day for a shorter absence. Review the decline settings and message before saving. Google’s instructions describe the controls.

A Google out-of-office event is a distinct event type. An ordinary event named Vacation or OOO is not necessarily the same thing. Google’s calendar status-event documentation distinguishes these event types and notes that status events are available on primary calendars and for some Google Calendar users.

If Out of office is unavailable in your account, you can still communicate the absence using an ordinary event and the title convention supported by your chosen Slack integration. That fallback does not acquire Google’s out-of-office decline controls merely because its title says OOO.

Declining meeting invitations and pausing Slack notifications also solve different problems. Verify both if you intend to disconnect completely: refusing new meetings is not a notification mute.

Schedule a custom status if you only need one absence

For a fixed absence, you can avoid another calendar integration. On Slack desktop, open your profile picture and Update your status. Enter a message and emoji, then use Duration to choose a future start and end time. Slack’s status guide documents this scheduling option.

Write the return expectation first. For example: On leave through Friday; back Monday. Billing: ask the finance team. Agree on the backup before including it, and avoid putting private medical or travel details in a public-facing status.

If the editor offers a notification-pause checkbox, choose it when appropriate. Otherwise, pause notifications from your profile menu and select a suitable custom end time. On mobile, open your profile picture and Pause notifications. Slack’s notification guide covers these controls and urgent-message overrides. On paid plans, VIP notification settings can also allow chosen contacts to reach you while notifications are paused.

A scheduled status follows the dates you entered. If leave is extended, update the scheduled status and notification pause too. An expiry prevents stale text; it does not know that your travel plans changed.

Add a schedule-aware return date with ModePilot

ModePilot’s out-of-office automation is useful when you want Google Calendar absence information to drive configurable Slack behavior and a return date that considers your work schedule.

ModePilot recognizes Google’s actual Out of office event type. It also recognizes an ordinary event whose entire title is Out of office or OOO, ignoring capitalization and spaces at the ends. Its built-in OOO rule does not treat every title containing PTO or Vacation as an out-of-office event. This differs from the general native Slack title convention, so check the event type or exact title when switching tools.

To configure the behavior:

  • Connect Google Calendar and Slack in Integrations, and select the calendar that contains your absence.
  • In Modes, open Out of Office and confirm it is enabled.
  • Configure Set status, the status message and emoji. Choose Set DND and Away presence separately if those match your absence policy.
  • Insert {return_date} into a message such as Out of office; back {return_date}.
  • Check your working schedule and calendar dates, then verify the computed status and return date during a short test before relying on the message.

The return-date variable uses the next available working day after the absence, taking non-working days and subsequent OOO blocks into account. For someone who does not work weekends, Friday leave can therefore point to Monday rather than Saturday. If Monday is also covered by an OOO block, the next available workday can be later. The result depends on the schedule and calendar information configured in ModePilot.

{return_date} supplies a date, not a promised time of day. For an afternoon appointment, do not use that date alone to imply you will answer at a particular hour. Choose clearer wording or include the specific return expectation yourself.

The Modes guide explains the separate outputs and matching behavior. ModePilot updates your custom status; Slack’s Enterprise mention-response feature is a separate option.

Check what happens at the end of your absence

Returning from leave is not always the same as reaching a calendar event’s end. A Friday absence may end before the weekend, while your next working window begins on Monday. A half-day absence might finish while another protected event is still running.

Calendar-and-schedule automation should evaluate the next applicable state. In ModePilot, the configured schedule, calendar modes, priority and temporary overrides determine what happens next. It does not simply force Slack to Active or enable every notification because one OOO event has ended. Returning presence to Auto leaves Slack to determine activity.

Test an absence’s start and end before an important trip. Check the status text, presence choice and paused-notification state individually. If ModePilot manages DND, do not assume it will preserve every longer pause set directly in Slack or by another app when its own protection ends.

Clear ownership helps: use one system to manage each Slack signal where possible. Avoid running two status-writing integrations and expecting their changes to coordinate automatically. The broader principle is the same as enforcing after-hours boundaries: the calendar should describe the real absence, and the tools should apply the intended boundary.

If Slack shows the wrong out-of-office status

Inspect the calendar event behind the status before reconnecting anything. Check its owner, title, calendar, dates, time zone and your response. An event containing someone else’s PTO in its title is worth investigating if the native integration is using title-based classification; it does not prove that you personally booked leave.

For Slack’s native integration, check Status Sync, the primary calendar and any manual status still in place. For ModePilot, check the actual Google event type or exact OOO title, the enabled OOO rule, the selected calendar and any conflicting mode or override.

Finally, confirm the return boundary in your own local time and check for another app writing the status. Keep general calendar-sync diagnosis separate from OOO-specific configuration: an absence has to be represented correctly before an integration can communicate it accurately.

For missing or stale calendar output, the Slack status diagnostic guide separates connection problems from event rules. The working-hours guide explains the schedule boundaries behind a return day.

Start with the schedule you already have.

ModePilot turns calendar context into live work-state automation so Slack, DND, and work boundaries keep up with the real day.

Get started

Google Calendar setup comes first. Slack can be connected later.