Create Checklist
wekan.create_checklist
ActionBusiness appsconnection required
Calls the Wekan API with the connection's credentials.
Add a checklist to a card, optionally with its items.
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
Configuration
4 fields, 3 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 |
card_id Wekan's id for the card, as returned by wekan.list_cards or wekan.create_card. | string | Yes | — | — | wJmnfd4bLLYAoRcS2 |
title The checklist's title, shown above its items on the card. | string | Yes | — | — | Release steps |
items The checklist items to create, in order. A plain string is accepted too and is split into one item per line. | array | No | — | array of string | ["Tag the release","Publish the changelog"] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"board_id": "wJmnfd4bLLYAoRcS2",
"card_id": "wJmnfd4bLLYAoRcS2",
"items": [
"Tag the release",
"Publish the changelog"
],
"title": "Release steps"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
_id The id Wekan gave the new record. | string | — |
{
"_id": ""
}Related Wekan nodes
See Create Checklist run in a workflow.
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.