Single Target Field #
The full text response is placed in the selected Target Field. Choose this for summaries, drafts, notes, classifications, or any task that produces one value.
The destination selector shows only supported fields from the current form. Text, Paragraph, and Hidden require Pro or higher. Every other supported destination requires Premium or higher. The plugin builds the provider contract from the live field configuration, validates the returned semantic value, writes the field’s native storage shape, and reads it back for verification.
JSON Multi-Field Mapping #
Use a mapping when one request should populate several form fields. Each row has:
- Response name: a name you choose for one value the AI must return.
- Destination field: the existing Gravity Forms field that receives that value.
- Output instructions: requirements specific to that generated value.
Example mapping:
| Response name | Destination field | Output instructions |
|---|---|---|
summary |
AI Summary | Summarize the request in no more than 80 words. |
headline |
Suggested Headline | Write a five-to-eight-word title. |
priority |
Suggested Priority | Choose one configured priority value. |
The response names are not Gravity Forms labels or field IDs. They are exact JSON property names included in the structure requested from Anthropic. Choose short, descriptive names such as summary, firstName, or internal_notes. Use each row’s Output instructions for the property’s content rules rather than repeating those rules in the common prompt.
Names are case-sensitive and punctuation-sensitive: firstName and firstname are different. They must be non-empty, unique, no more than 128 bytes, and contain no control characters.
Supported Destinations #
| Minimum plan | Supported destinations |
|---|---|
| Pro | Text, Paragraph, Hidden |
| Premium | Email, Website, non-calculated Number, Date, Time, supported Phone configurations, Select, Radio, Checkbox, Multiselect, Multiple Choice and Image Choice in Radio/Checkbox mode, Name, Address, List, Entry Tags |
Support is configuration-aware. For example, calculated Number fields, choice fields without a recognized effective mode, unsupported Phone configurations, stale List columns, and missing add-on field classes are refused. Each Output Map destination can be selected only once; choosing a field in one row disables it in the other rows.
Configuration requirements #
| Destination | Supported configuration and generated value |
|---|---|
| Text and Hidden | A plain string. |
| Paragraph | A plain string. Rich Text Editor fields accept sanitized HTML or Markdown converted to HTML; ordinary Paragraph fields store plain text. |
| One address that passes the field’s current Gravity Forms validation and rejected-domain rules. | |
| Website | An absolute http:// or https:// URL. |
| Number | A non-calculated field using Decimal Dot, Decimal Comma, or Currency format. Configured minimum and maximum values are enforced. |
| Date | Date Picker, Date Field, or Date Drop Down using a native Gravity Forms date format. The provider returns a real YYYY-MM-DD calendar date and the plugin converts it for the field. |
| Time | Native 12-hour and 24-hour modes. The provider returns structured hour/minute values and AM or PM when required. |
| Phone | US Standard and International (unformatted) are supported. US Standard requires a 10-digit North American number. International (unformatted) accepts the native plain international value. International (formatted) is available only when the installed Gravity Forms version exposes the country/dial-code data required for strict validation; otherwise it is omitted from the selector. |
| Select and Radio | At least one configured choice. The provider must return one current stored choice value. |
| Checkbox | Checkbox behavior with a complete current input for every choice. The provider returns one or more distinct stored choice values. |
| Multiselect | Native CSV or JSON storage with at least one configured choice. The provider returns one or more distinct stored choice values. |
| Multiple Choice and Image Choice | Supported only when their effective mode is Radio or Checkbox and their current choices can be resolved completely. |
| Name | A whole Name field with at least one recognized visible component. The provider returns the visible components, such as first and last, as one object. |
| Address | A whole Address field with recognized visible components. Current state and country choices are enforced when those components are shown. |
| List | A native single-column List or a multi-column List with a valid current column definition. Every generated row must match that shape, and the configured maximum row count is enforced. |
| Entry Tags | The GravityKit Entry Tags field class must be installed and the field must have configured choices. Only current tag values are accepted. |
Fields that represent consent, credentials, payment or pricing state, uploads/media, calculated results, relationships, identifiers, workflow actors/history, or structural controls cannot be AI text destinations.
What The Provider Is Asked To Return #
For a model with native structured-output support, the plugin supplies a schema derived from each active destination. A Number is a JSON number, Checkbox and Multiselect are arrays constrained to current choices, Date is a calendar-date string, and Name, Address, Time, and multi-column List fields use structured objects. Additional properties are rejected. A compatible model without native structured output receives an exact prompt-only JSON contract instead.
Fill-empty mode removes populated destinations—and their Output instructions—from the active schema. If every destination already has a value, generation is skipped before credential or provider resolution.
The plugin validates all returned properties before starting writes, then saves each valid output independently. A valid destination can therefore persist when another value is missing, invalid, or fails to write. The run is reported as partial, with safe field IDs and reasons in its entry note and terminal metadata; generated values are not copied into those diagnostics.
Prompt Example #
System Prompt:
Extract only facts explicitly present in the submission. Keep the summary under 80 words.User Prompt:
Analyze the request below using the configured output instructions.
Request: {Request:5}The active mapping and live destination fields determine the exact provider schema. The common prompt supplies source context; each mapping row explains its own property.
