[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)

# Approve Officient absence requests by your own rule

> Approve Officient absence requests that fit your team rule, such as nobody else out, and keep the clashes for yourself. Runs daily.

Source: https://cotlet.dev/integrations/officient-api-mcp-server/approve-absence-requests

Requests reach a manager one by one, and each needs a look at who else is away before the approve click.

Cotlet does it in your own Officient account with list\_absence\_requests, list\_colleague\_absences and approve\_absence\_request, 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 names calendar scopes for apps (checked 22 Oct 2026), but the public reference lists no endpoint to approve an absence. The Teams link only reports absences in a channel each day. Approval is a click in the Self Service.

## How you do it in Officient today

1. An employee sends the request from the Self Service Calendar with Send request.
2. The manager approves it in their own Self Service. Officient's help video shows this for a manager who has Self Service access only.
3. Once approved, the absence is entered in the calendar on the HR platform.
4. To spot a clash, the manager opens Calendar > Show colleagues and compares the days by hand.
5. The check repeats for every request, so a busy week before holidays means a long queue.

## How to approve Officient absence requests by your own rule

Prompt

```
Go through the absence requests waiting for me. Approve holiday requests where nobody else on the team is out on those days, and list the rest with a reason.
```

1. 01  
### Read the queue  
list\_absence\_requests returns the requests waiting for you with the person, the type, the dates and whether it is a full day, a half day or hours. If you have no approval rights, the run stops here and says so.
2. 02  
### Check the team  
For each request, list\_colleague\_absences reads the calendars for the same dates. The agent applies the rule in your prompt, for example "nobody else on the team is out" or "only holiday, never overtime".
3. 03  
### Approve the clean ones  
approve\_absence\_request runs for requests that pass the rule. Each approval reaches the employee and the calendar, so it waits for your OK by default.
4. 04  
### Keep the rest  
Requests that clash, or have a type your rule does not cover, stay untouched in the queue. The agent lists them with the name of the colleague who is also out.

### What you get back

Example data

```
Requests waiting: 3
Approved 2:
- Kathleen Janssens, Holiday, 16 to 17 Nov
- Noor Aziz, Holiday, 23 Nov (half day)
Left for you 1: Pieter Wouters, 9 to 13 Nov (Lena Maes is out the same days)
```

### Other ways to ask

- Every morning, approve half-day requests with no clash and list everything longer than three days for me.
- Show me the pending requests with who else is out, but approve nothing.
- Approve requests from my team only for the next two weeks.

## What Officient allows, and what to know first

- Officient lets a manager approve absence requests in the Self Service, so no HR platform login is needed for this job.
- Officient enters an approved absence in the HR platform calendar straight away.
- Officient employees can request a full day, a half day or specific hours, so a request may cover part of a day.
- Officient's Teams link posts who is absent into a channel each day, and linking it needs an admin in both systems.

approve\_absence\_request asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Officient Help: Apply for leave of absence in the Self Service](https://help.officient.io/en/articles/3228093-video-apply-for-leave-of-absence-in-the-self-service) · [Officient Help: Connect Officient to Teams](https://help.officient.io/en/articles/6441867-connect-officient-to-teams) · [Officient Help: Self Service calendar](https://help.officient.io/en/articles/3228648-self-service-calendar)

## Call approve\_absence\_request from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/officient/requests/req_2207/absence-request/approve \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"request_id": "req_2207",
"status": "approved",
"person": "Kathleen Janssens",
"type": "Holiday",
"from_date": "2026-11-16",
"to_date": "2026-11-17",
"in_calendar": true
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is officient\_write → approve\_absence\_request. 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 approve Officient absence requests by your own rule__
| Tool | Parameters |
| ------------------------- | -------------------------- |
| list\_absence\_requests | cursor |
| list\_colleague\_absences | from\_date, to\_date, team |
| approve\_absence\_request | request\_id |

[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)
- [See who is out next week in Officient](https://cotlet.dev/integrations/officient-api-mcp-server/who-is-out-next-week.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.