Skip to main content
POST
Hand an AI employee a piece of work
The employee plans the work, reads through its tools and your knowledge straight away, and proposes actions. Each one goes through your approval policy: an action that needs a person waits in the approval queue; one your policy lets run is carried out at once, on your authority.
AI employees are in beta. Every route answers 404 unless your deployment has switched the beta on. A tool with no saved connection reaches nothing: an approved action on it is recorded as not_sent, with the draft to use by hand (Connect your tools). See AI employees.
The plan is fixed for each employee. Nothing in the text you send chooses what it does: an access request or a password reset is only ever for requester, and only for an application in your catalogue. Requires owner, admin or editor. Returns 201.
string
required
Which employee: support, itsm (IT service desk), devops, marketer, sales or finance.
string
required
What the work is about. Cut at 200 characters.
string
The message, ticket text or alert detail. Cut at 8,000 characters.
string
Who asked, as your channel reported it. An identity change is only ever for this person. For Sales, the lead’s email address: the follow-up is only ever sent to it, and its domain is the company website read when your CRM holds none. For Finance, who a reply goes to.
string
Where it came from, such as email, slack or alert.
string
Its ID in that channel: a ticket key, a thread or an incident. For Sales, the lead’s CRM record ID.
string
DevOps only, and required for it: the service the alert is about.
string
The assistant whose knowledge answers questions in this work. The answer is a normal conversation on that assistant and counts against your monthly answers. Another organisation’s assistant returns 404.

Response

string
required
The task’s ID.
string
required
support, itsm, devops, marketer, sales or finance.
string
required
waiting_for_approval or done.
string
required
ISO 8601.
string
required
Who handed the work over.
object
required
The work as it arrived: title, body, requester, channel, reference, service, assistant_id.
object[]
required
The steps, in order: description, kind (read or action) and, for an action, its action_id.
object[]
required
Every action it proposed, in the shape Approve an action returns.
Last modified on November 7, 2026