GoliathDevelopersGet an API key
Reference/Workflowsgenerated from the gateway manifest

updateWorkflowSendWindow

Set the workflow's SENDING SCHEDULE, the hours its messages may go out.

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

Set the workflow's SENDING SCHEDULE, the hours its messages may go out. It belongs to the workflow (group id), not a version, so it applies to the LIVE workflow at once: every run reads it on its next send, whichever version it started on, with no draft or promote. A run already waiting for the old schedule's next opening keeps that wait and re-checks when it wakes. sendWindow is {timezone, days:[{day:"MON".."SUN", intervals:[{start:{hour,minute}, end:{hour,minute}}]}], timezoneMode?}, with the rules updateWorkflowGraph gives under SEND WINDOW; an absent day is CLOSED, and a window naming no days or hours is refused. null clears it to the platform default (Mon-Fri 09:00-19:00 org time). Read it from getWorkflow.sendWindow. The ONLY way to change it: updateWorkflowGraph refuses a graph carrying a different one.

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": "updateWorkflowSendWindow",
    "variables": {
      "workflowGroupId": "<workflowGroupId>"
    }
  }'
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.workflows.updateWorkflowSendWindow(
  {
    workflowGroupId: '<workflowGroupId>'
  },
  { 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: 'updateWorkflowSendWindow',
    variables: {
      workflowGroupId: '<workflowGroupId>'
    }
  }),
})
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.

workflowGroupIdID!required
sendWindowJSON

Response

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

response shape
{
  "data": {
    "workflowAutomationsMutation": {
      "updateWorkflowGroupSendWindow": {
        "id": "<ID>",
        "name": "…"
      }
    }
  }
}

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 →

READlistWorkflowsREADgetWorkflowREADgetWorkflowVersionGraphREADlistWorkflowRunsREADgetContentTemplateREADlistContentTemplates