visits.draftRecap

Draft the recap email for the customer after a visit. For a detailed recap, pass body (the full email) or what_happened, options_discussed and next_steps. Leave those out to use the short template: what_we_saw in the worker's own words (or measurements from a saved recording) and the next step. Private worker_notes from a recording are never included, and a draft that contains them is refused. Nothing is sent: show the worker the draft, edit it with visits.editRecap, and send only when they approve with visits.approveRecap. Drafting again replaces the open draft.

WhoAgents can call this
RESTPOST /v1/visits/recap/draft
MCP toolvisits_draftRecap
Writesyes, send an Idempotency-Key
AreaScheduling and visits

When to use it

Draft the recap email for the customer after a visit. For a detailed recap, pass body (the full email) or what_happened, options_discussed and next_steps.

What to tell the owner

Say what you did in plain words and what happens next.

Input

FieldTypeRequired
visit_idstring (uuid)yes
what_we_sawarrayno
next_stepstringno
subjectstringno
bodystringno
what_happenedstringno
options_discussedstringno
next_stepsstringno

Example

POST https://doingwork.work/v1/visits/recap/draft
content-type: application/json
Idempotency-Key: 3f1c...

{
  "visit_id": "00000000-0000-4000-8000-000000000000"
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

CodeStatusWhat to do
invalid_input, invalid_token, rate_limitedCan happen on any call. See errors.