WEKAN n8n INTEGRATION: AUTOMATE WEKAN WITH N8N

This action retrieves multiple lists from a specified Wekan board, perfect for workflows that need to analyze board structure or sync list data with external systems.

Key parameters: Board Name or ID (required) to specify the target board, Return All toggle to fetch every list on the board, and Limit (default: 100) to cap how many lists are returned when "Return All" is off.

Use cases: Fetch all lists to generate a board overview report, sync Wekan board structure with a project management dashboard, or check list counts before running card creation workflows.

Retrieve detailed information about a specific list within a Wekan board. Useful when you need to verify a list exists or fetch its metadata before performing other operations.

Key parameters: Board Name or ID (required) and List ID (required) to identify the specific list to retrieve.

Use cases: Validate a list exists before creating cards in it, fetch list details for logging or audit purposes, or build conditional workflows based on list properties.

Remove a list from your Wekan board entirely. Use with caution—this action permanently deletes the list and may affect cards within it depending on your Wekan configuration.

Key parameters: Board Name or ID (required) and List Name or ID (required) to identify the specific list to delete.

Use cases: Clean up temporary or staging lists after project completion, automate board maintenance by removing empty lists, or as part of a workflow that archives completed project phases.

Create a new list on a specified Wekan board. This is your go-to action for dynamically building board structure based on external triggers—like creating a new list for each new client or project phase.

Key parameters: Board Name or ID (required) and Title (required) for the name of your new list.

Use cases: Automatically create phase-specific lists when a new project starts, add client-specific lists when new accounts are onboarded, or build template boards programmatically.

Modify an existing checklist item on a Wekan card. Perfect for marking items as complete, updating their text, or changing their status based on external events.

Key parameters: Full path required including Board Name or ID, List Name or ID, Card Name or ID, Checklist Name or ID, and Checklist Item Name or ID, plus Update Fields to specify what to modify.

Use cases: Mark checklist items complete when related tasks finish in other systems, update item descriptions based on external data changes, or sync checklist status with external task tracking tools.

Retrieve information about a specific checklist item. Useful for conditional workflows where you need to check an item's status before proceeding.

Key parameters: Complete path including Board Name or ID, List Name or ID, Card Name or ID, Checklist ID, and Checklist Item Name or ID (all required).

Use cases: Check if a prerequisite task is marked complete, fetch item details for reporting, or validate checklist item status before triggering dependent actions.

Remove a specific item from a checklist. Handy for cleanup workflows or dynamically managing checklist content based on project changes.

Key parameters: Full path required: Board Name or ID, List Name or ID, Card Name or ID, Checklist Name or ID, and Checklist Item Name or ID.

Use cases: Remove obsolete tasks from checklists automatically, clean up completed items after a certain period, or sync deletions from external task management systems.

Fetch multiple checklists from a specified card, list, or board. Essential for workflows that need to analyze or sync checklist data at scale.

Key parameters: Optional filters include Board Name or ID, List Name or ID, and Card Name or ID. Return All toggle to fetch all matching checklists, or Limit (default: 100) to cap results.

Use cases: Generate reports on checklist completion rates across a board, sync all checklists to an external documentation system, or analyze workload distribution based on checklist items.

Retrieve detailed information about a single checklist, including its items and metadata.

Key parameters: Full path required: Board Name or ID, List Name or ID, Card Name or ID, and Checklist Name or ID.

Use cases: Fetch checklist details for conditional logic in workflows, display checklist information in external dashboards, or verify checklist exists before adding items.

Remove an entire checklist from a Wekan card. This deletes the checklist and all its items permanently.

Key parameters: Path to the checklist required: Board Name or ID, List Name or ID, Card Name or ID, and Checklist Name or ID.

Use cases: Clean up outdated checklists from archived cards, remove template checklists after they've been customized, or implement automated board maintenance workflows.

Add a new checklist to a Wekan card, optionally with initial items. Great for standardizing task breakdowns across similar cards.

Key parameters: Board Name or ID, List Name or ID, Card Name or ID (all required), Title (required), and optional Items to add initial checklist entries.

Use cases: Automatically add standard checklists to new cards based on card type, create onboarding checklists when new team members are added, or build template checklists from external process documentation.

