What the documents look like
Fresh-food supplier claims pursue quality responsibility for goods on arrival. They do not handle natural in-store shrinkage. Four document types sit at the centre of this work: the quality exception form, photographic evidence, the deduction notice, and the claim reconciliation statement. These come from inspection systems, WMS receiving, supplier contracts, and finance reconciliation respectively. Two rhythms coexist: per batch and per month.
Order fulfilment and after-sales question answering must establish, for a given batch, what state the quality exception is in and who holds what authorization to push a deduction or a replenishment forward. Inspection conclusions, receiving records, and contract clauses live in separate systems. An HTTP integration can carry field values between them. It cannot substitute for the business determination itself.
Constraints at the HTTP integrations step
The HTTP module sends a request to a configured address. Params carry path parameters, used mostly with GET. Body carries the request body, used mostly with POST and PUT. Headers carry request headers for special information. All three can reference variables through {{}}, drawing on global variables, system variables, and upstream node outputs. The URL can also reference variables.
Return values are not the interface response itself. They describe how to parse that response, extracting values through JSON path syntax or JS object property rules. When the output type is set to string, the value at the corresponding key is converted to a JSON string.
Among the system variables, chatId and responseChatItemId do not exist in test mode. A missing value during debugging is a documented condition, not a fault. The chat completions interface authenticates with an APIKey. Passing body.appId in the request body is recommended. The appId priority order is body.appId, then <apiKey>-<appId>, then the appId associated with the apikey under the older arrangement. The model, temperature, and similar parameters passed in are ineffective; orchestration decides these. Setting detail=true returns intermediate values in responseData, and token consumption must be calculated by the caller. Proxying a team member identity through authProxy requires the team owner to enable it when creating or editing the key, and the proxied identity still needs permission on the target application and conversation. An interactive response returned to an external caller is a display configuration only. User selection or form input requires a further session request to continue the workflow.
Assume a paper exercise sample. A receiving record for a batch of leafy greens states: "12 March 2025, batch A, receiving inspection found the proportion of wilted leaves exceeding the limit agreed in the contract annex; inspection has issued a quality exception form; the deduction amount awaits supplier confirmation." A draft handover note states: "The deduction for this batch has been executed and the supplier has agreed to replenishment." The material shows only that the quality exception form was issued and the deduction amount awaits confirmation. It shows no supplier agreement and no deduction execution record. Both assertions in the draft sentence lack support.
Configuration and implementation checks
| Configuration item | Assumed starting point for this exercise | Basis and comparison method |
|---|---|---|
| Request address and method | Fill in according to the external interface document; the address references the {{BaseUrl}} variable | Compare path and method item by item against the external interface contract |
| Headers authentication | Authorization references Bearer {{token}} | Compare against the key usage specification; credentials do not appear in public samples |
| Body structure | Declare JSON fields according to the external interface contract | Compare field names and types item by item against the external interface document |
| Return value extraction | Configure the key according to the actual response structure | Compare against JSON path syntax and the actual response |
| chatId usage | Pass a non-empty string to use conversation context | Compare against the length under 250 and the uniqueness requirement |
| detail value | Set to true when intermediate values are needed | Compare against the response structure description; tokens are calculated by the caller |
Three common errors
- Treating an issued quality exception form as an executed deduction. The input is the material text "inspection has issued a quality exception form; the deduction amount awaits supplier confirmation." The comparison object is the draft sentence "the deduction for this batch has been executed." The observable result is that the material contains no deduction execution record, so that assertion in the draft sentence lacks support.
- Treating awaiting supplier confirmation as supplier agreement. The input is "the deduction amount awaits supplier confirmation." The comparison object is "the supplier has agreed to replenishment." The observable result is that the material contains no agreement record, so that assertion lacks support.
- Treating an empty chatId under test mode as a business fault. The input is a call made in test mode. The comparison object is the system variable description recording that chatId does not exist in test mode. The observable result is that the empty value is a documented condition, and no conclusion about an external system failure follows from it.
How to verify the setup
- Input the assumed sample material text and the draft sentence. Compare the two assertions in the draft sentence against the states recorded in the material. The result is satisfied when both assertions are marked as lacking support, and the recorded material gaps are the deduction execution record and the supplier agreement record.
- Input a Headers configuration referencing
{{token}}. Compare the actual request header against the key usage specification. The result is satisfied when the authentication credential does not appear in any public sample and the reference relationship matches the specification. - Input a request with detail=true. Compare responseData in the response against the intermediate value structure described in the documentation. The result is satisfied when intermediate value fields are returned according to the documented structure, and the token figure is calculated by the caller rather than taken from a value returned directly by the interface.