Wekan

· #203 most-used

Self-hosted kanban your agents can drive end-to-end

ProductivityProjectsDocumentsDeveloperAutomation

Wekan is an open-source, MIT-licensed kanban board you host on your own infrastructure — full control, zero vendor lock-in, and a complete REST API that agents can call directly. Connect it to Actionist and your agents can create boards for every new project, route cards between lists as work progresses, attach checklists to enforce quality gates, post progress comments, and react to card events across every team's workflow — all without anyone touching the Wekan UI.

Try Wekan with Actionist Visit Wekan

Average time saved

10 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual work of creating cards from emails and forms, moving cards between workflow stages, posting status updates, and compiling weekly board summaries across every project.

Schedule

What your Wekan agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs

7Agents at work

24/7Always on

Agents

Wed–Fri

Wed

Thu

Fri

10a

11a

12p

Multi-app workflows

Wekan × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows

9Apps spanned

~25 hrsSaved / week

6Personas served

For customer success

Featured4 apps

Support email → Wekan card → Slack in 60 seconds

When a customer email arrives flagged as a support request, your agent creates a Wekan card in the 'New Tickets' list with the sender's name, issue summary, and a 48-hour due date — then reads the board to check current ticket load, posts a status update in the #support Slack channel, and drops a Google Calendar reminder for the follow-up. The customer gets a reply while the team has full kanban visibility, all before anyone opens their inbox.

~8 hrs

Time saved for your team — every week, on autopilot

The flow

Trigger·When a new support email arrives in Gmail

Trigger

Step 1

Gmail

Detect new support email

read

Step 2

Wekan

Get all cards in New Tickets list

write

Step 3

Wekan

Create a new card with issue details and due date

write

Step 4

Slack

Post ticket summary to #support channel

write

Step 5

Google Calendar

Create 48-hour follow-up reminder

Result

Create a new card with issue details and due datePost ticket summary to #support channelCreate 48-hour follow-up reminder

The win

Saved per run

18 min

Runs / week

~25×

Zero missed support tickets

Driven byCustomer Support Agent

ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

Sales
18 min / week
Pipeline card updates
Sales reps manually create and move Wekan cards for each deal stage, often forgetting to update after calls.
Sales Agent
0 min
Agent updates deal cards automatically
Agent creates and moves deal cards the moment Slack or HubSpot signals a stage change — pipeline is always current.
Marketing
13 min / week
Campaign board setup
Marketers manually create a new board and populate lists for each campaign launch, taking 15–20 minutes per campaign.
Marketing Agent
0 min
Agent scaffolds campaign boards instantly
Agent creates the board, adds channel lists, and links to the HubSpot campaign the moment it's created in HubSpot.
Customer Support
18 min / week
Email-to-card triage
Support staff copy-paste inbound emails into Wekan cards, assign them, and post acknowledgement replies manually.
Customer Support Agent
0 min
Agent creates and assigns cards on arrival
Agent parses the email, creates a card with due date and assignee, posts a reply, and pings the team in Slack — all within seconds.
Human Resources
7 min / week
Onboarding board prep
HR coordinators manually create an onboarding card and type out the day-1 checklist for each new hire.
Human Resources Agent
0 min
Agent creates onboarding card with full checklist
Agent creates the card, attaches the standard checklist, assigns the buddy manager, and books the kickoff calendar slot automatically.
Finance
13 min / week
Budget request tracking
Finance manually creates a Wekan card for each budget request received by email, sets SLA dates, and notifies approvers.
Finance Agent
0 min
Agent routes requests to kanban with SLA
Agent creates the card, sets a 5-day SLA due date, and notifies the finance lead the moment the request lands in Notion.
Operations
25 min / week
Spreadsheet-to-board transcription
Ops team manually transfers tasks from the planning spreadsheet to Wekan cards, often with a day's delay.
Operations Agent
0 min
Agent creates cards the moment rows are added
Agent reads the new spreadsheet row and creates a Wekan card with the correct assignee and due date in under 10 seconds.
Legal
6 min / week
Contract review card creation
Legal manually creates a Wekan card for each contract review request and sets review deadlines from their inbox.
Legal Agent
0 min
Agent creates review cards with deadline
Agent creates the card with contract details, assigns it to the right reviewer, and sets a deadline based on the contract's execution date.

