`email_person`

Propose an email to a person. Propose an email to one person for the owner's yes, in their thread, on a task you hold. person_id comes from people, never an address. Not for: several people or a newsletter (propose kind email).

Where it is

Always listed: call it by its name.

Does it need a yes?

Needs the owner's yes: it makes a yes card, and nothing happens until the owner taps yes. Here: an email waits for its yes.

Inputs

Input	Type	Needed	About
`person_id`	string	yes	The person's id (from people or file_email). · format `^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$`
`subject`	string	yes	1 to 200 characters
`text`	string	yes	The whole email, plain text. · 1 to 50,000 characters
`kind`	"email" \| "reply"	no
`number`	integer	yes	The task you hold. · 1 or more
`reply_to`	string	no	The message id (from thread) this answers. · format `^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$`
`run_id`	string	yes	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "email_person",
  "arguments": {
    "person_id": "person id",
    "subject": "Your booking",
    "text": "Hi Ana, thanks for your message.",
    "number": 1,
    "run_id": "the run_id from start"
  }
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.