β n8n Successfully Deployed to Fly.io with Flow Nexus MCP Integration
- Dominant language
- TypeScript
- Stars
- 72.7k
- Forks
- 8.6k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 83
Description
## π n8n Deployment Success!
n8n has been successfully deployed to Fly.io with full Flow Nexus MCP integration!
### π Deployment Details
- **URL**: https://n8n-flow-nexus.**
- **App Name**: n8n-flow-nexus
- **Region**: iad (US East)
- **Machine ID**: 3287e55ebe6528
- **Image Size**: 1.2 GB
### β Completed Tasks
1. **Database Schema Fixed**
- Created proper `workflow_executions` table
- Resolved schema reference issues between `public` and `workflow_system`
- Added all required columns
2. **Docker Image Fixed**
- Resolved n8n command not found issue
- Removed custom CMD to use base image entrypoint
- Successfully built and pushed to Fly.io registry
3. **MCP Integration Validated**
- 49 Flow Nexus MCP tools available
- Authentication working with session-based auth
- Workflow creation and execution operational
4. **Workflow Testing**
- Created test workflow ID: `7993052f-afec-4317-937a-48e85aedcd67`
- Successfully executed workflows
- Real-time tracking in database
### π§ Configuration
- **Flow Nexus URL**: https://mcp-flow-nexus.**
-
- **MCP Protocol**: Version 2025-06-18
- **Authentication**: Session-based with
- **n8n MCP Node**: n8n-nodes-mcp@latest
### π Files Created
```
/mcp/flow-nexus-sse/n8n/
βββ Dockerfile # Custom n8n image with MCP
βββ fly.toml # Fly.io deployment config
βββ package.json # Node.js dependencies
βββ mcp-integration.js # MCP integration hooks
βββ run-validation.js # Validation script with auth
βββ test-flow-nexus-api.js # API testing suite
βββ n8n-config.json # n8n configuration
βββ validation-report.json # Test results
βββ validation-report.md # Validation report
βββ workflows/
βββ *.json # Sample workflow definitions
```
### π Related Issue
- Previous validation issue: #754
### π Next Steps
1. Access n8n at https://n8n-flow-nexus.fly.dev/
2. Login with admin credentials (configured in fly.toml)
3. Create workflows using MCP nodes
4. Test bi-directional sync with Flow Nexus
### π― Features Working
- β
n8n deployed and accessible
- β
MCP tools integrated
- β
Flow Nexus authentication
- β
Workflow creation/execution
- β
Database tracking
- β
Persistent storage with Fly volumes
---
**Status**: DEPLOYED & OPERATIONAL π’
Contributor guide
Research direction
The issue documents deployment files under /mcp/flow-nexus-sse/n8n/, including Dockerfile, fly.toml, integration scripts, and validation reports. Start by reviewing those files and related issue #754; no new change or acceptance criteria are specified, while the reported deployment is already operational.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js, typescript
- Domain
- cloud, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100