Conclusion API
Overview
The Conclusion API: Request and Wait for Conclusion operation creates a conclusion request and automatically polls until completion. The node handles all polling logic internally.
For general API information, see the embraceableAI Conclusion API Documentation.
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| Model | Yes | Dropdown (dynamically loaded) | Available models are automatically loaded based on your API key. Select from the dropdown. |
| Goal | Yes | Multi-line text | The primary objective or intent. Be specific about the desired outcome. |
| Details | Yes | Multi-line text | Context and information about the case. Provide relevant facts, constraints, and domain-specific information. |
| Policies | Yes | Collection or Text | Hard rules and constraints that must be followed. Choose between List Mode (separate list items) or Text Mode (newline-separated text, each line = one policy). |
| Polling Interval | No | Number | How often to poll for status updates (in seconds). Default: 3s, Range: 1-60s. Recommended: 2-5 seconds. |
| Max Wait Time | No | Number | Maximum time to wait for completion (in seconds). Default: 300s (5 minutes), Range: 10-3600s. If exceeded, the node throws a timeout error. |
Output Format
Returns the complete conclusion response:
{
"status": "success",
"model": "model-id",
"output": [
{
"type": "step",
"status": "success",
"content": [{"type": "text", "text": "..."}]
}
]
}
For detailed schema information and complete response structure, see the get-conclusion endpoint documentation.
The complete reasoning process is contained within the response. Review executions in the Sandbox Console under Logs.
n8n-Specific Features
- Automatic Polling: No need to implement polling logic - the node handles it internally
- Blocking Execution: Node blocks until conclusion is complete or times out
- Error Handling: Returns structured error responses for HTTP errors; throws timeout errors if max wait time is exceeded