Resources · n8n integration

Wekan n8n integrationAutomate Wekan with n8n.

Your Wekan board is the place work becomes visible, so it should not be filled by hand. The Wekan n8n integration exposes 6 resources and 24 operations, from creating a board to checking off a single checklist item. Wekan ships no trigger node, so another trigger starts the workflow.

Try the Wekan integration on n8n See the 24 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Wekan n8n integration actually do?

The Wekan node ships inside n8n and talks to the REST API of the Wekan server you run yourself. It covers 6 resources, board, list, card, card comment, checklist and checklist item, through 24 operations. A single workflow can open a board, fill it with lists and cards, comment on those cards, then tick checklist items off days later. Authentication is basic auth against the domain where Wekan answers.

Start with the case the node was clearly built for: a board that builds itself. board.create opens the board, list.create adds the columns you always use, and card.create drops the first cards in. That is exactly the shape of the public template 728, which chains a board, its lists and a card in one run. For a project studio that spins up the same structure for every client, this replaces a manual copy of a board.

The second case reads instead of writing. card.getAll pulls the cards of a list, and the rest of the workflow decides what to do with them: a weekly count pushed into Google Sheets, a digest of what is still open posted to Slack, or a sync of statuses towards Jira Software when engineering lives elsewhere. Turn on Return All when the list is long, because n8n otherwise stops at Limit.

The third case is onboarding. One card per new hire, one checklist per week of the plan, and a workflow that flips each item to finished as the training tools report progress. checklist.create accepts its Items upfront, so the whole checklist arrives in one call rather than item by item.

Use the HTTP Request node when the endpoint you need sits outside these 24 operations. It reuses the same Wekan credential through predefined authentication, so nothing is duplicated. Two limits are worth knowing before you build. Every operation expects Wekan IDs, not titles, which is why most parameters are dropdowns that can also take an expression. And loading dropdowns such as the author list requires admin permissions on the Wekan user behind the credential.

The last limit is structural: Wekan has no trigger node in n8n. A Schedule Trigger on a fixed interval or an n8n Webhook called by another service starts the run. If you want the wider picture of the platform first, the n8n review and the n8n training cover how these pieces fit together.

Connect

How do you connect Wekan to n8n?

01
Get a Wekan server running
The node talks to your own instance, so Wekan has to be installed on a server you control before anything else. Note the domain where it answers, because that value goes straight into the credential. n8n itself can sit next to it on the same self-hosted setup, or on n8n Cloud, the hosted offer run by n8n. The workflow is identical either way, only the network path between n8n and Wekan changes.
02
Create the Wekan credential
In n8n, open the Credentials menu and pick the Wekan credential. It uses basic auth and asks for three values: Username, your Wekan username, Password, the password of that same account, and URL, the Wekan domain noted in step one. A credential is created once and reused by every workflow, so you never retype it. The node then offers it in its own dropdown.
03
Test it on a read operation
Add a Wekan node, choose the Board resource and the Get Many operation, then pick a user in User Name or ID. Running the node once tells you whether the credential answers and whether the account sees the boards you expect. A read costs nothing in Wekan and shows you the real ID format, which you will paste into expressions such as {{ $json._id }} further down the workflow.

Actions

What can the Wekan node do?

The Wekan node exposes 24 operations across 6 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create	Get	Get Many	Update	Delete
Board	✓	✓	✓		✓
Card	✓	✓	✓	✓	✓
Card Comment	✓	✓	✓		✓
Checklist	✓	✓	✓		✓
Checklist Item		✓		✓	✓
List	✓	✓	✓		✓

Board

4 operations

Create a board

board.create

What you see in n8n

Notes & use cases

This operation opens a new board in Wekan and returns its ID, the value every other operation asks for.

Key parameters

Title: the board name as it appears in Wekan, for example a client name or a sprint number.
Owner Name or ID: the Wekan user ID that owns the board, picked from the list or set with an expression.
Additional Fields: 7 optional settings, including Permission (private or public), Color among 6 themes, and Admin to make the owner a board admin.

Use cases