Retrieve multiple comments from Wekan cards, with flexible filtering options. Essential for building notification systems, audit trails, or syncing discussions to external platforms.

Key parameters: Optional filters: Board Name or ID, List Name or ID, Card Name or ID. Return All to fetch all matching comments, or Limit (default: 100) to cap results.

Use cases: Sync card discussions to Slack channels, build activity reports showing comment volume, or archive comments for compliance purposes.

Fetch a specific comment by its ID. Useful when you need to verify a comment exists or retrieve its content for processing.

Key parameters: Board ID, List Name or ID, Card Name or ID, and Comment ID (all required).

Use cases: Verify comment content before forwarding to external systems, fetch comment details for audit logging, or build conditional workflows based on comment content.

Remove a specific comment from a Wekan card. Handle with care—deleted comments cannot be recovered.

Key parameters: Board Name or ID, List Name or ID, Card Name or ID, and Comment Name or ID (all required).

Use cases: Automated moderation workflows removing flagged content, clean up automated notifications that are no longer relevant, or remove duplicate or erroneous comments.

Post a new comment on a Wekan card. Perfect for automated notifications, status updates, or logging workflow activity directly on relevant cards.

Key parameters: Board Name or ID, List Name or ID, Card Name or ID, Author Name or ID, and Comment text (all required).

Use cases: Post automated status updates when external systems change, log workflow execution results on relevant cards, or add notifications when cards are mentioned in other tools.

Modify an existing Wekan card's properties—title, description, due date, labels, members, and more. The workhorse action for keeping cards in sync with external data.

Key parameters: Board Name or ID, List Name or ID, Card Name or ID (all required), plus Update Fields to dynamically add fields to modify.

Use cases: Update card due dates based on external project schedules, sync card descriptions with CRM deal information, or add labels automatically based on card content analysis.

Retrieve multiple cards from your Wekan boards with flexible filtering. The foundation for reporting, syncing, and bulk-processing workflows.

Key parameters: Board Name or ID (recommended), From Object for filtering by association, Return All to fetch all matching cards, or Limit (default: 100) to cap results.

Use cases: Generate daily/weekly card count reports, sync all cards to external project management tools, or build dashboards showing card distribution across lists.

Retrieve detailed information about a specific Wekan card, including all its properties, labels, members, and due dates.

Key parameters: Board Name or ID, List Name or ID, and Card ID (all required).

Use cases: Fetch card details before making update decisions, display card information in external systems, or validate card exists before performing operations.

Remove a card from your Wekan board permanently. Use in cleanup workflows or when archiving completed work.

Key parameters: Board Name or ID, List Name or ID, and Card Name or ID (all required).

Use cases: Automatically delete test or temporary cards, clean up cancelled tasks from active boards, or archive old cards as part of board maintenance.

Create a new card on a Wekan board—the most commonly used action for bringing external data into your Kanban workflow.

Key parameters: Board Name or ID, List Name or ID, and Title (all required). Optional: Swimlane Name or ID, Author Name or ID, and Additional Fields for description, due date, labels, members, etc.

Use cases: Create cards automatically from incoming emails via Gmail integration or form submissions, generate task cards when new CRM deals are created, or build cards from webhook events sent by other systems.

Retrieve multiple boards from your Wekan instance, optionally filtered by user.

Key parameters: Optional User Name or ID to filter boards by owner/member. Return All to fetch all accessible boards, or Limit (default: 100) to cap results.

Use cases: Generate organization-wide board reports, sync board metadata to external documentation, or build board selection interfaces for other workflows.

Fetch detailed information about a specific Wekan board.

Key parameters: Board ID (required).

Use cases: Verify board exists before performing operations, fetch board metadata for reporting, or check board permissions or settings.

Remove an entire board from Wekan. This is a destructive action—all lists, cards, and associated data will be permanently deleted.

Key parameters: Board ID (required).

Use cases: Clean up completed project boards, remove test boards from production instances, or implement automated archival workflows (after backing up data).

Create a new Wekan board programmatically. Perfect for onboarding workflows or templating project structures.

Key parameters: Title (required), optional Owner Name or ID, and Additional Fields to add extra properties as needed.

Use cases: Automatically create project boards when new clients are onboarded, generate team-specific boards from templates, or build boards dynamically based on external project management data from tools like Monday.com.