Evaluation → Evaluate
AI-generatedSummary
Sends input to EchoStack's POST /v1/evaluate endpoint to evaluate it against a deployment playbook, and returns the API response (e.g. status and next_action) for each incoming item so downstream nodes can branch on it.
Inputs
- Evaluation ID — Evaluation UUID (from POST /v1/evaluations). Overrides the credential's Evaluation ID. One of the two must be set, otherwise the node errors. In Raw JSON mode, an evaluation_id already in the body takes precedence.
- Input Mode (required) — Form Fields (default), Transcript, or Raw JSON. Selects how the request body is built.
- Form Fields — Shown in Form Fields mode. A JSON object, which defaults to the incoming item's JSON. Empty/null values are dropped. The rest are flattened into a 'Form submission:' text message of '- key: value' lines and sent as input_type 'form'. Arrays are rejected, and nested values are stringified.
- Transcript JSON — Shown in Transcript mode. A non-empty JSON array of {role, content} turns. Role must be user, agent, or assistant, and content must be a string. Sent as input_type 'transcript'.
- Evaluate JSON — Shown in Raw JSON mode. A full request body that must have input_type and a non-empty input array. It is sent as-is, with the options and evaluation_id merged in.
- Request Next Action — Defaults to true. Sent as options.request_next_action, asking for next_instruction and suggestions in the response.
- Include Reasoning — Defaults to true. Sent as options.include_reasoning, asking for the LLM reasoning in the response.
Output shape
One output item per input item, whose json is the EchoStack API response body (documented fields include status and next_action; next_instruction, suggestions and reasoning depend on the options). Each item is paired with its input item.
Requires an echoStackApi credential with a Base URL and an org API key starting with 'esk_'. HTTP status 400 or higher raises an error, and the message includes the quota reset time and upgrade URL when the API supplies them. With Continue On Fail enabled, failed items return {error: message} instead. Each item makes its own request.
Examples
Example 1: Qualify a form submission from a trigger (e.g. a CRM form) and route on the result.
Input Mode: Form Fields with the default {{ $json }}. Keep Request Next Action on. Follow with an IF or Switch node on status / next_action.
Example 2: Evaluate a chat conversation transcript.
Input Mode: Transcript. Transcript JSON: an expression that produces [{"role":"user","content":"..."},{"role":"agent","content":"..."}]. Include Reasoning off to keep the output smaller.
Example 3: Send a custom request body with its own evaluation ID.
Input Mode: Raw JSON. Evaluate JSON: {"input_type":"transcript","input":[...],"evaluation_id":"