[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 or decline Connecteam time off requests with AI

> Approve Connecteam time off requests by your own rule on length, notice and overlaps, and leave edge cases for you. Runs daily, no API plan needed.

Source: https://cotlet.dev/integrations/connecteam-api-mcp-server/approve-time-off-requests

Time off requests pile up in Pending Requests during the week, and a manager has to check every date range before answering, so employees wait for a reply.

Cotlet does it in your own Connecteam account with list\_time\_off\_requests and decide\_time\_off\_request, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Connecteam do this on its own?

Connecteam answers requests by hand in Pending Requests, and its API, on the Expert plan or higher with the HR & Skills hub, lists, creates and updates time off requests (checked 20 Oct 2026). Auto-approval is a policy switch for every request, not a rule on dates, length or overlaps. Reading each request stays with you.

## How you do it in Connecteam today

1. Admin approval is a switch in the policy, Time off request requires admin approval. With it off, Connecteam approves requests automatically and deducts them from the balance. The switch needs the HR Basic plan or higher.
2. In the dashboard the admin opens Time Off in the left sidebar and clicks Pending Requests in the upper right.
3. The window lists every request employees submitted within a date range, and the admin approves or declines each one.
4. The gear icon on the Pending Requests tab sets whose requests reach this admin: a smart group they manage, their direct reports, specific users or no one.
5. An approved request lands on the employee's timesheet by itself. A decision can be reversed from the View Request window, History tab, three-dot menu.

## How to approve or decline Connecteam time off requests with AI

Prompt

```
Go through pending time off requests. Approve requests of up to 3 days that start at least 14 days from now and do not overlap an approved request. Leave the rest for me with the reason.
```

1. 01  
### Read the pending queue  
list\_time\_off\_requests runs with status pending and follows next\_cursor to the end, so a request list that grew over a weekend is judged as one batch. The account must be an admin allowed to act on requests; any other account gets APP\_PERMISSION\_DENIED and the run stops before anyone is judged.
2. 02  
### Apply your rule  
Each request is matched against the rule in your prompt, for example up to 3 days and a start at least 14 days out. The agent quotes the length and start date it relied on.
3. 03  
### Check overlaps  
list\_time\_off\_requests with status approved shows who is already off in the same dates. A request that overlaps an approved one is left for you, so the team keeps its cover.
4. 04  
### Decide  
decide\_time\_off\_request approves the matches. It declines only when your prompt says so, and everything else stays pending. An approved request lands on the employee's timesheet, and the employee sees the new status in the mobile app. Every call asks for your OK until you switch confirmation off for it.
5. 05  
### Skip what changed  
Before deciding, the agent reads the queue again. A request that another admin decided in the meantime is gone from it, so the agent logs it as already handled and leaves it alone.

### What you get back

Example data

```
Pending requests: 6
Approved 3 (e.g. Priya Nair, Vacation, Oct 22 to Oct 23, 2 days)
Left for you 3:
- Marco Bell: 8 days in December, over your 3-day rule
- Jo Kim: starts in 5 days
- Sam Reyes: overlaps Ana Lopez, already approved
```

### Other ways to ask

- Every morning, approve one-day requests and list everything else for me.
- Show me pending requests that overlap an approved one, and approve nothing.
- Decline requests that start within the next 7 days and tell me who asked.

## What Connecteam allows, and what to know first

- Admin approval in Time Off is available from the HR Basic plan and above; with it off, requests are approved automatically.
- Admins can act only on users they directly manage or whose smart group they administer, so the agent sees the requests your account sees.
- Employees see approved, declined or pending in the mobile app, and an approved request appears on their timesheet automatically.
- Each admin can switch on email or push alerts for new requests and for decisions of other admins under Time Off > Options > Settings.
- A decision can be changed afterwards in the History tab of the request, so a wrong approval is not final.

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

Sources: [Connecteam Help: How Do I Approve Time-Off Requests?](https://help.connecteam.com/en/articles/6451954-how-do-i-approve-time-off-requests) · [Connecteam Help: Time Off: Admins Permissions](https://help.connecteam.com/en/articles/6741264-time-off-admins-permissions) · [Connecteam Help: Starting Guide to Time Off](https://help.connecteam.com/en/articles/6713889-starting-guide-to-time-off)

## Call decide\_time\_off\_request from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/connecteam/requests/5528/time-off-request/decide \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"decision":"approve"}'
```

Example response

```
{
"request_id": "5528",
"status": "approved",
"name": "Priya Nair",
"policy_type": "Vacation",
"start_date": "2026-10-22",
"end_date": "2026-10-23",
"days": 2
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is connecteam\_write → decide\_time\_off\_request. Example data.

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

## Connecteam tools this automation uses

__Cotlet Connecteam tools used to approve or decline Connecteam time off requests with AI__
| Tool | Parameters |
| -------------------------- | -------------------------------------- |
| list\_time\_off\_requests | status, start\_date, end\_date, cursor |
| decide\_time\_off\_request | request\_id, decision |

[All 14 Connecteam tools with descriptions](https://cotlet.dev/integrations/connecteam-api-mcp-server.md#tools)

## Frequently asked questions

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

Yes. You sign in to Connecteam yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Connecteam 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 Connecteam automations

- [Approve Connecteam timesheets with AI](https://cotlet.dev/integrations/connecteam-api-mcp-server/approve-submitted-timesheets.md)
- [Copy last week's Connecteam schedule and publish it](https://cotlet.dev/integrations/connecteam-api-mcp-server/copy-last-weeks-schedule.md)
- [Connecteam API and MCP server: every tool](https://cotlet.dev/integrations/connecteam-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Connecteam.

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

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

---

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.