GoliathDevelopersGet an API key
Reference/Employeesgenerated from the gateway manifest

attachEmployeeToContacts

Put an AI employee on contacts (at most 200 ids per call; send more in further calls).

POST/api/v1/callWRITEidempotent · 24 hruns as the key's owner
View as Markdown

Put an AI employee on contacts (at most 200 ids per call; send more in further calls). It then answers those contacts' texts, emails and calls and works them. The employee must be switched on (setEmployeeStatus) and every contact one the key owner can open. Recorded as the key owner's own assignment, so a contact someone took the employee off is put back because you named it. changedCount is how many it was newly put on; the rest already had it. When interruptedContactId is set the batch stopped there (interruptedReason says why): the contacts before it are done, so send that one and the rest again. Confirm the contacts with the person first.

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": "attachEmployeeToContacts",
    "variables": {
      "employeeId": "<employeeId>",
      "contactIds": [
        "<contactIds>"
      ]
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

const result = await goliath.employees.attachEmployeeToContacts(
  {
    employeeId: '<employeeId>',
    contactIds: [
      '<contactIds>'
    ]
  },
  { 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: 'attachEmployeeToContacts',
    variables: {
      employeeId: '<employeeId>',
      contactIds: [
        '<contactIds>'
      ]
    }
  }),
})
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.

employeeIdID!required
contactIds[ID!]!required

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "aiEmployeesMutation": {
      "attachAiEmployeeToContacts": {
        "requestedCount": 0,
        "changedCount": 0,
        "interruptedContactId": "<ID>",
        "interruptedReason": "…"
      }
    }
  }
}

Errors

400unknown_variable

A variable the operation does not declare. A typo is refused rather than silently dropped.

401unauthorized

No bearer header, or the key is invalid or revoked.

403insufficient_scope

The key lacks the scope the operation requires.

403forbidden

A referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.

409idempotency_conflict

A 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 →

READlistEmployeesREADgetEmployeeREADgetEmployeeCaseloadREADlistEmployeeChannelOptionsREADlistEmployeeSuggestionsREADlistEmployeeRevisions