Repository navigation
Conversation
This was referenced Sep 4, 2026
Collaborator
|
Thanks for this contribution. We're closing outside-contributor pull requests that have had no activity for 14 days or more, so the queue reflects work that can still land. This isn't a judgment on the change itself. If it's still needed, please rebase onto |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
POST /webhook/ods-chat-completionsworkflowWhy this matters
The dashboard catalog promises a one-minute REST chat endpoint, but enabling the template previously imported only a manual trigger and setup note. This PR turns that reachable catalog action into a usable local API facade with safer limits and predictable responses.
The invariant is: unvalidated fields never reach llama-server, streaming cannot enter a response-node workflow, upstream payloads are not reflected wholesale, and every accepted request has one terminal JSON response.
Overlap check
Searched open and closed upstream PR titles/bodies for
n8n chat API endpoint workflow, reviewed the latest 1,000 open PRs and changed production files, and inspected01-chat-endpoint.jsonhistory. No open or closed PR implements this workflow or changes its production file; upstream history only contains the repository rename. Other runnable n8n PRs operate on distinct catalog entries.The HTTP Request node shape was checked against n8n's official implementation: https://github.com/n8n-io/n8n/blob/master/packages/nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts
Test plan
python -m pytest test_n8n_chat_endpoint_template.py test_workflows.py -q? 48 passeddocker run --rm ... n8nio/n8n:2.6.4 import:workflow --input=/workflows/01-chat-endpoint.json? successfully imported 1 workflow using the exact image ODS shipspython -m json.tool ods/config/n8n/01-chat-endpoint.jsonpython -m compileall -q .../test_n8n_chat_endpoint_template.pygit diff --checkDesign and operational notes
Generated with Codex.
Batch compatibility