📐 Arquitectura — Caso 14: ▲ Next.js → 🌉 n8n → ⚡ Supabase (Postgres + RLS)#

Emisor Next.js que reenvía a n8n; el receiver persiste en Supabase (Postgres + PostgREST) gobernado por Row Level Security. Reproduce el núcleo BaaS de Supabase sin la suite completa.

🧭 Ficha técnica#

Atributo	Valor
ID	`14`
Origen	Next.js 15 (App Router) — `origin/app/api/emit/route.js`
Puente	n8n — `case-14-nextjs-to-supabase.json`
Destino	Receiver → PostgREST — `dest/index.js`
Persistencia	Postgres 16 + RLS (`web_anon`) vía PostgREST
Puerto (dashboard)	`http://localhost:8094`
Perfil Docker	`case14`

🗺️ Diagrama de arquitectura#

diagrama mermaid

%%{init: {'theme':'base','themeVariables':{'fontSize':'26px','fontFamily':'Segoe UI, Arial, sans-serif'},'flowchart':{'useMaxWidth':true,'htmlLabels':false,'nodeSpacing':55,'rankSpacing':70,'padding':16,'diagramPadding':16}}%%
flowchart TB
    subgraph ORIGIN["ORIGEN - Next.js 15"]
        N["route.js (App Router)"]
    end

    subgraph BRIDGE["PUENTE - n8n + Guardrails"]
        C(["Webhook"]) --> IDEM{"Idempotencia + circuit breaker"}
        IDEM -->|nuevo| FWD["HTTP forward + reintentos"]
        FWD -.->|error| DLQ["Dead Letter Queue (/errors)"]
    end

    subgraph DEST["DESTINO - Supabase (Postgres + RLS)"]
        FWD --> REC["receiver /webhook"]
        REC -->|REST + Prefer upsert| PR["PostgREST"]
        PR -->|SET ROLE web_anon + RLS| DB[("Postgres")]
        DB --> DASH["Dashboard :8094"]
    end

    N -->|POST JSON| C

    classDef origin fill:#000000,stroke:#333,color:#fff
    classDef bridge fill:#EA4B71,stroke:#333,color:#fff
    classDef dest fill:#3ECF8E,stroke:#333,color:#000
    classDef db fill:#336791,stroke:#333,color:#fff
    class N origin
    class C,IDEM,FWD,DLQ bridge
    class REC,PR,DASH dest
    class DB db

🔁 Diagrama de secuencia (ciclo de una publicación)#

diagrama mermaid

%%{init: {'theme':'base','themeVariables':{'fontSize':'24px','fontFamily':'Segoe UI, Arial, sans-serif'},'sequence':{'useMaxWidth':true,'actorFontSize':22,'messageFontSize':20,'noteFontSize':18,'actorMargin':80,'boxMargin':16,'width':170}}}%%
sequenceDiagram
    autonumber
    participant Next as route.js (Next.js)
    participant N8N as n8n
    participant Rec as receiver
    participant PR as PostgREST
    participant DB as Postgres (RLS)

    Next->>N8N: POST /webhook (post vencido)
    N8N->>N8N: Circuit breaker + idempotencia
    N8N->>Rec: HTTP POST /webhook (reintentos x3)
    Rec->>PR: POST /social_posts (Prefer: merge-duplicates)
    PR->>DB: SET ROLE web_anon; INSERT (RLS check)
    DB-->>PR: 201
    PR-->>Rec: 201
    Rec-->>N8N: 200 OK
    Note over PR,DB: GET /logs -> PostgREST GET /social_posts?order=created_at.desc

🧩 Componentes#

▲ Origen — Next.js 15#

origin/app/api/emit/route.js (Route Handler) reenvía los posts a n8n; origin/emit.mjs es el equivalente CLI.

🌉 Puente — n8n#

Guardrails canónicos: fingerprint → circuit breaker → idempotencia → HTTP forward con reintentos → DLQ.

⚡ Destino — Supabase (Postgres + PostgREST + RLS)#

dest/index.js traduce /webhook→POST y /logs→GET contra PostgREST. La tabla tiene RLS habilitada; el rol web_anon (que PostgREST asume) gobierna el acceso vía política.

▶️ Cómo levantarlo#

bash

docker-compose --profile case14 up -d          # Postgres (RLS) + PostgREST + receiver

Dashboard: http://localhost:8094

🔗 Enlaces#

Diagramas en Mermaid — se renderizan nativamente en GitHub. Parte de Social Bot Scheduler.

← Toda la documentación Portada Esta carpeta en GitHub