Skip to main content

Automation Domain

The Automation domain contains 3 agents specialized in designing and configuring n8n workflow automation, webhook integrations, and scheduling patterns.

Agents

AgentStagePurpose
Workflow Architect2Complete n8n workflow design from requirements
Webhook Engineer3Webhook integrations (GitHub, Slack, custom)
Schedule Optimizer3Cron expressions and schedule patterns

When to Use

Workflow Architect

  • Designing complete n8n workflows
  • Complex multi-node automations
  • Event-driven workflows
  • Data transformation pipelines

Webhook Engineer

  • GitHub/Slack/API webhooks
  • Security configuration
  • Retry logic
  • Payload validation

Schedule Optimizer

  • Cron expressions
  • Timezone handling
  • Business hour scheduling
  • Calendar-aware triggers

Domain Characteristics

Primary Output: n8n Workflow JSON

All automation agents produce schema-validated n8n workflow JSON:
{
  "name": "GitHub Push to Slack",
  "nodes": [
    {
      "id": "webhook_trigger",
      "type": "n8n-nodes-base.webhook",
      "position": [250, 300],
      "parameters": {
        "httpMethod": "POST",
        "path": "github-push"
      }
    },
    {
      "id": "slack_notification",
      "type": "n8n-nodes-base.slack",
      "position": [500, 300],
      "parameters": {
        "channel": "#deployments",
        "text": "New push to {{ $json.repository.full_name }}"
      }
    }
  ],
  "connections": {
    "webhook_trigger": {
      "main": [[{ "node": "slack_notification", "type": "main", "index": 0 }]]
    }
  }
}

Integration with n8n

All workflows integrate with SO1’s self-hosted n8n instance:
  • 400+ integrations available
  • Visual workflow editor for modifications
  • Execution history and monitoring
  • Error handling and retries

Common Use Cases

Use: Workflow Architect + Webhook EngineerScenario: Automate actions on GitHub events (push, PR, issues)Example:
Use the Workflow Architect to create an n8n workflow that:
1. Receives GitHub push webhooks
2. Runs tests via GitHub Actions
3. Notifies Slack on failure
4. Creates JIRA ticket if tests fail repeatedly
Use: Workflow Architect + Schedule OptimizerScenario: Generate and distribute reports on scheduleExample:
Use the Schedule Optimizer to create a cron schedule for:
- Daily sales reports at 9 AM EST
- Weekly team summaries on Friday 4 PM
- Monthly analytics on 1st day of month

Then use Workflow Architect to build the workflow.
Use: Workflow Architect + Webhook EngineerScenario: Connect multiple APIs with data transformationExample:
Use the Webhook Engineer to set up webhooks from Stripe,
then use Workflow Architect to:
1. Transform payment events
2. Update CRM (Salesforce)
3. Send confirmation email
4. Log to analytics

FORGE Stages

StageAgentsActivities
Stage 2 (Implementation)Workflow ArchitectDesign complete workflows, define node connections
Stage 3 (Documentation)Webhook Engineer, Schedule OptimizerConfigure integrations, document patterns

Veritas Integration

Common Prompts Consumed

Prompt IDPurposeUsed By
vrt-a1b2c3d4n8n workflow patternsWorkflow Architect
vrt-e5f6g7h8Error handlingWorkflow Architect
vrt-wh001Webhook patternsWebhook Engineer
vrt-sec001Webhook securityWebhook Engineer
vrt-cron01Cron patternsSchedule Optimizer
vrt-tz01Timezone handlingSchedule Optimizer

Prompts Produced

Automation agents discover and output novel workflow patterns to:
  • veritas/agent-prompts/automation/

Best Practices

1

Start with Workflow Architect

Begin with the Workflow Architect for overall design before diving into specific webhook or schedule configuration.
2

Add Error Handling

Always include error handling nodes in workflows (retry, fallback, notifications).
3

Validate Schemas

Use Zod schemas (via TypeScript Shared agent) to validate webhook payloads.
4

Test Locally

Import generated JSON into local n8n instance for testing before production.