Integrations
Common issues with Structured Output Parser in Duaer
Common Structured Output Parser issues in Duaer: connecting it, format mismatches, empty responses, and required fields.
Expressions resolve to the first item
Structured Output Parser is a sub-node. Most nodes resolve an expression once per input item; Duaer calls a sub-node with the first item only. Given five names, {{ $json.name }} is always the first name.
To use a different value per item, put the expression in the root node (such as the AI Agent prompt), or run Loop Over Items first so each run gets one item.
Connect it to an AI node
Turn on Require Specific Output Format in AI Agent or Basic LLM Chain. An Output Parser input appears under the node; connect Structured Output Parser there.
Model output doesn't fit required format
The model returned invalid JSON or JSON that does not match the schema. You can:
- Turn on Auto-Fix Format so a mismatch triggers one more model call to fix it.
- Simplify the schema with fewer fields and less nesting.
- Set On Error to Continue in the root node Settings so one bad item does not stop the digital organization.
The AI model returned an empty response to the Structured Output Parser
The model usually ran out of output tokens before writing the structured result. Shorten the prompt, raise the model’s output limit, or simplify the schema.
Every field is required
With Schema Type set to Generate From JSON Example, every field in the example is required. For optional fields, use Define using JSON Schema and list only the mandatory ones under required.
Format AI Agent output
Structured Output Parser shapes the final output only, not intermediate steps. For a fixed format in between, put an example or schema in the AI Agent System Message.
If parsing inside AI Agent keeps failing, let the agent answer freely, then pass the answer to a Basic LLM Chain with the parser attached.
Questions
How do I make a field optional in the Duaer Structured Output Parser?
In the Duaer Structured Output Parser, set Schema Type to Define using JSON Schema and list only mandatory fields under required.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.