Kratos Labs

Showing 25 of 29 from the live probe.

• List Workflows

  Retrieve all workflows from n8n. Optionally filter by active status, tags, or name.

• Get Workflow

  Retrieve detailed information about a specific workflow including nodes, connections, and settings.

• Create Workflow

  Create a new workflow in n8n. The workflow is created in INACTIVE state. REQUIRED FIELDS (per n8n OpenAPI spec): - name: Workflow name (string) - nodes: Array of node objects (at least one trigger node recommended) - connections: Object defining how nodes connect - settings: Workflow settings object (use { "executionOrder": "v1" } at minimum) NODE OBJECT STRUCTURE: { "name": "My Node", // Required: display name "type": "n8n-nodes-base.X", // Required: node type "typeVers

• Update Workflow

  Update an existing workflow. Provide only the fields you want to change. NOTE: - The 'active' field is READ-ONLY. Use activate_workflow/deactivate_workflow tools. - When updating nodes, you must provide the COMPLETE nodes array (not just changes).

• Delete Workflow

  Permanently delete a workflow. This action cannot be undone.

• Activate Workflow

  Activate a workflow so it responds to triggers. The workflow must have a valid trigger node.

• Deactivate Workflow

  Deactivate a workflow so it no longer responds to triggers.

• List Executions

  List workflow executions. Filter by workflow ID or status.

• Get Execution

  Retrieve detailed information about a specific execution.

• Delete Execution

  Delete an execution record.

• Execute Webhook

  Trigger a workflow via its webhook endpoint. REQUIREMENTS: - Workflow must have a Webhook trigger node - Workflow must be ACTIVE - Use the webhook path from the Webhook node configuration The webhook URL format is: {n8n_base_url}/webhook/{path}

• Execute Workflow

  Execute a workflow programmatically and return the execution results. This tool: 1. Triggers the workflow by ID 2. Waits for it to finish (up to 2 minutes) 3. Returns per-node execution results with inputs/outputs REQUIREMENTS: - The workflow must exist - For webhook-triggered workflows, use execute_webhook instead - Works best with workflows that have a Manual Trigger node RETURNS: Full execution data including per-node results (data.resultData.runData).

• Diagnose Execution

  Analyze a workflow execution to identify errors, bottlenecks, and issues. This tool inspects the per-node execution data and returns: - Which nodes succeeded/failed - Error messages and stack traces from failed nodes - Execution time per node (identifies slow nodes) - Data flow summary (what each node received/produced) - Specific fix suggestions based on common error patterns Use this after execute_workflow or on any execution ID from list_executions.

• Self Heal Workflow

  Execute a workflow, diagnose any failures, and return a detailed fix plan. This is the self-healing loop: 1. Execute the workflow 2. Inspect per-node results 3. Identify failures with root cause analysis 4. Generate specific fix instructions (which nodes to change and how) After getting the fix plan, use update_workflow to apply the fixes, then run self_heal_workflow again to verify. This is the recommended workflow development cycle: 1. list_workflow_examples → find a similar pattern 2.

• List Tags

  List all tags for organizing workflows.

• Create Tag

  Create a new tag for organizing workflows.

• List Credentials

  List all credentials (names and types only, not secrets).

• Get Credential Schema

  Get the parameter schema for a credential type.

• List Variables

  List environment variables (Pro/Enterprise feature).

• Run Audit

  Run a security audit on the n8n instance.

• Get Node Types

  List all known n8n node types with their descriptions. This MCP server includes a built-in catalog of common nodes with full parameter schemas. Use this to discover available nodes and understand what they do. Filter by category: - trigger: Nodes that start workflows (Manual, Schedule, Webhook) - core: Essential utility nodes (HTTP Request, Code) - action: Service integrations - data: Data transformation nodes (Set, Filter, Sort, Aggregate) - flow: Flow control nodes (IF, Switch, Merge, Split

• Get Node Schema

  Get the complete parameter schema for a specific node type. Returns: - All parameters with types, descriptions, and defaults - Required credentials - Working examples with real configurations This is essential for creating workflows with correctly configured nodes.

• Search Nodes

  Search for nodes by name or description. Useful when you don't know the exact node type.

• Get Workflow Templates

  List available workflow templates. Templates provide pre-built workflow patterns for common use cases.

• Get Workflow Template

  Get a complete workflow template that can be used with create_workflow. Templates include: - Pre-configured nodes with working parameters - Proper connections between nodes - Realistic examples you can customize