A repository of n8n workflow automations built with AI assistance using Claude Code and n8n-mcp.
This project serves as:
- A workflow library - Reusable n8n automation workflows stored as JSON
- An AI-assisted development environment - Using Claude Code with MCP servers to design, build, and deploy workflows
- A version-controlled backup - All workflows tracked in git for history and collaboration
| Workflow | Description | Status |
|---|---|---|
| Notion-Todoist Bidirectional Sync | Syncs tasks between Notion and Todoist with status mapping and deduplication | In Development |
n8n/
├── README.md # This file
├── CLAUDE.md # AI assistant instructions
├── .mcp.json # MCP server config (gitignored)
├── .env # Environment secrets (gitignored)
├── .gitignore # Git ignore rules
└── *.json # Workflow files
- Claude Code CLI installed
- n8n instance (self-hosted or cloud)
- API credentials for services you want to automate
-
Clone the repository
git clone https://github.com/robbybarnes/n8n.git cd n8n -
Configure MCP servers
Create
.mcp.jsonwith your credentials:{ "mcpServers": { "n8n-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "n8n-mcp"], "env": { "N8N_API_URL": "https://your-n8n-instance.com/", "N8N_API_KEY": "your-api-key" } }, "notion": { "type": "stdio", "command": "npx", "args": ["-y", "@notionhq/notion-mcp-server"], "env": { "NOTION_TOKEN": "your-notion-token" } } } } -
Start Claude Code
claude
MCP servers will automatically connect.
- Copy the workflow JSON file content
- In n8n, go to Workflows > Import from File
- Paste or upload the JSON
- Configure credentials for each node
- Test with the Manual Trigger before activating
With n8n-mcp configured, Claude can deploy workflows directly:
Deploy notion-todoist-bidirectional-sync.json to my n8n instance
Ask Claude to help build automations:
Create a workflow that:
- Triggers when a new row is added to Google Sheets
- Sends a Slack notification to #alerts channel
- Logs the event to a database
Claude will:
- Search for relevant templates
- Configure nodes with proper parameters
- Validate the workflow
- Save as JSON and optionally deploy
Each workflow JSON includes embedded documentation via sticky notes. Key information:
- Purpose and use case
- Required credentials
- Configuration steps
- Status/field mappings
- Create workflows using Claude Code in this directory
- Test thoroughly with dry run modes when available
- Document any required setup in sticky notes
- Commit the JSON file with a descriptive message
.mcp.jsonand.envare gitignored - never commit credentials- Workflow JSONs may contain database IDs or project IDs - review before sharing publicly
- Use n8n's credential system rather than hardcoding secrets in workflows