JSON multi-field mapping is useful when one reading of the submission should produce several related values.
Example: Support Triage #
Prepare three destination fields:
- AI Summary
- Suggested Department
- Suggested Priority
Create these mapping rows:
| Response name | Destination | Output instructions |
|---|---|---|
summary |
AI Summary (Paragraph) | Summarize the request in no more than 80 words. |
department |
Suggested Department (Select) | Choose one configured department value. |
priority |
Suggested Priority (Radio) | Choose one configured priority value. |
Each destination can appear in only one row. Once selected, that field is disabled in every other Destination dropdown; remove or change the first selection to make it available again.
Use a System Prompt such as:
Analyze only the information supplied. Do not invent missing facts.Use a User Prompt such as:
Analyze this support request using the configured output instructions.
Subject: {Subject:3}
Request: {Request:4}Choose Response Names Carefully #
Names should describe their content and remain stable. They are case-sensitive schema properties, not field labels. Changing a response name changes the structure requested from the provider. Update the row’s Output instructions when the new name changes what its content means.
Validate Destination Fields #
Use a Paragraph destination for prose and real Select or Radio destinations for controlled values. The provider schema and adapter validate against current configured choices; stale or invented choices are not persisted. Continue to include human review before consequential automation.
Preserve Existing Work #
Choose Fill only empty targets when staff may already have filled one of the destinations. The active provider request contains only empty fields and only their Output instructions. If every destination is populated, the feed skips generation without provider usage. Administrator reruns are the deliberate exception and always overwrite.
If one returned property is missing or invalid, other valid properties can still be written. The run is marked partial and its entry note identifies the affected destination without copying the generated value into logs or notes.
