# getWorkflowVersionGraph

Fetch one workflow VERSION by workflowAutomationId (from getWorkflow.versions/currentVersion/pendingDraft) with its full node/edge graph: the superjson-serialized WorkflowGraph updateWorkflowGraph writes back. Its `triggers` array shows what starts runs; updateWorkflowGraph documents the trigger shapes, how to add or remove them, and the FULL step vocabulary (far more than text steps). Read `graph.config` before answering about BEHAVIOUR rather than steps: exit conditions, sender selection and the trigger operator live there, not on a node. The SENDING schedule does not: it is getWorkflow.sendWindow. `inWords` states the triggers and the stop rules in words, and `inWords.names` names every tag, list, teammate or stage the graph holds by id (a tag and a list share names: read `kind`). Describe the workflow from these, never from its name or description; keep every stop rule unless the person asks to drop that one. TRIGGERS ARE NOT THE ONLY WAY IN. Steps in OTHER workflows enroll records into this one: a PROPERTY `create_contact_action` (the contact it creates), a `trigger_contact_workflow_action` (start another workflow), and an EVENT `find_create_contact_action` / `event_find_property_action`. A workflow whose only trigger is {type: "manual"} is normal when it is fed that way: never call it idle or unreachable from its triggers alone. getDeletionImpact(targetKind: WORKFLOW_GROUP, targetId: <this group id>) says whether anything references it: its WORKFLOW_AUTOMATION group counts REFERENCES (each step, trigger or filter in each live version naming this one, so one workflow can count more than once), not names. To see WHICH workflows feed it, scan other workflows' graphs (getWorkflowVersionGraph) for a step naming this group id. TO CHANGE WHAT A WORKFLOW DOES (add a condition, change a trigger, narrow who it acts on), edit its graph: createOrReturnWorkflowDraft → updateWorkflowGraph → promoteWorkflowDraft, then resumeWorkflow if it was paused. Pausing only stops it. E.g. a PROPERTY workflow can require a motivation signal before it creates or texts anyone: a `conditional` step on the `hasSignal` or `propertySignalTypes` property filter fields (listFilterFieldNames lists them) ahead of the `create_contact_action` step. Never tell a user restricting outreach this way needs human review: it is a graph edit. WEBHOOK SECRETS ARE REDACTED. A `send_webhook_action` step's `config.auth.secret` reads as the literal `__GOLIATH_WEBHOOK_SECRET_REDACTED__`: never the credential, never a value to quote or reason about. Send it BACK UNCHANGED in updateWorkflowGraph to keep the stored secret, and a different string only when the user is deliberately rotating it. Never invent, guess or complete a replacement: that overwrites a working credential. The sentinel on a step with no stored secret behind it (a step you just added, or a graph read so long ago its node ids rotated) is REFUSED: re-read the graph and carry it from the fresh copy.

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "getWorkflowVersionGraph", "variables": {...} }`
- Scope: `READ`
- Type: query
- Idempotency: a read; rejects `Idempotency-Key`
- Rate-limited: no

## Variables

- `workflowAutomationId`: `ID!` (required)

## Response (data, an example)

```json
{
  "workflowAutomationsQuery": {
    "workflowAutomation": {
      "id": "<ID>",
      "workflowGroupId": "<ID>",
      "name": "…",
      "description": "…",
      "status": "DRAFT",
      "channels": [
        "TEXT"
      ],
      "workflowDomain": "PROPERTY",
      "stepKinds": [
        "…"
      ],
      "updatedAt": "2026-01-01T00:00:00.000Z",
      "inWords": {
        "triggers": [
          "…"
        ],
        "triggerOperator": "…",
        "stopsWhen": "…",
        "names": [
          {
            "id": "<ID>",
            "name": "…",
            "kind": "…"
          }
        ]
      },
      "graph": "…"
    }
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operationId": "getWorkflowVersionGraph",
    "variables": {
      "workflowAutomationId": "<workflowAutomationId>"
    }
  }'
```