{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-n8n-io--n8n","slug":"n8n-io--n8n","name":"n8n","type":"workflow","url":"https://n8n.io","page_url":"https://unfragile.ai/n8n-io--n8n","categories":["automation"],"tags":["ai","apis","automation","cli","data-flow","development","integration-framework","integrations","ipaas","low-code","low-code-platform","mcp","mcp-client","mcp-server","n8n","no-code","self-hosted","typescript","workflow","workflow-automation"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-n8n-io--n8n__cap_0","uri":"capability://automation.workflow.visual.workflow.composition.with.node.based.dag.editor","name":"visual workflow composition with node-based dag editor","description":"Provides a canvas-based UI for constructing directed acyclic graphs (DAGs) where users drag-and-drop nodes representing integrations or operations, connect them with edges to define data flow, and configure parameters through a visual parameter editor. The frontend uses Vue.js state management to track workflow structure, node positions, and connections in real-time, with the expression editor enabling dynamic parameter binding using n8n's expression language for data transformation between nodes.","intents":["I want to build a multi-step workflow without writing code","I need to visually map data flow between 5+ services","I want to see the structure of my automation before executing it"],"best_for":["non-technical business users automating repetitive tasks","teams building integration workflows without backend engineering","rapid prototypers who need visual feedback on workflow logic"],"limitations":["Complex conditional logic beyond simple if/then requires custom code nodes","Large workflows (100+ nodes) may experience UI performance degradation","Visual editor abstracts away some advanced execution semantics"],"requires":["Modern browser with ES2020+ support","n8n instance running (cloud or self-hosted)","Basic understanding of data flow concepts"],"input_types":["node configuration objects","workflow JSON schema","parameter expressions"],"output_types":["workflow definition JSON","visual canvas state","executable workflow graph"],"categories":["automation-workflow","user-interface"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_1","uri":"capability://automation.workflow.workflow.execution.engine.with.multi.process.runtime.modes","name":"workflow execution engine with multi-process runtime modes","description":"Executes workflows through a pluggable execution engine (packages/core) that supports multiple runtime modes: single-process for development, worker-based for horizontal scaling, and sandboxed task runners for isolation. The engine manages the workflow lifecycle from parsing the DAG, executing nodes sequentially or in parallel based on dependencies, handling data transformation between node outputs/inputs, and persisting execution state. Uses Bull queue for job distribution in worker mode and supports both synchronous and asynchronous node execution with timeout and retry policies.","intents":["I need to execute workflows reliably at scale across multiple machines","I want to isolate workflow execution to prevent resource contention","I need to retry failed steps with exponential backoff"],"best_for":["teams running production automation at 1000+ executions/day","enterprises requiring multi-tenant isolation and resource quotas","organizations needing audit trails and execution recovery"],"limitations":["Worker mode requires Redis for queue management and adds ~500ms overhead per execution","Sandboxed task runners add latency for each node execution due to process spawning","No built-in distributed transaction semantics — partial workflow failures require custom compensation logic","Maximum workflow execution time configurable but typically capped at 24 hours"],"requires":["Node.js 18+","PostgreSQL or MySQL for execution history storage","Redis 6+ for worker queue mode (optional for single-process)","Docker for sandboxed task runner execution"],"input_types":["workflow definition JSON","execution context with input data","node configuration with parameters"],"output_types":["execution result with node outputs","execution logs and timing metrics","error traces with stack information"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_10","uri":"capability://automation.workflow.execution.monitoring.and.observability.with.logs.metrics.and.error.tracking","name":"execution monitoring and observability with logs, metrics, and error tracking","description":"Provides comprehensive execution monitoring through execution logs (per-node logs with timestamps and data snapshots), execution metrics (duration, memory usage, node execution times), and error tracking with stack traces. The system stores execution history in the database with full audit trails including who triggered the workflow, when, and what data was processed. Integrates with external observability platforms (Datadog, New Relic, Sentry) through telemetry exports. The UI provides execution history views with filtering, search, and drill-down into individual node executions. Supports custom logging through workflow expressions.","intents":["I need to debug why a workflow failed","I want to track execution performance and identify bottlenecks","I need audit logs showing who executed which workflows and when"],"best_for":["teams troubleshooting workflow failures in production","organizations requiring audit trails for compliance","teams optimizing workflow performance"],"limitations":["Execution logs can grow large for high-volume workflows — requires log retention policies","Real-time log streaming not supported — logs are persisted after execution completes","Metrics are basic (duration, memory) — advanced profiling requires external tools","Log search is limited to simple filters — complex queries require database access","Sensitive data in logs requires careful redaction to avoid credential exposure"],"requires":["n8n instance with database backend","Optional: external observability platform (Datadog, Sentry) for advanced monitoring"],"input_types":["workflow execution","node execution data","error information"],"output_types":["execution logs","execution metrics","error traces","audit trail"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_11","uri":"capability://safety.moderation.multi.tenant.project.based.authorization.and.resource.sharing","name":"multi-tenant project-based authorization and resource sharing","description":"Implements a project-based authorization model where workflows, credentials, and other resources are organized into projects with fine-grained access control. Users can be assigned roles (owner, editor, viewer) per project, and workflows can be shared with specific users or teams. The system supports role-based access control (RBAC) with custom role definitions. Credentials are scoped to projects and can be shared across workflows within a project. The authorization layer is enforced at the API level, preventing unauthorized access to resources. Audit logs track all access and modifications.","intents":["I want to share a workflow with a colleague without giving them access to all workflows","I need to restrict who can edit vs view workflows","I want to organize workflows by project and control access per project"],"best_for":["teams with multiple users needing granular access control","enterprises managing workflows across departments","organizations requiring audit trails for compliance"],"limitations":["Project-based model adds complexity for simple single-user deployments","Fine-grained permissions (field-level access) not supported","Sharing workflows requires explicit configuration — no default inheritance","Cross-project workflows not supported — workflows must be in same project","Permission changes take effect immediately — no approval workflow"],"requires":["n8n instance with user management enabled","Database backend for storing authorization rules"],"input_types":["user identity","resource (workflow, credential)","requested action (read, write, delete)"],"output_types":["authorization decision (allow/deny)","filtered resource list","audit log entry"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_12","uri":"capability://automation.workflow.self.hosted.deployment.with.docker.and.environment.based.configuration","name":"self-hosted deployment with docker and environment-based configuration","description":"Supports self-hosted deployment through Docker containers with a docker-compose configuration for easy setup. The system uses environment variables for configuration (database connection, Redis URL, API keys, etc.), enabling different configurations per environment without code changes. Provides CLI commands for database migrations, user management, and workflow import/export. Supports multiple database backends (PostgreSQL, MySQL) and optional Redis for worker mode. The deployment model is stateless for the main instance, enabling horizontal scaling through load balancing.","intents":["I want to run n8n on my own infrastructure","I need to configure n8n for different environments (dev, staging, prod)","I want to deploy n8n using Docker Compose or Kubernetes"],"best_for":["enterprises with strict data residency requirements","organizations wanting full control over infrastructure","teams with existing Docker/Kubernetes deployments"],"limitations":["Self-hosting requires operational expertise (database, Redis, monitoring)","Upgrades require manual steps and testing","No automatic backups — requires external backup solutions","Scaling requires load balancer and database replication setup","Security hardening is the responsibility of the operator"],"requires":["Docker and Docker Compose","PostgreSQL 12+ or MySQL 8+","Redis 6+ (optional, required for worker mode)","Reverse proxy (nginx, Traefik) for HTTPS","Backup solution for database and file storage"],"input_types":["environment variables","docker-compose.yml configuration","database schema"],"output_types":["running n8n instance","database with workflows and execution history","logs and metrics"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_13","uri":"capability://tool.use.integration.rest.api.for.workflow.management.and.execution.control","name":"rest api for workflow management and execution control","description":"Exposes a comprehensive REST API (packages/@n8n/api-types) for programmatic workflow management, including endpoints for creating/updating/deleting workflows, triggering executions, querying execution history, managing credentials, and user administration. The API uses JWT authentication and supports API keys for service-to-service communication. Responses follow a consistent JSON schema with pagination support for list endpoints. The API enables external systems to integrate with n8n, automate workflow deployment, and build custom UIs. OpenAPI/Swagger documentation is available for all endpoints.","intents":["I want to trigger a workflow from my application","I need to programmatically create and deploy workflows","I want to query execution history and metrics from an external system"],"best_for":["developers integrating n8n with external applications","teams automating workflow deployment through CI/CD","organizations building custom UIs on top of n8n"],"limitations":["API rate limiting may throttle high-frequency requests","Webhook-based triggers are more efficient than polling execution status","API responses include full workflow definitions which can be large","Batch operations not supported — requires multiple API calls","API versioning requires careful management for backward compatibility"],"requires":["n8n instance with API enabled","JWT token or API key for authentication","HTTP client library"],"input_types":["workflow definition JSON","execution parameters","query filters"],"output_types":["workflow definition","execution result","execution history","user/credential data"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_2","uri":"capability://tool.use.integration.400.pre.built.node.integrations.with.credential.management","name":"400+ pre-built node integrations with credential management","description":"Provides a node registry (packages/nodes-base) containing 400+ pre-configured integrations with external services (Slack, Salesforce, GitHub, etc.) and utility nodes (HTTP, database, code execution). Each node encapsulates API authentication, request/response transformation, and error handling. The credential system stores encrypted API keys, OAuth tokens, and connection strings in a secure vault, with support for dynamic credential injection at runtime and external secret management (AWS Secrets Manager, HashiCorp Vault). Nodes declare required credentials through a schema-based system, enabling automatic credential selection and validation.","intents":["I want to connect to Salesforce without writing API code","I need to securely store and rotate API keys across multiple environments","I want to use the same credential across multiple workflows"],"best_for":["teams integrating with SaaS platforms (Slack, Stripe, HubSpot, etc.)","enterprises requiring centralized credential management and audit logs","developers building custom nodes that need secure credential handling"],"limitations":["Pre-built nodes may lag behind API updates — custom nodes required for bleeding-edge features","Credential encryption uses instance-level keys — multi-tenant deployments require careful key management","OAuth flows require callback URL configuration and may timeout for long-running workflows","Some integrations have rate-limiting that isn't automatically handled — requires manual backoff configuration"],"requires":["n8n instance with database backend","API credentials for target service","Network access to external service endpoints","Optional: external secret manager (AWS/Vault) for enterprise deployments"],"input_types":["credential configuration (API key, OAuth token, connection string)","node parameters with credential references","workflow execution context"],"output_types":["authenticated API responses","transformed data from external services","credential validation status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_3","uri":"capability://data.processing.analysis.expression.language.for.dynamic.data.transformation.and.parameter.binding","name":"expression language for dynamic data transformation and parameter binding","description":"Implements a custom expression language (packages/@n8n/expression-runtime) that evaluates JavaScript-like expressions at runtime to dynamically compute node parameters, transform data between nodes, and implement conditional logic. Expressions have access to execution context (previous node outputs, workflow variables, environment variables) through a scoped evaluation environment. The expression editor provides syntax highlighting, autocomplete, and real-time validation. Supports both simple variable references ({{ $node.NodeName.data.field }}) and complex transformations ({{ $node.Data.json.items.map(item => item.price * 1.1) }}).","intents":["I need to transform API response data before passing it to the next node","I want to conditionally route data based on field values","I need to access previous node outputs and workflow variables in parameters"],"best_for":["workflow builders needing data transformation without custom code nodes","teams implementing complex conditional logic in visual workflows","developers building dynamic workflows that adapt to runtime data"],"limitations":["Expression evaluation adds ~10-50ms per node depending on complexity","Limited to JavaScript subset — no async/await or external module imports","Expressions are evaluated in isolated context — cannot access Node.js globals or require()","Large array transformations (100k+ items) may cause performance degradation","Debugging expressions is limited to error messages — no step-through debugger"],"requires":["Understanding of JavaScript syntax and array/object operations","Knowledge of n8n's execution context variables ($node, $env, etc.)","n8n instance with expression-runtime package"],"input_types":["expression string","execution context (node outputs, variables)","parameter definitions"],"output_types":["evaluated value (string, number, object, array)","validation errors","type hints for autocomplete"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_4","uri":"capability://planning.reasoning.ai.assisted.workflow.generation.and.chat.based.automation.builder","name":"ai-assisted workflow generation and chat-based automation builder","description":"Provides an AI Workflow Builder (packages/@n8n/nodes-langchain) that uses LLMs to generate workflow definitions from natural language descriptions. Users describe their automation goal in a chat interface, and the system uses Claude or GPT-4 to decompose the task into steps, select appropriate nodes, configure parameters, and generate the workflow JSON. The Chat Hub backend manages conversation history, maintains context about available nodes and integrations, and iteratively refines workflows based on user feedback. Supports multi-turn conversations where users can ask the AI to modify workflows, add error handling, or optimize performance.","intents":["I want to describe my automation goal in plain English and have the AI build the workflow","I need to modify an existing workflow through conversational feedback","I want the AI to suggest optimizations or error handling for my workflow"],"best_for":["non-technical users who struggle with visual workflow building","rapid prototypers wanting to generate workflows in seconds","teams exploring automation possibilities without upfront design"],"limitations":["AI-generated workflows often require manual refinement for production use","LLM context window limits the complexity of workflows that can be generated in a single prompt","AI may hallucinate node names or parameters that don't exist — requires validation","Requires API access to Claude or OpenAI (cost per generation)","Generated workflows may not follow best practices for error handling or performance"],"requires":["OpenAI API key (GPT-4) or Anthropic API key (Claude)","n8n instance with LangChain nodes enabled","Chat Hub backend service running"],"input_types":["natural language workflow description","conversation history","workflow modification requests"],"output_types":["workflow definition JSON","suggested node configurations","explanations of generated steps"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_5","uri":"capability://planning.reasoning.autonomous.ai.agent.execution.with.tool.calling.and.memory","name":"autonomous ai agent execution with tool calling and memory","description":"Implements an Instance AI system (referenced in DeepWiki as 'Instance AI — Autonomous Agent System') that enables workflows to spawn autonomous agents that can make decisions, call tools (n8n nodes), and maintain state across multiple steps. Agents use an LLM as the reasoning engine, with access to a tool registry of available nodes, and can iteratively plan and execute actions based on feedback. The system maintains agent memory (conversation history, execution state) and supports both single-shot and multi-step agent execution. Agents can be triggered by workflow events or user requests and can modify workflow state or trigger other workflows.","intents":["I want to create a workflow that makes autonomous decisions based on data","I need an agent that can iteratively refine results by calling multiple tools","I want to build a chatbot that can execute workflows on behalf of users"],"best_for":["teams building intelligent automation that adapts to runtime conditions","organizations implementing chatbots that execute workflows","enterprises automating complex decision-making processes"],"limitations":["Agent execution is non-deterministic — same input may produce different results","LLM token costs scale with agent iterations — complex tasks may be expensive","Agents may enter infinite loops or make incorrect tool selections without proper guardrails","Memory management requires careful configuration to avoid context window overflow","Debugging agent behavior is difficult due to non-determinism and opaque LLM reasoning"],"requires":["OpenAI API key (GPT-4 recommended) or compatible LLM","n8n instance with LangChain nodes enabled","Tool registry configured with available nodes","Memory backend (Redis or database) for agent state persistence"],"input_types":["agent goal or user request","available tools (node definitions)","execution context and constraints"],"output_types":["agent execution result","tool call history","agent reasoning trace"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_6","uri":"capability://automation.workflow.distributed.workflow.execution.with.worker.scaling.and.job.queuing","name":"distributed workflow execution with worker scaling and job queuing","description":"Implements a distributed execution model using Bull queue (Redis-backed job queue) where the main n8n instance enqueues workflow executions as jobs, and multiple worker processes consume jobs from the queue. Workers are stateless and can be scaled horizontally by adding more instances. The system supports job prioritization, retry policies with exponential backoff, and execution affinity (pinning jobs to specific workers). Execution state is persisted to the database, enabling recovery if workers crash. The main instance monitors job status and provides execution history and logs through the API.","intents":["I need to scale workflow execution across multiple machines","I want to isolate high-load workflows from impacting other executions","I need reliable job execution with automatic retry and recovery"],"best_for":["enterprises running 1000+ workflow executions daily","teams requiring high availability and fault tolerance","organizations with variable load patterns needing elastic scaling"],"limitations":["Requires Redis for queue management — adds operational complexity","Worker startup time adds ~1-2 seconds overhead per execution","Job state is eventually consistent — brief window where job status may be stale","Distributed transactions not supported — partial failures require custom compensation","Monitoring and debugging distributed executions requires centralized logging (ELK, Datadog)"],"requires":["Redis 6+ for job queue","PostgreSQL or MySQL for execution history","Multiple Node.js processes or containers for workers","Network connectivity between main instance and workers"],"input_types":["workflow definition","execution trigger (webhook, schedule, manual)","job priority and retry configuration"],"output_types":["job ID and status","execution result","execution logs and metrics"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_7","uri":"capability://automation.workflow.workflow.scheduling.with.cron.expressions.and.event.based.triggers","name":"workflow scheduling with cron expressions and event-based triggers","description":"Provides multiple trigger mechanisms for workflow execution: cron-based scheduling (using standard cron syntax for recurring executions), webhook triggers (HTTP endpoints that accept POST requests to start workflows), event-based triggers (listening to external events like Slack messages or GitHub pushes), and manual triggers. The scheduler service (part of the CLI runtime) manages cron jobs and ensures they execute at the specified times. Webhooks are registered as HTTP routes and can pass request data into the workflow. Event triggers integrate with external services through polling or event subscriptions. All triggers support conditional execution based on input data.","intents":["I want to run a workflow every day at 9 AM","I need to trigger a workflow when a Slack message is posted","I want to accept HTTP requests and execute a workflow with the request data"],"best_for":["teams automating recurring tasks (daily reports, data syncs)","organizations integrating n8n with external event sources","developers building webhook-based integrations"],"limitations":["Cron scheduling has minute-level granularity — sub-minute scheduling requires custom code","Webhook triggers require public URL exposure — security considerations for self-hosted","Event polling adds latency (typically 30-60 second delay) compared to push-based events","Timezone handling requires explicit configuration — default is UTC","High-frequency triggers (sub-second) may overwhelm the execution queue"],"requires":["n8n instance running with scheduler service enabled","For webhooks: public URL or reverse proxy for self-hosted","For event triggers: API credentials for external service"],"input_types":["cron expression (e.g., '0 9 * * *')","webhook request (JSON body, headers, query params)","event payload from external service"],"output_types":["workflow execution triggered","execution result","trigger metadata (timestamp, source)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_8","uri":"capability://automation.workflow.workflow.versioning.and.source.control.integration","name":"workflow versioning and source control integration","description":"Provides workflow versioning capabilities where each workflow change creates a new version with metadata (timestamp, author, change description). Versions can be compared to see what changed, and workflows can be reverted to previous versions. Integrates with Git for source control, enabling workflows to be stored in Git repositories with automatic sync. The system tracks workflow definitions as JSON files, supports branching and merging workflows, and enables CI/CD integration. Environment-based configuration allows workflows to use different credentials and parameters per environment (dev, staging, prod).","intents":["I want to track changes to my workflows and revert if something breaks","I need to store workflows in Git and deploy them through CI/CD","I want to use different API credentials in dev vs production"],"best_for":["teams managing workflows as code with version control","enterprises requiring audit trails and change tracking","organizations implementing GitOps for workflow deployment"],"limitations":["Workflow JSON can be large and difficult to review in diffs","Merge conflicts in workflow JSON require manual resolution","Environment-based configuration requires careful management to avoid credential leaks","Git sync is one-way (n8n → Git) or requires manual pull","Versioning adds database storage overhead for large workflow histories"],"requires":["n8n instance with database backend","Git repository (GitHub, GitLab, Bitbucket) for source control","Git credentials configured in n8n"],"input_types":["workflow definition JSON","version metadata (author, message)","environment configuration"],"output_types":["versioned workflow definition","version history with diffs","deployed workflow in target environment"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-n8n-io--n8n__cap_9","uri":"capability://code.generation.editing.custom.node.development.with.typescript.sdk.and.community.package.system","name":"custom node development with typescript sdk and community package system","description":"Provides a Node Development Kit (packages/node-dev) that enables developers to create custom nodes using TypeScript. Custom nodes extend a base Node class, define input/output parameters through a schema, implement execute() method for the node logic, and can be packaged as npm modules. The system supports community packages (npm packages with n8n nodes) that can be installed into n8n instances. Node registration is automatic through package.json metadata. Developers can use the n8n CLI to scaffold new nodes, test locally, and publish to npm. The SDK includes utilities for common patterns (HTTP requests, credential handling, error handling).","intents":["I want to create a custom node for an internal API","I need to build a reusable node that can be shared across workflows","I want to publish a community node to npm for others to use"],"best_for":["developers building custom integrations for internal systems","teams creating reusable node libraries for their organization","open-source contributors building community nodes"],"limitations":["Custom nodes require TypeScript knowledge and Node.js development experience","Node development requires local setup and testing — no visual builder","Community nodes must be manually installed — no built-in marketplace","Node versioning and dependency management can be complex","Testing custom nodes requires mocking n8n's execution context"],"requires":["Node.js 18+","TypeScript 4.8+","n8n CLI installed","Understanding of n8n's node schema and execution model"],"input_types":["TypeScript source code","node schema definition","credential configuration"],"output_types":["compiled JavaScript node","npm package","installed node in n8n instance"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":43,"verified":false,"data_access_risk":"high","permissions":["Modern browser with ES2020+ support","n8n instance running (cloud or self-hosted)","Basic understanding of data flow concepts","Node.js 18+","PostgreSQL or MySQL for execution history storage","Redis 6+ for worker queue mode (optional for single-process)","Docker for sandboxed task runner execution","n8n instance with database backend","Optional: external observability platform (Datadog, Sentry) for advanced monitoring","n8n instance with user management enabled"],"failure_modes":["Complex conditional logic beyond simple if/then requires custom code nodes","Large workflows (100+ nodes) may experience UI performance degradation","Visual editor abstracts away some advanced execution semantics","Worker mode requires Redis for queue management and adds ~500ms overhead per execution","Sandboxed task runners add latency for each node execution due to process spawning","No built-in distributed transaction semantics — partial workflow failures require custom compensation logic","Maximum workflow execution time configurable but typically capped at 24 hours","Execution logs can grow large for high-volume workflows — requires log retention policies","Real-time log streaming not supported — logs are persisted after execution completes","Metrics are basic (duration, memory) — advanced profiling requires external tools","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.4964832797200209,"quality":0.5,"ecosystem":0.65,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.2,"quality":0.25,"ecosystem":0.1,"match_graph":0.4,"freshness":0.05}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:22.062Z","last_scraped_at":"2026-05-03T13:56:56.344Z","last_commit":"2026-05-03T12:45:07Z"},"community":{"stars":186543,"forks":57305,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=n8n-io--n8n","compare_url":"https://unfragile.ai/compare?artifact=n8n-io--n8n"}},"signature":"fwnR7ArjeNSX0W3Ts4AKyLrCYpuz4OdO+de9Xdio35PLLgEhwoN0y80rnFa2MMrxq+I7GdKFE0umdNyhDjL4AQ==","signedAt":"2026-06-20T10:50:51.951Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/n8n-io--n8n","artifact":"https://unfragile.ai/n8n-io--n8n","verify":"https://unfragile.ai/api/v1/verify?slug=n8n-io--n8n","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}