schedule.setKitListEmail
Set the hour (0 to 23, shop time) the night-before kit list email goes to each worker with visits the next day, or turn it off with on false. Default 18 (6 PM). Owner only.
| Who | Agents can call this |
| REST | POST /v1/schedule/kit-list-email |
| MCP tool | schedule_setKitListEmail |
| Writes | yes, send an Idempotency-Key |
| Area | Scheduling and visits |
When to use it
Read schedule.settings first: it has the shop's time zone, working hours, arrival window and buffer. Use schedule.findTime to get open times that fit the shop's hours, each worker's hours and time off, and visits already booked with the buffer around them, then book with visits.create.
What to tell the owner
Say what you did in plain words and what happens next.
Input
| Field | Type | Required |
|---|---|---|
shop_id | string (uuid) | yes |
on | boolean | yes |
hour | integer | no |
Example
POST https://doingwork.work/v1/schedule/kit-list-email
content-type: application/json
Idempotency-Key: 3f1c...
{
"shop_id": "00000000-0000-4000-8000-000000000000",
"on": true
}Output
JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.
Errors
| Code | Status | What to do |
|---|---|---|
invalid_input, invalid_token, rate_limited | Can happen on any call. See errors. |