n8n

Manage n8n workflows via direct SQL queries to the PostgreSQL datastore.

8|1|Updated Aug 5, 2025
One-click install
npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill n8n-artymclabin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n
Source: https://github.com/ArtyMcLabin/ClaudeCode-global-config/tree/main/skills/n8n
Command: npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill n8n-artymclabin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

n8n tasks often rely on the browser/UI, which can be brittle and slow. This skill enables direct SQL access to the n8n PostgreSQL datastore, providing faster, more reliable workflow management.

Core Features & Use Cases

  • Direct SQL access to manage n8n workflows without UI automation.
  • Modify workflows, update nodes or connections programmatically, and debug issues.
  • Check recent executions and verify workflow health; restart n8n when needed.

Quick Start

Connect to your n8n PostgreSQL database and run example SQL commands to list active workflows, update nodes, or review executions. Examples: docker exec <postgres-container> psql -U n8n -d n8n -c "SELECT id, name, active FROM workflow_entity WHERE active = true ORDER BY "updatedAt" DESC;" docker exec <postgres-container> psql -U n8n -d n8n -c "UPDATE workflow_entity SET nodes = '<JSON>' WHERE id = '<workflow-id>';" docker exec <postgres-container> psql -U n8n -d n8n -c "SELECT "startedAt", "stoppedAt", status FROM execution_entity WHERE "workflowId" = '<workflow-id>' ORDER BY "startedAt" DESC LIMIT 5;"

Frequently Asked Questions about n8n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modify n8n workflows directly in PostgreSQL without using the UI?

You can modify n8n workflows by running SQL UPDATE commands on the workflow_entity table in the PostgreSQL database, allowing you to programmatically update nodes and connections without relying on the browser UI.

Why does direct SQL access solve brittle n8n workflow management?

Direct SQL access solves brittle n8n workflow management by bypassing the slow and unreliable browser UI, enabling faster and more reliable modification of workflow nodes, connections, and execution records directly in the PostgreSQL datastore.

Can I check recent n8n execution history using SQL queries?

Yes, you can check recent n8n execution history by querying the execution_entity table in PostgreSQL, selecting the startedAt, stoppedAt, and status columns filtered by the specific workflowId to verify workflow health.

What is the best way to debug n8n workflow issues when the chrome-agent is unreliable?

The best way to debug n8n workflow issues when the chrome-agent is unreliable is to query the PostgreSQL database directly using SQL to inspect the execution_entity and workflow_entity tables for recent statuses and node configurations.

Do I need direct PostgreSQL database access to manage n8n workflows with SQL?

Yes, you need direct access to the n8n PostgreSQL database, typically via a command like docker exec, to connect and run SQL queries against the workflow_entity and execution_entity tables for workflow management.

What are the limitations of using SQL to update n8n workflow nodes?

Using SQL to update n8n workflow nodes requires manual construction of valid JSON for the nodes column and may require restarting n8n for changes to take effect, posing a risk of corrupting workflow structures if the JSON is malformed.