a studio that runs one board per client creates it the moment the deal is signed, with the same color code every time.

Delete a board

board.delete

What you see in n8n

Notes & use cases

Removes a board from Wekan by ID. The call is final, so most workflows put a condition or a manual approval in front of it.

Key parameters

Board ID: the ID of the board to delete, typed as a plain string rather than chosen from a list, usually carried over from an earlier node with an expression.

Use cases

a monthly cleanup workflow that lists boards, filters the ones created for a demo, and deletes only those.

Get a board

board.get

What you see in n8n

Notes & use cases

Reads a single board and returns its data, which lets the rest of the workflow branch on what it finds.

Key parameters

Board ID: a string field, so the value comes from a previous node or from a board ID you keep in the workflow.

Use cases

before creating a card, check that the target board still exists and read its title, so the notification sent afterwards names the board instead of showing a raw ID.

Get many boards

board.getAll

What you see in n8n

Notes & use cases

Returns the boards attached to one Wekan user, which is how a workflow discovers what exists instead of hard coding IDs.

Key parameters

User Name or ID: the user whose boards you want, chosen from the list or given as an ID through an expression.
Return All: on, n8n walks the pages of the API and brings back every board; off, Limit caps the number of boards returned.

Use cases

an audit that lists every board of a service account, then feeds a spreadsheet with what is actually in use.

Card

5 operations

Create a card

card.create

What you see in n8n

Notes & use cases

Adds a card to a list and returns its ID. Five required parameters place the card precisely inside Wekan.

Key parameters

Board Name or ID and List Name or ID: where the card lands, board first, then the column inside it.
Swimlane Name or ID: the horizontal lane of the new card, required even when your board uses a single lane.
Author Name or ID: the Wekan user credited with the card.
Title: the card name, often {{ $json.title }} from the incoming item.
Additional Fields: 3 optional values, Description, Assignee Names or IDs and Member Names or IDs.

Use cases

a support request received by email becomes a card in the intake column, description filled with the message body.

Delete a card

card.delete

What you see in n8n

Notes & use cases

Drops one card from Wekan. The node walks down the hierarchy to find it, so three IDs travel together.

Key parameters

Board Name or ID: the board the list belongs to.
List Name or ID: the list holding the card.
Card Name or ID: the card to delete, from the dropdown or via an expression.

Use cases

a duplicate detector that compares incoming tickets, keeps the oldest card and deletes the copy created by a double submission.

Get a card

card.get

What you see in n8n

Notes & use cases

Fetches one card and hands its data to the next node, title and description included.

Key parameters

Board Name or ID and List Name or ID: the path leading to the card.
Card ID: a plain string here, unlike the delete operation, so the ID comes from an expression such as {{ $json.cardId }}.

Use cases

a daily reminder that reads the card behind a due date and includes its current description in the message sent to the assignee.

Get many cards

card.getAll

What you see in n8n

Notes & use cases

Returns the cards of a list or of a swimlane, depending on how you tell the node to look.

Key parameters

From Object: list or swimlane, the axis the node reads along.
Board Name or ID and List Name or ID: the board and the column being read.
Swimlane Name or ID: optional, and useful when the board splits work by team or by client.
Return All: on, every card comes back page after page; off, Limit stops the read.

Use cases

a Monday workflow that counts the cards still sitting in the doing column and posts the number to the team channel.

Update a card

card.update

What you see in n8n

Notes & use cases

Changes an existing card without touching the fields you leave alone. This is also the operation that moves a card between columns.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card being edited.
Update Fields: 17 optional values. List Name or ID inside the collection performs the move, Due At, Start At and End At carry dates, Color flags the card visually, Spent Time records effort.

Use cases

when an invoice is marked paid in the billing tool, the matching card slides to the closed column and turns green.

Card Comment

4 operations

Create a comment on a card

cardComment.create

What you see in n8n

Notes & use cases

Posts a comment under a card, signed by a Wekan user. Comments are the least destructive way for a workflow to write on a board.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card receiving the comment.
Author Name or ID: the user shown as posting it, usually a dedicated automation account.
Comment: the text itself, often built from the data of the previous node.

