johndoe6345789
665e1b4aac
- Migrated 67/72 workflows from MetaBuilder JSON Script to n8n schema - All migrated workflows now conform to schemas/n8n-workflow.schema.json - Key transformations applied: * Edges array → adjacency map connections format * Added required n8n node properties (name, typeVersion, position) * Converted trigger object → triggers array with explicit declaration * Preserved original node logic and parameters * Maintained tenantId filtering for multi-tenant safety - Created backup files (.backup.json/.backup.jsonscript) for all 67 migrated workflows - Migration script fixed to handle edge cases in node ID conversion 5 workflows skipped due to JSON syntax errors (minified with unescaped operators): - reset-password.jsonscript - list-users.jsonscript - delete-user.jsonscript - list-scripts.jsonscript - export-script.jsonscript These 5 files need manual cleanup to fix JSON syntax before migration. Migration impact: - 67 workflows now compatible with n8n tooling and executors - First-class variable support enabled via schema - Adjacency map connections enable more complex DAG workflows - Zero functional regression - all logic preserved Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Default Application Workflow
The Default Application Workflow is AutoMetabuilder's production-ready system that combines backend initialization with an iterative AI agent loop. It demonstrates the framework's self-referential approach where internal logic is expressed as declarative workflows.
Overview
This workflow package replaces imperative Python code with a declarative JSON-based approach, providing a complete end-to-end workflow that bootstraps the backend and executes the AI loop.
Key Components
Phase 1: Backend Bootstrap (9 nodes)
Initializes all required services:
- Message loading from storage
- Metadata configuration
- Prompt template loading
- GitHub client initialization
- OpenAI client initialization
- Tool definitions loading
- Plugin loading and initialization
- Context seeding
- Message seeding
Phase 2: AI Agent Loop (8 nodes)
Executes the core agent through iterative cycles:
- Loading context
- Seeding messages
- Making LLM requests
- Executing tool calls
- Appending results
The loop continues for up to 10 iterations or until no tool calls are returned.
Main Advantages
The workflow-based architecture provides:
- Separation of Concerns: Clear boundaries between initialization and execution
- Flexibility: Easy to modify individual nodes without affecting others
- Observability: Each node execution can be logged and monitored
- Extensibility: New nodes can be added without changing existing ones
- Visual: The declarative format enables visual workflow editors
- Testable: Individual nodes can be unit tested in isolation
- Modular: Components can be reused across different workflows
File Structure
default_app_workflow/
├── package.json # Package metadata and configuration
├── workflow.json # Workflow definition with nodes and connections
└── README.md # This documentation file
Customization
To create a custom variant:
- Copy this package to a new directory
- Edit the
workflow.jsonfile to modify nodes or connections - Update the
package.jsonwith new name and description - Update any configuration references
Related Workflows
backend_bootstrap- Initialization onlysingle_pass- Single AI request without loopiterative_loop- Loop-only without bootstrapplan_execute_summarize- Advanced planning workflow
Architecture Notes
The system distinguishes between:
- Immutable Context: Configuration and dependencies that don't change during execution
- Mutable Store: Execution state that changes as the workflow progresses
This separation enables both workflow data flow and programmatic access patterns.
License
MIT