feat: Add n8n workflow integration for Taskade MCP Server #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds a complete n8n workflow that implements all 25 Taskade API endpoints as HTTP nodes with MCP server trigger functionality. Features: - Webhook-based MCP Server Trigger Node for receiving requests - Switch node for intelligent routing to 25 HTTP endpoints - Complete Taskade API coverage including workspaces, projects, tasks, folders - Comprehensive documentation with usage examples and troubleshooting guide Files added: - n8n-taskade-mcp-workflow.json: Complete n8n workflow with 27 nodes - N8N_WORKFLOW_GUIDE.md: Detailed integration guide and API reference The workflow enables seamless integration between n8n and Taskade's API, allowing automation of workspace management, project creation, task operations, and folder organization through a single webhook endpoint.
|
This commit updates the workflow to use the correct MCP (Model Context Protocol) node types and connection architecture. Changes: - Replace webhook trigger with @n8n/n8n-nodes-langchain.mcpTrigger (v2) - Replace httpRequest nodes with httpRequestTool nodes (v4.3) - Change connection type from 'main' to 'ai_tool' for MCP compatibility - Implement $fromAI() functions for AI-driven parameter extraction - Remove Switch router node (MCP trigger handles routing automatically) Architecture: - MCP Trigger Node -> 21 HTTP Request Tool Nodes (via ai_tool connections) - Each tool uses $fromAI() for dynamic parameter extraction from AI requests - All tools connect directly to MCP trigger (no manual routing needed) This is the correct MCP implementation pattern for n8n v1.0+ with LangChain support, enabling seamless integration with AI clients like Claude Desktop, Cline, and other MCP-compatible applications. Updated documentation to reflect MCP-specific usage and configuration.
This commit enhances all 21 tool nodes with detailed descriptions extracted
from the official Taskade OpenAPI 3.0.3 specification.
Enhancements include:
- Comprehensive tool descriptions with use cases and return values
- Detailed parameter descriptions with REQUIRED/OPTIONAL labels
- Data type specifications and format requirements (UUID, alphanumeric, patterns)
- Regex patterns for validation (dates, times, content patterns)
- Min/max length constraints and character limits
- Enum value listings for restricted fields
- JSON format examples for complex parameters (tasks array, date objects, target objects)
- Cross-references to related tools for workflow guidance
- Nullability information for responses
- Business logic notes (e.g., "REPLACES all existing assignees")
Key improvements:
- All $fromAI() parameter descriptions now include detailed validation rules
- Tool descriptions explain response formats and data structures
- Clear guidance on when to use each tool and how tools relate to each other
- Specific patterns for dates (^\d{4}-\d{2}-\d{2}$) and times (^(?:[0-1][0-9]|[2][0-3]):[0-5][0-9](?::[0-5][0-9])?$)
- Task creation placement options with examples
- Pagination guidance for blocks and tasks endpoints
This enhancement significantly improves AI understanding and reduces errors
when interacting with the Taskade API through the MCP server.
Version: 3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds a complete n8n workflow that implements all 25 Taskade API endpoints as HTTP nodes with MCP server trigger functionality.
Features:
Files added:
The workflow enables seamless integration between n8n and Taskade's API, allowing automation of workspace management, project creation, task operations, and folder organization through a single webhook endpoint.
Note
Introduces an n8n MCP Server workflow exposing 21 Taskade API tools via
@n8n/n8n-nodes-langchain.mcpTrigger, plus a concise setup/usage guide.n8n-taskade-mcp-workflow.json):@n8n/n8n-nodes-langchain.mcpTriggerat path/taskade-mcp-serverwithai_toolconnections.n8n-nodes-base.httpRequestToolnodes covering Taskade endpoints for workspaces, projects, tasks (incl. assignees, dates, notes), and folders.$fromAI()for parameter extraction and Bearer token auth viaAuthorization: Bearer {{api_key}}.projectBlocksGetandprojectTasksGet.N8N_WORKFLOW_GUIDE.md):Written by Cursor Bugbot for commit 2cccaa2. This will update automatically on new commits. Configure here.