+ 100s of other Wekan automations

Average monthly

10 hrs / person / month

Average monthly

10 hrs / person / month

Calculator

Calculate what your team saves

Team size

10 person

Hourly rate

$20 / hr

Hours saved / week

Hours saved / year

1,250

Annual ROI

$25,000

Based on Wekan's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Wekan into Actionist

Pick the connection method that suits your environment.

The fastest path to your self-hosted Wekan instance. Connect via MCP and the agent reaches your boards, lists, and cards through a secure, permissioned channel — no credentials stored in plain text, no token rotation to manage.

Open the Apps tab

Find Wekan in the Apps library and click Connect. MCP is selected by default.

Enter your Wekan instance URL

Provide the full URL of your self-hosted Wekan server (e.g. https://wekan.yourcompany.com). The agent needs direct network access to this host.

Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

24 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 event your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Wekan

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.

MCP servers

MCP servers that work with Wekan

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.

FAQs

Questions about Wekan + Actionist

How does Actionist connect to my self-hosted Wekan instance?

Actionist connects to Wekan using either MCP (recommended) or Basic Auth with your Wekan username, password, and instance URL. Your Wekan server must be reachable from Actionist's network — if it's behind a firewall, expose the Wekan port via a secure tunnel or VPN. The agent uses Wekan's REST API; no browser access is required.

What credentials does the agent need, and what can it access?

The agent uses the credentials you provide — typically a dedicated Wekan service account username and password. It can access every board, list, card, checklist, and comment that the service account user has permission to view or edit. Create a service account with the minimum board permissions your workflows need; avoid using an admin account unless necessary.

Which Wekan objects can the agent read and write?

The agent can manage the full core object model: boards (create, read, delete), lists (create, read, delete), cards (create, read, update, delete), card comments (create, read, delete), checklists (create, read, delete), and checklist items (create, read, update, delete). It cannot yet manage swimlanes, labels, or user settings directly via the standard -based API surface.

Can the agent react to events in Wekan, like a card moving?

Yes. Actionist supports Wekan event triggers including card created, card updated, card moved to list, comment added to a card, checklist completed, board created, and card due date reached. Set a trigger in your workflow to fire on any of these events so the agent acts the moment something changes on your board — no polling delay.

How do I avoid a trigger loop when my agent updates cards?

Two safeguards work reliably: first, use a condition step that checks whether the card's last modifier is the service account — if so, skip the action to prevent the agent from reacting to its own writes. Second, add a short cooldown check by comparing the card's updatedAt timestamp against the trigger time; if the gap is under 30 seconds and the author is the agent, abort the run. Both checks together eliminate re-trigger loops without missing legitimate human-initiated events.

Does Wekan impose API rate limits I should know about?

Wekan's REST API has no published rate limit — it runs on your own server, so the bottleneck is your server's resources. For high-volume workflows (more than 50 concurrent card operations), add a short delay step between writes to avoid overwhelming a low-spec server. For read-heavy workflows, caching board and list IDs locally avoids redundant GET calls.

Can the agent work across multiple Wekan boards at once?

Yes. The agent can call Get all user boards to enumerate every board your service account can access, then iterate over them. This lets you run cross-board audits, generate portfolio-level reports, or apply bulk updates — for example, reassigning cards across all boards when a team member goes on leave.

What happens if I delete a board or list that the agent references?

The agent will return a 404 error on the next call targeting that board or list ID. Build defensive checks into your workflows: use Get all user boards or Get all board lists before writing to confirm the target still exists. If the target is missing, the agent can alert you in Slack and pause the workflow rather than failing silently.