List Lists

wekan.list_lists

ActionBusiness appsconnection required

Calls the Wekan API with the connection's credentials.

List a board's lists, the columns cards are arranged into.

Connection

Required: Yes — the node will not save without one
Auth type: Bearer token
Providers: Wekan
Secret shape: the Wekan API token as {"token": "…"}, or {"username": "…", "password": "…"} to log in with
Config it needs: base_url, user_id
Resolved by: config.connection_id, else node.connection_id

1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
board_id Wekan's id for the board. It is the long identifier in the board URL, not its title.	string	Yes	—	—	wJmnfd4bLLYAoRcS2

Every value below is the contract’s own example or default — nothing invented.

{
  "board_id": "wJmnfd4bLLYAoRcS2"
}

One shape.

Field	Type	Example
items The board's lists, in Wekan's own order.	array	—
items[]._id Wekan's id for the list.	string	—
items[].title The list's title.	string	—
items[].modifiedAt When the list document itself last changed.	string	—
items[].cardsModifiedAt When a card in this list last changed, so a caller can tell whether the list's contents moved without fetching every card.	string	—
count How many lists were returned.	number	—

{
  "count": 0,
  "items": [
    {
      "_id": "",
      "cardsModifiedAt": "",
      "modifiedAt": "",
      "title": ""
    }
  ]
}

In a technical demo we add the Wekan connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.