Connecteam automation · runs weekly
Copy last week's Connecteam schedule and publish it
Most weeks the schedule looks like last week with a few changes, and every Sunday a manager copies it over, checks it against who is off and publishes it so the team can see it.
Cotlet does it in your own Connecteam account with list_schedulers, list_shifts, copy_previous_week, list_time_off_requests and publish_shifts, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Connecteam do this on its own?
Connecteam copies a week in the dashboard with copy previous week, and its API, on the Expert plan or higher, can create and update shifts, but its reference lists no copy action (checked 20 Oct 2026). The copy and the publish are two separate manual steps, and nothing compares the copied shifts with approved time off.
How you do it in Connecteam today
- In the Job Scheduler the manager opens next week and uses copy previous week, which copies every shift from the week before, or the same for a single employee.
- Copied shifts are drafts. Connecteam's article says they will not be published, and advises fixing any shift that is not relevant for this week.
- Single shifts can be duplicated too: in Weekly view the three dots on a shift offer Duplicate or Multi duplicate, and the copies stay in Draft until published.
- Users do not see shifts until they are published. The manager hovers over a shift, clicks the three dots and Publish, or clicks the Publish button at the top right to publish everything at once.
- To publish only some drafts, the manager selects them and uses the Publish bulk action from the Actions menu at the bottom.
How to copy last week's Connecteam schedule and publish it
Copy last week's Front of House schedule to the week of Oct 19 as drafts. If no shift clashes with approved time off, publish them. Otherwise tell me which shifts clash and publish nothing. - 01
Find the schedule
list_schedulers returns each schedule of the account. The agent matches the name in your prompt, and when two schedules fit it reports both instead of guessing.
- 02
Check the target week
list_shifts reads the week you want to fill. Connecteam's article does not say how copy treats shifts already in that week, so the agent stops and reports when the week is not empty.
- 03
Copy last week as drafts
copy_previous_week copies every shift of the previous week, or only one employee's when you name one. The shifts arrive as drafts and nobody sees them yet. The call asks for your OK until you switch confirmation off for it.
- 04
Check the drafts against time off
list_time_off_requests with status approved returns who is off that week. A draft shift of someone on approved time off is reported with the day, and the agent will not publish it.
- 05
Publish what is clean
publish_shifts makes the drafts visible to the team, all at once or only the ids you pass. If your prompt says to publish nothing when anything clashes, the run ends with the list of clashes.
What you get back
Schedule Front of House, week Oct 19 to Oct 25
Copied 14 draft shifts from Oct 12 to Oct 18 (week was empty)
Clash with approved time off: 1 (Marco Bell, Thu Oct 22)
Published 0, held back 14 until you fix the clash Other ways to ask
- Copy last week for Ana only and leave the rest of the week empty.
- Every Sunday at 6 pm, copy the week and publish it when no shift clashes with approved time off.
- Copy the week as drafts and list them by person, but publish nothing.
What Connecteam allows, and what to know first
- Copy previous week copies every shift of the previous week and publishes none of them.
- Users do not see a shift until it is published.
- In Connecteam's mobile app a shift can be published only if it has a title or a job, and either assigned users or claiming turned on.
- Selecting some drafts to publish is a bulk action of the Advanced plan in the Operations hub; the Publish button at the top right publishes everything at once.
- Connecteam's Unpublish bulk action undoes a publish that went out too soon without notifying users; publish_shifts has no counterpart, so that stays a click in the dashboard.
copy_previous_week and publish_shifts ask for your OK by default. To run it weekly without you, switch confirmation off for those tools in your dashboard.
Sources: Connecteam Help: How Do I Copy Shifts? · Connecteam Help: Schedule Tricks and Quick Actions · Connecteam Help: Perform Bulk Actions on Shifts in the Job Scheduler
Call copy_previous_week from a script
curl -X POST https://cotlet.dev/api/v1/connecteam/schedulers/1177/previous-week/copy \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"week_start":"2026-10-19"}' {
"scheduler_id": 1177,
"week_start": "2026-10-19",
"copied": 14,
"published": false
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is connecteam_write → copy_previous_week. Example data.
Schedule it in n8n, Make, Zapier or cronConnecteam tools this automation uses
| Tool | Parameters |
|---|---|
| list_schedulers | none |
| list_shifts | scheduler_id, start_date, end_date, published, cursor |
| copy_previous_week | scheduler_id, week_start, user_id |
| list_time_off_requests | status, start_date, end_date, cursor |
| publish_shifts | scheduler_id, shift_ids |
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.
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.