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

# Assign PeopleHR onboarding tasks to new starters

> Give every new PeopleHR starter their onboarding tasks, set per role and assigned to the right manager, without repeating the same form by hand.

Source: https://cotlet.dev/integrations/peoplehr-api-mcp-server/assign-onboarding-tasks

A new starter is added on Monday, and the tasks for their manager, IT and the team still wait until someone creates them one by one in the Tasks area.

Cotlet does it in your own PeopleHR account with list\_employees, get\_employee, list\_tasks and create\_task, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can PeopleHR do this on its own?

PeopleHR has no task action in its Integration API, which lists 31 resources and none for tasks, and the Zapier app has no actions (checked 22 Oct 2026). Natively a Background ripple linked to a query creates the same task steps for everyone the query returns. Tasks that depend on the role or the manager are created by hand.

## How you do it in PeopleHR today

1. An admin opens Tasks and the All Tasks view, then clicks the plus icon to create a task.
2. The task takes a title and, if wanted, a completion date, who it is in relation to and a description. An admin can assign it to anyone, a manager only to employees reporting to them.
3. The admin repeats this for each task of each starter. PeopleHR groups the results under Overdue, New, Due Today, Upcoming and Completed.
4. To avoid the repetition, an admin builds a query on Employees Details > Start Date filtered to Today, creates a Background ripple under Settings > Ripples with a Task step and links the ripple to the query.
5. The Task step has a name, an Assigned to person and a Date Offset, so every starter gets the same tasks with the same assignee.

## How to assign PeopleHR onboarding tasks to new starters

Prompt

```
For everyone who started in PeopleHR this week, create the onboarding tasks for their manager: book a 1:1, share the team handbook and confirm their equipment. Set the completion date to 7 days after their start. Skip tasks that already exist.
```

1. 01  
### Find who started  
list\_employees returns the employee list with each start date. The agent keeps people whose start date falls in your window and leaves leavers out.
2. 02  
### Read the profile  
get\_employee gives job title, department and line manager for each starter. The tasks follow your prompt by role: an engineer gets an equipment task, a salesperson gets a CRM access task.
3. 03  
### Check for duplicates  
list\_tasks reads the New and Overdue tasks, so a task created earlier by a ripple or by hand for the same starter is not created twice.
4. 04  
### Create the tasks  
create\_task runs once per task with the assignee, the starter the task is about and a completion date counted from the start date. Each call waits for your OK until you switch confirmation off, because the assignee sees the task.
5. 05  
### Report who is missing  
A starter without a line manager, or whose manager is leaving, is listed for you instead of getting a task nobody owns. PeopleHR refuses a task for someone who is leaving.

### What you get back

Example data

```
Starters this week: 3
Tasks created 8 for 3 starters, e.g. Ana Lopez: "Book first 1:1" for Dana Reyes, due 23 Nov
Skipped 1 (task "Confirm equipment" already exists)
Needs you 1:
- Jake Ortiz: no line manager on the profile
```

### Other ways to ask

- Every Monday, create the 30-day check-in task for people who started 30 days ago.
- Create a task for IT for every new starter whose department is Engineering.
- List the new starters without any task and create nothing yet.

## What PeopleHR allows, and what to know first

- A PeopleHR admin can assign a task to anyone, while a manager can assign tasks only to employees reporting to them.
- PeopleHR does not allow a task for someone who is leaving; it has to go to another active employee.
- Documents cannot be attached to PeopleHR tasks. Documents for new starters go out through a ripple or Mail Merge.
- The completion date of a task is optional, and tasks are sorted under Overdue, New, Due Today, Upcoming and Completed.

create\_task asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [PeopleHR Help: Overview on Tasks](https://help-peoplehr.theaccessgroup.com/en/articles/11905238-overview-on-tasks) · [PeopleHR Help: Assign tasks to all employees in bulk](https://help-peoplehr.theaccessgroup.com/en/articles/12180219-assign-tasks-to-all-employees-in-bulk) · [PeopleHR Help: Attach documents to new starters' tasks](https://help-peoplehr.theaccessgroup.com/en/articles/12275718-attach-documents-to-new-starters-tasks) · [PeopleHR Help: Mobile tasks](https://help-peoplehr.theaccessgroup.com/en/articles/12131128-mobile-tasks)

## Call create\_task from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/peoplehr/assignees/PW8/tasks \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Book first 1:1","about_employee_id":"PW41","completion_date":"2026-11-23","description":"Book a 30 minute 1:1 in the first week."}'
```

Example response

```
{
"task_id": "tsk-3301",
"title": "Book first 1:1",
"assignee": "Dana Reyes",
"about": "Ana Lopez",
"completion_date": "2026-11-23",
"status": "New"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is peoplehr\_write → create\_task. Example data.

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

## PeopleHR tools this automation uses

__Cotlet PeopleHR tools used to assign PeopleHR onboarding tasks to new starters__
| Tool | Parameters |
| --------------- | ----------------------------------------------------------------------- |
| list\_employees | search, cursor |
| get\_employee | employee\_id |
| list\_tasks | view, status, cursor |
| create\_task | title, assignee\_id, about\_employee\_id, completion\_date, description |

[All 10 PeopleHR tools with descriptions](https://cotlet.dev/integrations/peoplehr-api-mcp-server.md#tools)

## Frequently asked questions

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

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

- [Auto-approve PeopleHR holiday requests](https://cotlet.dev/integrations/peoplehr-api-mcp-server/approve-holiday-requests.md)
- [PeopleHR API and MCP server: every tool](https://cotlet.dev/integrations/peoplehr-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to PeopleHR.

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

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

---

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.