# Schedule a crew on a new job in ClockShark

> Your agent creates the ClockShark job, drafts a shift per day for the crew, checks for clashes and publishes the week after your OK.

Source: https://cotlet.dev/integrations/clockshark-api-mcp-server/schedule-crew-shifts

A job is signed on Friday and the crew has to see it in the ClockShark app before Monday. Someone creates the job, opens SCHEDULES, adds shifts for every day and person, checks nobody is booked twice, then publishes.

Cotlet does it in your own ClockShark account with list\_jobs, create\_job, list\_shifts, list\_time\_off\_requests, create\_shift and publish\_shifts, called by your AI agent, an n8n workflow or a script.

[Request access](https://cotlet.dev/app/signup?app=clockshark) [All ClockShark tools](https://cotlet.dev/integrations/clockshark-api-mcp-server)

Hosted · nothing to install or maintain

Official options

## Can ClockShark do this on its own?

ClockShark has no public API for schedules; Zapier can create a job and fires when a schedule is created, but cannot add a shift (checked 10 Oct 2026). ClockShark offers the web scheduler and the mobile Schedule tab, and Pro plan accounts on Simpro Premium can sync schedules from Simpro instead (checked 12 Oct 2026). Without Simpro, every shift is built by hand from wherever the job arrived: an email, a quote or a phone call.

By hand

## How you do it in ClockShark today

1. Create the job first, because SCHEDULES only offers the jobs in its list on the left side to drag onto an employee.
2. Drag the job onto an employee date block. ClockShark creates an all-day shift with no start or end time, so each one needs the pencil icon, All Day switched off and times set.
3. For several people at once, click Add Shift, pick start and end dates and times, Employees, Job, Task and Notes, then click Publish, or Save Draft to hold it back.
4. Draft shifts show with a dotted border, and the Publish button at the top right counts the drafts in the date range before publishing them in bulk.
5. Toggle the schedule between the job and employee views to check that every job has people on it. It is all done again for every new job, and the scheduling articles we read describe no warning when someone is already booked elsewhere.

With an agent

## How to schedule a crew on a new job in ClockShark

Prompt

```
Create a job for 42 Oak Street and put Ana and Luis on it Monday to Wednesday, 7:00 to 15:30. Check nobody is booked elsewhere and show me the drafts before you publish.
```

1. 01  
### Reuse the job if it exists  
The agent searches list\_jobs by address or number before calling create\_job, so a job the office already entered is not duplicated. A new job gets the budget hours from the quote when you give them.
2. 02  
### Check who is free  
list\_shifts for the dates shows every crew member's existing shifts, drafts included, and list\_time\_off\_requests shows pending and approved time off. A person booked on another job or off that day is reported with an alternative, never double booked.
3. 03  
### Draft one day at a time  
Each create\_shift call covers one start and end, so the agent drafts one call per working day with the same crew, task and notes. Weekends are skipped unless you ask for them.
4. 04  
### Show the drafts, then publish only those  
You see the drafted week as a short list before anything reaches the crew. publish\_shifts waits for your OK and gets only the shift IDs just created, so other drafts in that week stay hidden.
5. 05  
### Stop when Simpro owns the schedule  
If the account syncs schedules from Simpro, the agent stops and says so, because shifts made in ClockShark never reach Simpro and the next sync overwrites edits to imported ones.

### What you get back

Example data

```
Job created: 2041 42 Oak Street, Harlow Homes, 320 budget hours
Drafted 6 shifts, Mon 13 to Wed 15 Oct, 7:00 to 15:30, task Framing
Ana Silva: 3 shifts. Luis Ortega: 3 shifts
Clash check: no other shifts or time off for Ana or Luis on those days
Published 6 shifts after your OK, visible in the crew app now
```

### Other ways to ask

- Put the framing crew on 42 Oak Street next week, Monday to Friday, but leave the shifts as drafts.
- Copy this week's crew on 42 Oak Street to next week and publish after I check it.
- Here is the job email from Harlow Homes. Create the job and schedule two people for the dates in it.

Before you automate it

## What ClockShark allows, and what to know first

- Dragging a job onto the ClockShark schedule makes an all-day shift with no start or end time until someone edits it.
- ClockShark draft shifts stay hidden from the crew until published, and a published shift can be turned back into a draft with Unpublish.
- A published ClockShark shift appears in the employee's mobile app right away, and later changes to time, job or notes sync to the app on their own.
- ClockShark does not write schedule changes to the Audit Log, unlike timesheet edits.
- With Simpro schedule sync on (ClockShark Pro plan), Simpro is the source of truth: most changes arrive within about an hour, and shifts whose job or employee is not synced yet are skipped.

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

Sources: [ClockShark: Scheduling employees, web and mobile](https://help.clockshark.com/scheduling-employees-web-and-mobile) · [ClockShark: Draft schedules](https://help.clockshark.com/draft-schedule) · [ClockShark: Sync your Simpro schedule into ClockShark](https://help.clockshark.com/sync-your-simpro-schedule-into-clockshark) · [ClockShark: Audit Log FAQ](https://help.clockshark.com/audit-log-faq)

REST

## Call create\_shift from a script

curl

```
curl https://cotlet.dev/api/v1/clockshark/create_shift \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"employee_ids":["e_48213","e_48219"],"job_id":"j_3307","start":"2026-10-13T07:00:00-05:00","end":"2026-10-13T15:30:00-05:00"}'
```

Example response

```
{
"shifts": [
{
"shift_id": "s_77201",
"employee_id": "e_48213",
"job_id": "j_3307",
"start": "2026-10-12T07:00:00-05:00",
"end": "2026-10-12T15:30:00-05:00",
"status": "draft"
},
{
"shift_id": "s_77202",
"employee_id": "e_48219",
"job_id": "j_3307",
"start": "2026-10-12T07:00:00-05:00",
"end": "2026-10-12T15:30:00-05:00",
"status": "draft"
}
]
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is clockshark\_create\_shift. Example data.

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

Tools

## ClockShark tools this automation uses

__Cotlet ClockShark tools used to schedule a crew on a new job in ClockShark__
| Tool | Parameters |
| ------------------------- | ----------------------------------------------------------- |
| list\_jobs | active, customer, search |
| create\_job | name, number, customer, address, description, budget\_hours |
| list\_shifts | from, to, employee\_ids, status |
| list\_time\_off\_requests | status |
| create\_shift | employee\_ids, job\_id, start, end, task\_id, notes |
| publish\_shifts | shift\_ids, from, to |

[All 15 ClockShark tools with descriptions](https://cotlet.dev/integrations/clockshark-api-mcp-server#tools)

## More ClockShark automations

- [Approve ClockShark timesheets before payroll](https://cotlet.dev/integrations/clockshark-api-mcp-server/approve-weekly-timesheets)
- [Fix missed clock outs in ClockShark every morning](https://cotlet.dev/integrations/clockshark-api-mcp-server/fix-missed-clock-outs)
- [Approve ClockShark time off requests against the schedule](https://cotlet.dev/integrations/clockshark-api-mcp-server/approve-time-off-requests)
- [ClockShark API and MCP server: every tool](https://cotlet.dev/integrations/clockshark-api-mcp-server)
- [All use cases](https://cotlet.dev/use-cases)

## Give your agent access to ClockShark.

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

[Request access](https://cotlet.dev/app/signup?app=clockshark)