setEmployeeStatus
Switch an AI employee on (ACTIVE) or off (INACTIVE).
Switch an AI employee on (ACTIVE) or off (INACTIVE). ON means it starts answering and working the contacts it is on, with real people, right away, which may publish its answer workflows; OFF stops it mid-conversation on every contact it is working. Say which and to how many contacts (getEmployee's commitments) and get the person's yes before either. The employee's own chat records the change. Same as the switch on the employee's page.
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": "setEmployeeStatus",
"variables": {
"employeeId": "<employeeId>",
"status": "ACTIVE"
}
}'import { GoliathClient } from '@goliath-data/sdk'
const goliath = new GoliathClient({
apiKey: process.env.GOLIATH_API_KEY!,
baseUrl: 'https://server.goliathdata.com',
})
// Enum values as strings: the SDK's enum types aren't exported yet, so assert to the method's variables type.
const variables = {
employeeId: '<employeeId>',
status: 'ACTIVE'
} as Parameters<typeof goliath.employees.setEmployeeStatus>[0]
const result = await goliath.employees.setEmployeeStatus(variables, { idempotencyKey: crypto.randomUUID() })const res = await fetch('https://server.goliathdata.com/api/v1/call', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
'Content-Type': 'application/json',
'Idempotency-Key': crypto.randomUUID(),
},
body: JSON.stringify({
operationId: 'setEmployeeStatus',
variables: {
employeeId: '<employeeId>',
status: 'ACTIVE'
}
}),
})
const { data, errors } = await res.json()Variables
The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.
Response
What comes back under data: a list shows as one entry, and a value as its type.
{
"data": {
"aiEmployeesMutation": {
"setContactAgentStatus": {
"id": "<ID>",
"name": "…",
"status": "ACTIVE",
"updatedAt": "2026-01-01T00:00:00.000Z"
}
}
}
}Errors
unknown_variableA variable the operation does not declare. A typo is refused rather than silently dropped.
unauthorizedNo bearer header, or the key is invalid or revoked.
insufficient_scopeThe key lacks the scope the operation requires.
forbiddenA referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.
idempotency_conflictA request with this Idempotency-Key is still in flight.
Idempotency
Send an Idempotency-Key of 1 to 255 characters. A finished request retried with the same key replays its stored response, marked Idempotency-Replayed: true; one still in flight returns 409 idempotency_conflict. Keys expire after 24 hours. Write without fear →