Experience · Worker · Active

funnel worker

Dedicated worker process for asynchronous FunnerAI jobs, started from the backend workspace and backed by BullMQ queues on Redis.

• Nest ApplicationContext
• BullMQ
• Redis
• Node.js

Spec sheet

Repository path

funnel-ia-engine/backend

Runtime

Node process bootstrapping Nest ApplicationContext

Known queues

MESSAGE_QUEUE, CONTACT_ENRICHMENT_QUEUE, FUNNEL_STAGE_EVALUATION_QUEUE

External providers

SMTP plus Core AI/agent services through backend orchestration

Responsibilities

• Consume asynchronous jobs emitted by the backend.
• Handle messaging dispatch, contact enrichment and stage evaluation work.
• Reuse the same backend module graph without exposing public HTTP endpoints.

Interfaces and contract surface

• start:worker
• start:worker:dev

Consumers

• funnel backend

Dependencies and external touchpoints

• funnel backend
• Redis
• PostgreSQL
• SMTP provider
• platform-agent-service

Notes

• The worker is operationally separate even if it shares the backend codebase.

Source references

• docs/architecture-current.md
• funnel-ia-engine/backend/package.json