[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# See who is out next week in Officient

> List who is away next week in Officient, by team and day, and flag the days with too many people out. Runs weekly from chat or a script.

Source: https://cotlet.dev/integrations/officient-api-mcp-server/who-is-out-next-week

Planning next week starts with knowing who is away, and in Officient that answer sits in the calendar of each colleague.

Cotlet does it in your own Officient account with list\_colleagues and list\_colleague\_absences, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=officient) [All Officient tools](https://cotlet.dev/integrations/officient-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Officient do this on its own?

Officient has a calendar:read scope for apps (checked 22 Oct 2026), but the public reference lists no calendar endpoint. Its Teams link posts a daily list of who is absent, with no weekly view and no per-day count.

## How you do it in Officient today

1. On desktop, the employee opens Calendar, clicks the gear at the top right and selects Show colleagues.
2. Colleagues at the bottom of the calendar gives an overview per colleague. On mobile, the same is Show colleagues at the bottom of the screen.
3. Clicking your own name in Show colleagues opens your yearly calendar.
4. For a daily feed, an admin can link Teams under Settings > Integrations > Teams integration, which posts who is absent into a channel.
5. Neither view counts people per day, so a team lead adds the numbers up by eye.

## How to see who is out next week in Officient

Prompt

```
Every Friday, list who on my team is out next week, day by day, and flag days when more than two people are away.
```

1. 01  
### Find your team  
list\_colleagues with your team name returns the people on it, so the report covers the right group and ignores the rest of the company.
2. 02  
### Read next week  
list\_colleague\_absences reads the colleagues' calendars for Monday to Friday of next week and returns each absence with the person, type and day part.
3. 03  
### Count per day  
The agent counts people out per day, treats a half day as half a person and flags any day above the limit in your prompt.
4. 04  
### Report  
You get one line per day with names. Days above your limit come first, so the cover decision is the first thing you read.

### What you get back

Example data

```
Next week, Design team (6 people)
Mon 9 Nov: Lena Maes
Tue 10 Nov: Lena Maes
Wed 11 Nov: Lena Maes, Tom De Smet (half day), Aya Claes (home office)
Flagged: Wed 11 Nov, more than two entries
```

### Other ways to ask

- Tell me who is out on Monday morning before 9:00 every week.
- Show absences for the whole company in December and group them by team.
- List only half-day and hour-based absences for this week.

## What Officient allows, and what to know first

- Officient shows colleagues' calendars through Show colleagues, and each colleague appears in the overview.
- Officient has a home office entry, so remote days are visible next to absences.
- Officient's Teams link posts daily who is absent, who has a birthday and who starts that day.
- Officient lets you link its calendar to your own calendar application.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [Officient Help: Self Service calendar](https://help.officient.io/en/articles/3228648-self-service-calendar) · [Officient Help: Connect Officient to Teams](https://help.officient.io/en/articles/6441867-connect-officient-to-teams) · [Officient Help: Link your Officient calendar to your own calendar application](https://help.officient.io/en/articles/3228142-link-your-officient-calendar-to-your-own-calendar-application)

## Call list\_colleague\_absences from a script

curl

```
curl "https://cotlet.dev/api/v1/officient/colleague-absences?from_date=2026-11-09&to_date=2026-11-13" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"absences": [
{
"person": "Lena Maes",
"type": "Holiday",
"from_date": "2026-11-09",
"to_date": "2026-11-13",
"day_part": "full_day"
},
{
"person": "Tom De Smet",
"type": "Holiday",
"from_date": "2026-11-11",
"to_date": "2026-11-11",
"day_part": "half_day"
},
{
"person": "Aya Claes",
"type": "Home office",
"from_date": "2026-11-11",
"to_date": "2026-11-11",
"day_part": "full_day"
}
],
"total": 3
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is officient\_read → list\_colleague\_absences. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/officient-api-mcp-server.md#automations)

## Officient tools this automation uses

__Cotlet Officient tools used to see who is out next week in Officient__
| Tool | Parameters |
| ------------------------- | -------------------------- |
| list\_colleagues | query, team |
| list\_colleague\_absences | from\_date, to\_date, team |

[All 12 Officient tools with descriptions](https://cotlet.dev/integrations/officient-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Officient to Cotlet?

Yes. You sign in to Officient yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Officient once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Officient automations

- [Request time off in Officient from chat](https://cotlet.dev/integrations/officient-api-mcp-server/request-time-off.md)
- [Approve Officient absence requests by your own rule](https://cotlet.dev/integrations/officient-api-mcp-server/approve-absence-requests.md)
- [Officient API and MCP server: every tool](https://cotlet.dev/integrations/officient-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Officient.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Officient.

[Sign up free](https://cotlet.dev/app/signup?app=officient)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.