Skip to main content

​
Workflow Architect

The Workflow Architect translates business requirements into complete, executable n8n workflow JSON with proper error handling, data transformation, and integration patterns.

​
Quick Reference

PropertyValue
DomainAutomation
FORGE Stage2 (Implementation)
Version1.0.0
Primary Outputn8n workflow JSON (schema-validated)

​
Overview

Use this agent when: You need to design a complete n8n workflow from business requirements, connecting multiple services with data transformation and error handling.
The Workflow Architect is your go-to agent for n8n automation. It:
  1. Analyzes business requirements
  2. Selects appropriate n8n nodes from 400+ integrations
  3. Designs data flow and transformations
  4. Implements error handling and retry logic
  5. Validates output against n8n schema

​
Core Capabilities

Requirements Analysis

Parse business requirements into discrete automation steps

Workflow Composition

Select and arrange n8n nodes to implement logic

Connection Mapping

Define data flow between nodes with proper typing

Error Path Design

Implement comprehensive error handling and retries

​
When to Use

​
✅ Use Workflow Architect for:

  • Complete n8n workflow design
  • Multi-step automation with complex logic
  • Event-driven workflows (webhooks, schedules, triggers)
  • Data transformation pipelines
  • Integration of multiple services (GitHub, Slack, Stripe, etc.)

​
❌ Use specialized agents for:

  • Webhook configuration only → Use Webhook Engineer
  • Schedule optimization only → Use Schedule Optimizer
  • API endpoint creation → Use Hono Backend

​
Usage Examples

Use the Workflow Architect to design an n8n workflow that:
1. Triggers on GitHub push events
2. Filters for main branch only
3. Checks if tests pass via GitHub Actions API
4. Sends success notification to #deployments channel
5. On failure, creates ticket in Linear
Output: Complete n8n workflow JSON with:
  • Webhook Trigger node
  • IF node for branch filtering
  • HTTP Request node for GitHub API
  • Slack node for notifications
  • Linear node for ticket creation
  • Error handling on all HTTP requests

​
Outputs

​
n8n Workflow JSON

{
  "meta": {
    "generatedBy": "workflow-architect",
    "version": "1.0.0",
    "timestamp": "2026-03-10T10:30:00Z",
    "domain": "automation",
    "forgeStage": 2,
    "veritasRefs": ["vrt-a1b2c3d4"],
    "description": "GitHub push notifications to Slack",
    "tags": ["github", "slack", "ci-cd"]
  },
  "name": "GitHub Push to Slack",
  "nodes": [
    {
      "id": "webhook_trigger",
      "name": "GitHub Webhook",
      "type": "n8n-nodes-base.webhook",
      "position": [250, 300],
      "parameters": {
        "httpMethod": "POST",
        "path": "github-push",
        "responseMode": "onReceived",
        "options": {}
      },
      "notes": "Receives GitHub push webhooks"
    },
    {
      "id": "filter_branch",
      "name": "Filter Main Branch",
      "type": "n8n-nodes-base.if",
      "position": [450, 300],
      "parameters": {
        "conditions": {
          "string": [
            {
              "value1": "={{ $json.ref }}",
              "operation": "equals",
              "value2": "refs/heads/main"
            }
          ]
        }
      },
      "notes": "Only process main branch pushes"
    },
    {
      "id": "slack_notify",
      "name": "Notify Slack",
      "type": "n8n-nodes-base.slack",
      "position": [650, 250],
      "parameters": {
        "channel": "#deployments",
        "text": "🚀 New push to {{ $json.repository.full_name }} by {{ $json.pusher.name }}",
        "attachments": []
      },
      "notes": "Send notification to Slack"
    }
  ],
  "connections": {
    "webhook_trigger": {
      "main": [[{ "node": "filter_branch", "type": "main", "index": 0 }]]
    },
    "filter_branch": {
      "main": [[{ "node": "slack_notify", "type": "main", "index": 0 }]]
    }
  },
  "settings": {
    "executionOrder": "v1",
    "saveManualExecutions": true,
    "timezone": "UTC"
  }
}

​
FORGE Gate Compliance

​
Entry Gate

Before workflow design begins:
  • Business requirement or user story provided
  • Target systems/APIs for integration identified
  • Expected inputs and outputs defined
  • Success criteria established

​
Exit Gate

Workflow design completes when:
  • n8n workflow JSON validated against schema
  • All nodes have documented purposes in notes field
  • Error handling nodes present for each integration point
  • Workflow metadata includes Veritas prompt references
  • Decision record logged with design rationale

​
Best Practices

Every external integration (HTTP Request, API call, database query) should have:
  • Error trigger node to catch failures
  • Retry logic with exponential backoff
  • Notification on persistent failures
Instead of “HTTP Request”, use “Fetch User from Salesforce” Instead of “IF”, use “Check if Order Complete”
Use the notes field to explain:
  • What the node does
  • Why specific parameters were chosen
  • Any gotchas or edge cases
Include sample input data in your request for realistic workflow testing.

​
Integration Points

​
Control Plane API

EndpointPurpose
POST /api/v1/workflowsRegister new workflow
GET /api/v1/integrationsQuery available n8n nodes

​
Veritas Integration

Consumes:
  • vrt-a1b2c3d4: Workflow design patterns
  • vrt-e5f6g7h8: n8n node selection guidance
Produces:
  • Workflow task prompts for novel patterns
AgentRelationship
Webhook EngineerConfigures webhook security and validation
Schedule OptimizerOptimizes cron triggers
Hono BackendCreates API endpoints to receive webhooks

​
Source Files

Agent Definition

View full agent markdown

n8n Schema

Workflow output schema