{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "wanmol-goal-flow--serve-workflow-as-chat-api",
 "repo": "wanmol/goal-flow",
 "repo_url": "https://github.com/wanmol/goal-flow",
 "repo_slug": "wanmol-goal-flow",
 "title": "Serve a workflow as a chat API with Redis and MySQL",
 "page_title": "How to serve a workflow as a chat API with Redis and MySQL with Goal Flow",
 "summary": "Run the GoalFlow FastAPI server with persistence so clients can call your workflow.",
 "who": "A backend engineer who needs a streaming chat endpoint for a registered workflow and has Redis and MySQL available.",
 "problem": "A workflow file alone does not give clients an HTTP endpoint, streaming output, or stored conversation history.",
 "outcome": "A local server on port 8000 that accepts POST requests to /v1/chat-messages with a Bearer token and streams SSE responses.",
 "steps": [
  "Run `git clone` on the goalflow repository and `cd goalflow`.",
  "Run `cp .env.example .env` and set real Redis and MySQL values in .env.",
  "Run `pip install -e .`.",
  "Run `goalflow-server` and 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."
 ],
 "agent_prompt": "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.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "1 hour",
 "basis": "readme",
 "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.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "python",
 "requirements": [
  "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"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/wanmol-goal-flow/serve-workflow-as-chat-api/",
 "md": "https://dedupedai.com/use-cases/wanmol-goal-flow/serve-workflow-as-chat-api/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/wanmol-goal-flow--serve-workflow-as-chat-api.json",
 "api_version": "v1"
}