Skip to main content

Automation

1. Definition​

Automation executes a predefined process in response to a trigger, event, schedule, API request, user action, or system condition.

AI is optional.

flowchart TD
    T(["Trigger"]):::actor --> S1["Step 1"]:::process
    S1 --> C{"Condition"}:::gate
    C -->|"Branch A"| A[["API / Script / Job"]]:::process
    C -->|"Branch B"| B["Alternate Step"]:::process
    A --> R(["Result"]):::output
    B --> R

    classDef actor fill:#DBEAFE,stroke:#1D4ED8,stroke-width:1px,color:#0B1220
    classDef process fill:#EEF2F7,stroke:#475569,stroke-width:1px,color:#0B1220
    classDef gate fill:#FEF3C7,stroke:#B45309,stroke-width:1px,color:#0B1220
    classDef output fill:#DCFCE7,stroke:#15803D,stroke-width:1px,color:#0B1220

2. Suitable Automation Work​

  • Scheduled synchronization.
  • Event-triggered notifications.
  • Package/document processing.
  • ETL/data transformation.
  • API orchestration with known sequence.
  • Business approval workflows.
  • Retry/queue handling.
  • Rule-based task creation.
  • File generation and movement.
  • Known deployment sequences.

3. AI Inside Automation​

A workflow remains Automation if it contains model calls but the process is still predefined.

flowchart TD
    D(["Document Uploaded"]):::actor --> E["Extract Text"]:::process
    E --> L["LLM: classify document"]:::model
    L --> C{"Category = X?"}:::gate
    C -->|"Yes"| T(["Create Task"]):::output
    C -->|"No"| N(["Continue alternate configured path"]):::output

    classDef actor fill:#DBEAFE,stroke:#1D4ED8,stroke-width:1px,color:#0B1220
    classDef process fill:#EEF2F7,stroke:#475569,stroke-width:1px,color:#0B1220
    classDef model fill:#EDE9FE,stroke:#6D28D9,stroke-width:1px,color:#0B1220
    classDef gate fill:#FEF3C7,stroke:#B45309,stroke-width:1px,color:#0B1220
    classDef output fill:#DCFCE7,stroke:#15803D,stroke-width:1px,color:#0B1220

The LLM is a step in the workflow; it does not automatically make the workflow an Agent.

4. n8n Role​

n8n is well suited to the Automation role because it is a workflow automation platform with triggers, integrations, code steps, credentials, executions, and AI capabilities.

It can also participate in agentic architectures, but classification should be based on the workflow's behavior, not on the product name.

5. Site Configuration​

capability_type: automation
trigger:
  type: event
  event_type: document.uploaded
workflow:
  runtime: n8n
  workflow_ref: workflow-reference
permissions:
  execute_as: service-identity
controls:
  retry_policy: exponential
  idempotency_key: event-id

6. Agent Invoking Automation​

Agents should reuse deterministic automation rather than reimplement fixed processes through model-driven steps.

flowchart TD
    A[["Agent Decision"]]:::model --> I["Invoke automation: create-approved-work-order"]:::process
    I --> W[["Automation executes known transactional sequence"]]:::process
    W --> R(["Return status to Agent"]):::output

    classDef process fill:#EEF2F7,stroke:#475569,stroke-width:1px,color:#0B1220
    classDef model fill:#EDE9FE,stroke:#6D28D9,stroke-width:1px,color:#0B1220
    classDef output fill:#DCFCE7,stroke:#15803D,stroke-width:1px,color:#0B1220

This improves reliability, auditability, and repeatability.