# createEmployee

Hire an AI employee. It is ALWAYS created switched off (INACTIVE), whatever the config says: it answers nobody until it is switched on. Omit `config` for the generalist an operator gets with no template (texts, emails and calls once a phone line or mailbox is attached, notes, tasks, notifying a teammate, booking its own follow-up), then shape it with updateEmployeeConfig; or pass a COMPLETE config document in the shape getEmployee returns as `configDocument`. The same checks the employee builder runs apply, and a refusal names each field and what to change. Returns the new employee and its `configDocument`.

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "createEmployee", "variables": {...} }`
- Scope: `WRITE`
- Type: mutation
- Idempotency: honors `Idempotency-Key` (24 h)
- Rate-limited: no

## Variables

- `name`: `String!` (required)
- `title`: `String`
- `avatar`: `String`
- `origin`: `String`
- `config`: `JSON`

## Response (data, an example)

```json
{
  "aiEmployeesMutation": {
    "createAiEmployee": {
      "id": "<ID>",
      "name": "…",
      "title": "…",
      "status": "ACTIVE",
      "configDocument": "…",
      "updatedAt": "2026-01-01T00:00:00.000Z"
    }
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "createEmployee",
    "variables": {
      "name": "<String>"
    }
  }'
```