Work public

crewai-n8n-bridge

Five multi-agent crews as REST API. Research, sales, content, strategy, flow. SSE streaming, webhooks, 54 tests. CrewAI plus FastAPI plus Docker Compose.

  • multi-agent
  • crewai
  • fastapi
  • sse
  • webhooks
  • docker-compose
Repo
github.com/mj-deving/crewai-n8n-bridge
Published
2026-05-26

The problem

Multi-agent frameworks ship as libraries. n8n workflows ship as automation. The bridge between them is usually a hand-written FastAPI wrapper that handles streaming, webhooks, error semantics, and process supervision. Every team writes it again.

This is that bridge, productized.

How it works

Five pre-built crews expose themselves as REST endpoints. The research crew assembles sources. The sales crew drafts outreach. The content crew shapes posts. The strategy crew runs market questions. The flow crew composes the others into ordered pipelines. Streaming runs over Server-Sent Events. Async completion runs over webhooks. The whole stack ships in Docker Compose so n8n can call it as a regular HTTP node.

54 tests cover the crew contracts and the streaming surface. Adding a sixth crew means writing one CrewAI agent definition and one registration line.

Stack

CrewAI for the agent layer. FastAPI for the HTTP layer. SSE for stream-through. Webhooks for async completion. Docker Compose for the deployment unit.