`email_domain`

Email domain. Who emails come from now (sender: ready from day one, replies to the office inbox), and the optional own email domain: see where it stands, with the owner's DNS lines; setting one up waits for the owner's yes (on task).

Where it is

In the inbox area (filing an email on a person's card): open it with tools_for { area: "inbox" }, then call it with use_tool { name: "email_domain", args }.

Does it need a yes?

Needs the owner's yes: it makes a yes card, and nothing happens until the owner taps yes. Here: reading is direct; setting it is a company_setting yes.

Inputs

Input	Type	Needed	About
`domain`	string	no	Like studio.com; leave out to read. Setting it waits for the owner's yes. · up to 200 characters
`task`	integer	no	With domain: the task you hold, where the owner's yes is asked. · 1 or more
`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_domain",
  "arguments": {
    "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.