updateTask
Fix an existing task by taskId + its linked contactId.
Fix an existing task by taskId + its linked contactId (from listMyTasks or listContactTasks): title, description, taskType, dueDate (ISO, with timezone), timezone, or participants (teammate userIds from listTeammates). PATCH: only the fields you pass change; participants REPLACES the whole assignee list. UNDO: Task keeps no history, but every edit on a contact-linked task writes an UPDATED_TASK entry with oldValues to the contact's timeline (listContactActivities; one per edit, the oldest holds the original): read it and write the old value back; never call a value unrecoverable without looking. WHOSE TASK: empty participants = UNASSIGNED, nobody's; a NON-EMPTY list that does not include the key owner is a TEAMMATE's task: an admin key may write it, but say whose first; a queue read is never proof a task is the reader's. The tool for 'push that follow-up to Friday': reschedule in place; many tasks to one date is rescheduleTasks. contactId IDENTIFIES the task's existing contact, it does NOT move it: any other is rejected, and nothing here re-links a task. Delete-then-recreate is NOT a move (it loses completedAt, the outcome, the created date and every notification and automation link) so say the task can't be moved, and rebuild it only if they ask after hearing that. To tick a task off use completeTask. A task with no contact: updateTaskOnDeal.
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": "updateTask",
"variables": {
"taskId": "<String>",
"contactId": "<String>"
}
}'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.tasks.updateTask(
{
taskId: '<String>',
contactId: '<String>'
},
{ 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: 'updateTask',
variables: {
taskId: '<String>',
contactId: '<String>'
}
}),
})
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.
AZ: Arizona: MST all year, no DST.
Response
What comes back under data: a list shows as one entry, and a value as its type.
{
"data": {
"tasksMutation": {
"updateTaskOnContact": {
"id": "<ID>",
"name": "…",
"tasks": [
{
"id": "<ID>",
"title": "…",
"description": "…",
"taskType": "…",
"dueDate": "2026-01-01T00:00:00.000Z",
"timezone": "IDLW",
"completedAt": "2026-01-01T00:00:00.000Z",
"participants": [
{
"id": "<ID>",
"firstName": "…",
"lastName": "…"
}
]
}
]
}
}
}
}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 →