---
title: "Create Workbench Bindings"
method: POST
path: "/workbench-bindings"
tags: ["Workbench"]
---

# Create Workbench Bindings

`POST /workbench-bindings`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/workbench-bindings`
- Auth: HTTP bearer

Show a workflow's outputs as columns on a list. FREE.

Requires WRITE access to the list. The columns appear on the list's next
column fetch; their values fill in when the workflow runs.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- CreateWorkbenchBindingsRequest: Bind a workflow's outputs to columns on one list.
  - `list_id` integer, required: The list whose grid gains the columns.
  - `workflow_id` string, required: The workflow producing the values.
  - `bindings` WorkbenchBindingItem[], required: At least one. The app refuses an empty set; so does this.
    - `node_id` string, required: The workflow node whose output feeds the column.
    - `output_path` string, required: Dot path into that node's output.
    - `column_name` string, required: Display name of the column.
    - `column_type` 'computed' | 'ai' | 'enrichment' | 'state' | 'action' | 'review', required: How the grid treats the column.
    - `display_mode` string: How the cell renders.
    - `sort_order` integer: Position among the bound columns.
    - `config` object, nullable: Column-type settings.

## Response `201`

Successful Response

- ApiResponseEnrichmentListPayload
  - `data` EnrichmentListPayload, required: A collection result. `items` is ALWAYS present, so a caller can iterate without knowing whether the handler returned a bare list or a named key. When the handler used a named key that key is preserved beside `items` rather than renamed, because renaming it would make the API and the app disagree about the same data.
    - `items` unknown[]: The collection, always present.
      - unknown
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)