Who it is forA backend engineer who needs a streaming chat endpoint for a registered workflow and has Redis and MySQL available.
The problemA workflow file alone does not give clients an HTTP endpoint, streaming output, or stored conversation history.
The outcomeA local server on port 8000 that accepts POST requests to /v1/chat-messages with a Bearer token and streams SSE responses.
What you need first
- Python 3.12
- Redis (cluster or standalone) and MySQL
- A cloned copy of the goalflow repository and a filled-in .env file copied from .env.example
- A Dify DSL export (.yml) if you want to transpile a visual flow
Steps
- Run
git cloneon the goalflow repository andcd goalflow. - Run
cp .env.example .envand set real Redis and MySQL values in .env. - Run
pip install -e .. - Run
goalflow-serverand confirm it serves on http://localhost:8000. - Send a test POST to /v1/chat-messages with a Bearer token that auth_validator maps to your registered workflow.
Prompt for your agent
Start the goalflow server in the goalflow repo and send one POST request to /v1/chat-messages for the workflow <workflow-name> using the Bearer token <token>. Expected output is a streamed SSE response. Verify that the conversation is stored in Redis and MySQL.
Caveat. Before you publish any fork publicly, the README warns that real credentials remain in git history and internal service URLs are hard-coded, so read docs/security-and-open-sourcing.md first.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for wanmol/goal-flow and "Serve a workflow as a chat API with Redis and MySQL"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer