setEmployeeCallTransfers
Set who an AI employee puts a live call through to when a caller asks for someone. destinations REPLACES the saved list.
Set who an AI employee puts a live call through to when a caller asks for someone. destinations REPLACES the saved list (send every one to keep; [] turns transfers off): each is { name, phoneLineId }, name the person as callers ask for them (unique ignoring case), phoneLineId one of the organization's own lines, an organization.twilioPhoneNumbers[].id from listCommunicationChannels (its user.id is the teammate the line belongs to; listTeamMembers names them). At most 10. The call rings that line's routing, so a number the organization does not own, such as a personal cell, cannot be one. This is the live transfer: a line in its instructions alone makes it say it is transferring on a call that never connects. Refused on an employee with no call channel (getEmployee configDocument.channels.callConfig absent). Pass expectedUpdatedAt. On an employee that is switched on it takes effect on its next run: needs their yes; a card’s counts.
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": "setEmployeeCallTransfers",
"variables": {
"employeeId": "<employeeId>",
"destinations": [
{
"name": "<String>",
"phoneLineId": "<phoneLineId>"
}
]
}
}'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.setEmployeeCallTransfers(
{
employeeId: '<employeeId>',
destinations: [
{
name: '<String>',
phoneLineId: '<phoneLineId>'
}
]
},
{ 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: 'setEmployeeCallTransfers',
variables: {
employeeId: '<employeeId>',
destinations: [
{
name: '<String>',
phoneLineId: '<phoneLineId>'
}
]
}
}),
})
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": {
"setAiEmployeeCallTransfers": {
"id": "<ID>",
"name": "…",
"config": {
"channels": {
"callConfig": {
"transferDestinations": [
{
"name": "…",
"phoneLineId": "<ID>"
}
]
}
}
},
"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 →