Use cases

every reply received on a support thread is copied under the card, so the history stays where the team already looks.

Delete a comment from a card

cardComment.delete

What you see in n8n

Notes & use cases

Erases one comment while the card stays untouched.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card the comment sits on.
Comment Name or ID: the comment to remove, picked from the dropdown or resolved earlier by a read operation.

Use cases

a workflow that posts a temporary status under a card and clears its own comment once the real update arrives, so the thread does not fill with noise.

Get a card comment

cardComment.get

What you see in n8n

Notes & use cases

Reads a single comment and returns its content.

Key parameters

Board ID: a string field on this operation, not a dropdown, so pass the ID directly.
List Name or ID and Card Name or ID: the path to the card.
Comment ID: also a string, typically {{ $json._id }} taken from a previous read.

Use cases

a workflow that re-reads the comment it created earlier to confirm the text stored in Wekan matches what was sent.

Get many card comments

cardComment.getAll

What you see in n8n

Notes & use cases

Brings back the comment thread of a card in one call, ready to be summarized or archived.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card whose thread you read.
Return All: on for the entire discussion, off to keep only the first comments up to Limit.

Use cases

when a card reaches the done column, the whole thread is exported into the client report before the board is archived.

Checklist

4 operations

Create a checklist

checklist.create

What you see in n8n

Notes & use cases

Attaches a checklist to a card, and fills it in the same call when you provide the items.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card that receives the checklist.
Title: the checklist name, such as the phase it covers.
Items: optional but the one that saves time, since the items arrive with the checklist instead of one call each.

Use cases

a new employee card gets a first week checklist, laptop, accounts, introductions, created the day the contract is signed.

Delete a checklist

checklist.delete

What you see in n8n

Notes & use cases

Removes a whole checklist from a card in one call.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card holding the checklist.
Checklist Name or ID: the checklist to delete, from the list or through an expression.

Use cases

a template card is copied for every project, and the workflow strips the checklists that do not apply to this one, keeping the card readable.

Get a checklist

checklist.get

What you see in n8n

Notes & use cases

Returns the data of one checklist, items included, so the workflow can measure progress.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: where the checklist lives.
Checklist Name or ID: the checklist to read.

Use cases

a progress bar in a client dashboard, fed by the ratio between finished items and total items on the delivery checklist of the card.

Get many checklists

checklist.getAll

What you see in n8n

Notes & use cases

Lists every checklist attached to a card, which is the entry point when you do not know their IDs yet.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card being inspected.
Return All: on to get them all, off to stop at Limit.

Use cases

a nightly check that opens each card of the delivery column, reads its checklists and flags the cards where nothing has moved.

Checklist Item

3 operations

Delete a checklist item

checklistItem.delete

What you see in n8n

Notes & use cases

Takes a single line out of a checklist, leaving the rest in place.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card concerned.
Checklist Name or ID: the checklist the item belongs to.
Checklist Item Name or ID: the line to remove.

Use cases

an onboarding checklist built for every hire, with the company car line removed automatically when the role does not come with one.

Get a checklist item

checklistItem.get

What you see in n8n

Notes & use cases

Reads one line of a checklist and returns its state, which lets a workflow wait on a precise step.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the path to the card.
Checklist ID: a plain string on this operation, so the value comes from an earlier read.
Checklist Item Name or ID: the item to read.

Use cases

a release workflow that only sends the announcement once the QA line of the checklist comes back finished.

Update a checklist item

checklistItem.update

What you see in n8n

Notes & use cases

Ticks a line off, or renames it, without touching the rest of the checklist.

Key parameters

Board Name or ID, List Name or ID and Card Name or ID: the card concerned.
CheckList Name or ID and Checklist Item Name or ID: the checklist and the exact line.
Update Fields: 2 values, Finished to check the box and Title to rewrite the line.

Use cases

the accounting tool confirms a payment, and the payment received line of the client card is checked without anyone opening Wekan.

List

4 operations

Create a list

list.create

What you see in n8n

Notes & use cases

Adds a column to a board and returns its ID, which cards then use as their destination.

