Wekan

Wekan

· پراستفاده‌ترین #203

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

بهره‌وریProjectsاسنادDeveloperاتوماسیون

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.

میانگین زمان صرفه‌جویی‌شده
10 ساعت
برای هر نفر · در هر ماه
تقریبا 1 روز کاری برگشتی

کار دستی را حذف می‌کند. 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.

زمان‌بندی

عامل Wekan شما چه چیزهایی را خودکار اجرا می‌کند

یک هفته کارهای زمان‌بندی‌شده که عامل Actionist از طرف شما اجرا می‌کند.

28کارهای زمان‌بندی‌شده
7عامل‌های فعال
24/7همیشه روشن
عامل‌ها
چهارشنبهجمعه
چهارشنبه
پنجشنبه
جمعه
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
گردش‌کارهای چنداپلیکیشنی

Wekan × همه اپلیکیشن‌های دیگر شما

اتوماسیون‌های سرتاسری که چند اپلیکیشن را به هم وصل می‌کنند؛ هرکدام یک خروجی واقعی کسب‌وکار.

6گردش‌کارها
9اپلیکیشن‌های درگیر
حدود 25 ساعتصرفه‌جویی در هفته
6نقش‌های پوشش‌داده‌شده
برای موفقیت مشتری
ویژه4 اپلیکیشن

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 ساعت

زمانی که تیم شما هر هفته و به‌صورت خودکار پس می‌گیرد

جریان کار
تریگر·When a new support email arrives in Gmail
نتیجه
Create a new card with issue details and due datePost ticket summary to #support channelCreate 48-hour follow-up reminder
برد اصلی
صرفه‌جویی در هر اجرا
18 دقیقه
اجرا در هفته
~25×
Zero missed support tickets
اجرا توسطCustomer Support Agent
بازگشت سرمایه

صرفه‌جویی

چیزی که تیم شما پس می‌گیرد: کارهای دستی‌ای که حذف می‌شوند و ارزشی که ایجاد می‌شود.

بدون Actionist

کاری که امروز دستی انجام می‌دهید

با Actionist

کاری که عامل شما برایتان اجرا می‌کند

  • Sales
    18 دقیقه در هفته
    Pipeline card updates

    Sales reps manually create and move Wekan cards for each deal stage, often forgetting to update after calls.

    عامل Sales
    ۰ دقیقه
    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 دقیقه در هفته
    Campaign board setup

    Marketers manually create a new board and populate lists for each campaign launch, taking 15–20 minutes per campaign.

    عامل Marketing
    ۰ دقیقه
    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 دقیقه در هفته
    Email-to-card triage

    Support staff copy-paste inbound emails into Wekan cards, assign them, and post acknowledgement replies manually.

    عامل Customer Support
    ۰ دقیقه
    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 دقیقه در هفته
    Onboarding board prep

    HR coordinators manually create an onboarding card and type out the day-1 checklist for each new hire.

    عامل Human Resources
    ۰ دقیقه
    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 دقیقه در هفته
    Budget request tracking

    Finance manually creates a Wekan card for each budget request received by email, sets SLA dates, and notifies approvers.

    عامل Finance
    ۰ دقیقه
    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 دقیقه در هفته
    Spreadsheet-to-board transcription

    Ops team manually transfers tasks from the planning spreadsheet to Wekan cards, often with a day's delay.

    عامل Operations
    ۰ دقیقه
    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 دقیقه در هفته
    Contract review card creation

    Legal manually creates a Wekan card for each contract review request and sets review deadlines from their inbox.

    عامل Legal
    ۰ دقیقه
    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.

+ صدها اتوماسیون دیگر Wekan
میانگین ماهانه
10 ساعت / نفر / ماه
میانگین ماهانه
10 ساعت / نفر / ماه
محاسبه‌گر

محاسبه کنید تیم شما چه چیزی ذخیره می‌کند

اندازه تیم
10 نفر
نرخ ساعتی
20 دلار / ساعت
ساعت ذخیره‌شده / هفته
25
ساعت ذخیره‌شده / سال
1,250
بازگشت سالانه
$25,000

بر اساس الگوی رایج استفاده تیمی از Wekan: کارهای قابل مشاهده به‌علاوه چند اتوماسیون دیگر که عامل اجرا می‌کند: حدود2.5 ساعت / نفر / هفته کار اداری خودکار می‌شود.

اتصال

چطور Wekan را به Actionist وصل کنید

روش اتصالی را انتخاب کنید که با محیط کاری شما سازگار است.

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.

1
Open the Apps tab

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

2
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.

3
Test the connection

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

اکشن‌ها

24 اکشن که عامل شما می‌تواند اجرا کند

عملیات خواندن و نوشتنی که برای عامل Actionist شما در دسترس است.

تریگرها

7 رویداد که عامل شما می‌تواند به آن واکنش نشان دهد

رویدادهایی که عامل شما زیر نظر می‌گیرد و در پاسخ به آن‌ها اکشن اجرا می‌کند.

مهارت‌ها

مهارت‌هایی که با Wekan خوب کار می‌کنند

مهارت‌های قابل استفاده مجدد عامل که کنار این اپلیکیشن مفید هستند.

هنوز مهارت جفت‌شده‌ای آماده نشده است. این اپلیکیشن را به عامل خود اضافه کنید تا گزینه‌های مناسب را کشف کنید.
سرورهای MCP

سرورهای MCP سازگار با Wekan

Actionist را به سرورهای MCP ساخته‌شده برای این اپلیکیشن یا پیرامون آن وصل کنید.

هنوز سرور MCP برای این اپلیکیشن فهرست نشده است.
پرسش‌ها

پرسش‌ها درباره 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.