SACASE
07Lead Automation
2026CLOSE CASE ×
07 / 07Operations / Automation2026

Lead Automation System

Automation is not complete when a webhook leaves—it is complete when the product knows what happened.

ROLE
Workflow architecture · Backend engineering · Automation
STATUS
Private workflow
STACK
FastAPI · n8n · Webhooks · Docker · Event workflows
SYSTEM ARCHITECTURE / 07SYSTEM LOGIC / PRIVATE BUILD
01 / RECORDCreate the eventSTATE / FORWARD
02 / ROUTERun the workflowSTATE / FORWARD
03 / CALLBACKReport the outcomeSTATE / FORWARD
04 / CLOSEExpose the final stateSTATE / CLOSED
01 / CONTEXT

WHY THIS PRODUCT
NEEDED TO EXIST.

CHALLENGE

External workflows often fail silently. The application emits a webhook, but cannot reliably tell whether a notification was delivered, failed, or disappeared between services.

RESPONSE

I designed the workflow around recorded events and callbacks. FastAPI creates the event before dispatch, n8n routes it, and the callback closes the state as SENT or FAILED with a notification log.

02 / OPERATING LOGIC

THE OPERATING
SEQUENCE.

  1. 01RECORD

    Create the event

    FastAPI persists the automation request and its initial status.

  2. 02ROUTE

    Run the workflow

    n8n interprets the event and sends the required notification path.

  3. 03CALLBACK

    Report the outcome

    The workflow returns delivery success or failure to the product.

  4. 04CLOSE

    Expose the final state

    The event and notification log provide a trustworthy SENT or FAILED result.

03 / PRODUCT DECISIONS

DECISIONS THAT
SHAPED THE BUILD.

01 / STATE

Record before dispatch

The application owns an event record before any external workflow begins.

02 / BOUNDARY

One clear contract

FastAPI and n8n exchange a defined payload rather than sharing hidden product logic.

03 / FAILURE

Silence becomes a state

Failed or missing callbacks remain visible and reviewable instead of vanishing.

04 / EVIDENCE LIMIT

THE SYSTEM.
BEYOND THE INTERFACE.

This case documents architecture, failure handling, and implementation decisions while the product interface and source remain private.

05 / MY RESPONSIBILITY

SCOPE OF
RESPONSIBILITY.

I defined the event contract, FastAPI/n8n boundary, routing logic, callback behavior, delivery states, and observable failure path.

The private workflow proves the event lifecycle and operational feedback loop. It is documented here as system architecture because no public client interface or repository is available.

  • Workflow architecture
  • Callbacks
  • Failure states
  • Observability
NEXT CASE / 01Livestock Platform