HTTP ingress that starts a versioned workflow.
workflow-ingress-service exposes tenant endpoints (publish, disable, retire, revisions, replay). A live example is the Pod Farou contact webhook path into a named workflow with a schema.
- Trigger
- Agent
- Knowledge
- Decision
- Tool
- Approval
- Result
What ingress provides
Automation intake. Endpoints are tenant-scoped and can require a schema before a run starts.
Managed endpoints
Create, test, publish, disable and retire an ingress endpoint from admin. Revisions and rollback are first-class.
Payload schema
Named schemas (for example a contact-v1 body) validate the HTTP payload before orchestration starts.
Events and replay
Each accepted call is an event you can inspect and replay without re-POSTing from the client.
Production shape
Pod Farou uses a dedicated ingress path and workflow key for the public contact form — not a generic unauthenticated dump into RAG.
Ready to move beyond the chatbot?
Build AI that understands your business, follows your processes and can actually get things done.