Key parameters

Board Name or ID: the board the column is created in.
Title: the column name, for example the stage of your process.

Use cases

right after board.create, a loop creates the four columns your team always works with, so every new board opens with the same structure.

Delete a list

list.delete

What you see in n8n

Notes & use cases

Deletes a column from a board. Two IDs are enough, since a list belongs directly to its board.

Key parameters

Board Name or ID: the board the list belongs to.
List Name or ID: the column to delete.

Use cases

at the end of a seasonal campaign, the temporary columns created for it are removed while the permanent ones stay untouched.

Get a list

list.get

What you see in n8n

Notes & use cases

One column, read by its ID: the operation hands back its title and its data, handy when a card carries a list ID and nothing else.

Key parameters

Board Name or ID: the parent board.
List ID: a string here, so pass the value through an expression rather than picking it in a dropdown.

Use cases

a notification that says which column a card moved into, by resolving the list ID into a readable name before sending the message.

Get many lists

list.getAll

What you see in n8n

Notes & use cases

Returns the columns of a board, the fastest way to map a board before writing anything to it.

Key parameters

Board Name or ID: the board whose columns you read.
Return All: on, every column comes back; off, Limit caps the result.

Use cases

a workflow that finds the column named after the current month, then creates the card inside it, without any ID written into the node.

Need help

Need help automating Wekan with n8n?

A person reads every message.

FAQ

Wekan and n8n, the questions that come up

01Is the Wekan n8n integration free?

Yes on the n8n side. The Wekan node ships with n8n, so there is nothing to install and no extra cost, whether you run n8n Cloud or a self-hosted instance of the Community Edition under the Sustainable Use license. The same workflow behaves identically in both cases. What you do provide is the Wekan server itself, since the node talks to an instance you install and host. This brief covers the n8n side only, so any cost tied to running Wekan, hosting included, is outside what is documented here and depends entirely on your own setup.

02What credentials does the Wekan node need?

Basic auth, and only that. The Wekan credential in n8n asks for three values: a Username, which is your Wekan username, a Password, the password of that account, and a URL, the domain where your Wekan instance answers. You create that credential once in the Credentials menu and every workflow reuses it, with the node offering it in a dropdown. One detail matters in practice: to load the full parameter lists, author IDs among them, the Wekan account behind the credential needs admin permissions. A normal, comment-only or worker account authenticates fine but leaves several dropdowns empty.

03What are the limits of the Wekan node in n8n?

The node exposes 24 operations across 6 resources: board, list, card, card comment, checklist and checklist item. Anything the Wekan API offers beyond those 24 operations is reachable with the HTTP Request node, which calls any endpoint and reuses the same Wekan credential through predefined authentication. Two practical points. Read operations page through results only when Return All is enabled, otherwise Limit caps what comes back. And every operation works on Wekan IDs rather than names, so a value picked from a dropdown in the editor becomes an expression such as an ID carried from a previous node once the workflow runs on its own.

04Can a Wekan change trigger a workflow in real time?

No, because Wekan has no trigger node in n8n. A workflow that touches Wekan always starts with another trigger. Two options cover most needs. A Schedule Trigger runs at a fixed interval, reads the board with Get Many operations and reacts to what changed since the last run, which fits reporting and cleanup. An n8n Webhook, an URL that a third party service calls, starts the workflow the moment something happens elsewhere, in a form or a billing tool, and the Wekan node then writes the card. The trigger of another tool works exactly the same way.

05n8n or Make for Wekan?

It depends on where your data has to stay. Wekan is software you host yourself, and n8n can be hosted the same way with Docker or npm, so both the board and the automation stay on your own servers. Make, formerly Integromat, is a hosted platform with no self-hosting option, which means calls to your Wekan instance travel through a third party. The cost model differs too: Make bills per operation, while a self-hosted n8n bills you for the machine it runs on. Make offers a visual builder many teams find quicker at first, n8n gives more room for expressions and custom logic.

Get a Wekan server running

Create the Wekan credential

Test it on a read operation

Need help automating Wekan with n8n?