Text feeds are created under Form Settings -> AI Text and use Anthropic.
Model lifecycle #
Claude Sonnet 5 is the recommended default. Older Claude models that Anthropic still lists as active may remain selectable with the plugin’s Superseded label and a recommendation to compare their newer replacement’s behavior, capabilities, and pricing. Legacy is reserved for an official provider status; the plugin does not currently apply it to any selectable Claude model.
Deprecated models are retained only for feeds that already use them. A retired model blocks every execution path until an administrator saves a supported replacement.
Max Tokens #
The maximum number of output tokens the provider may return. Tokens are pieces of text rather than words; one word can use one or several tokens. A larger value allows a longer answer and can cost more. It does not reserve or guarantee that much output.
Enter a positive whole number. A blank value uses 1,024. For listed models, the plugin rejects a value above the known model output limit. For a custom model, consult the provider because the plugin does not know its ceiling.
Choose a limit suited to the task. A category label may need tens of tokens, a short summary a few hundred, and a long draft considerably more.
System Prompt #
Optional standing instructions describing how the AI should behave: role, tone, rules, boundaries, audience, and output style. Merge tags are supported, although stable instructions usually belong here and entry-specific content usually belongs in User Prompt.
Example: You are an internal support assistant. Be concise, do not invent facts, and do not include personal contact information in the summary.
User Prompt #
The required task and content for this request. Use the merge-tag button to insert form values.
Example: Summarize this request in three bullets for the support team: {Request details:5}
Anything inserted through a merge tag is sent to Anthropic. Do not insert {all_fields} without understanding how much and what kind of entry data it includes.
Output Mode #
- Single target field saves the complete response to one selected Gravity Forms field.
- JSON multi-field mapping asks the model for named values and saves each into a selected destination field.
Target Field #
Shown for single-field output. Choose the field that receives the generated text. The field must already exist on the same form. A Paragraph, Text, or Hidden field is usually the best choice. Avoid a field whose validation or type cannot accept generated text.
Regular Paragraph Text fields receive plain text. If Use the Rich Text Editor is enabled on a Paragraph Text or Post Body field, supported Markdown is converted to sanitized HTML for the editor.
JSON Field Map #
Shown for multi-field output. Add one row per generated value. Response name is the exact JSON property requested from the model; Destination field is the Gravity Forms field that receives that value. See the dedicated output mapping reference for examples and rules.
Execution Mode #
Shown only for after-submission feeds.
- Synchronous waits for generation during submission processing. Use it when the generated value must be available to an immediate confirmation or another immediate operation.
- Async queues generation after submission. Use it for slower requests when the visitor does not need the result in the immediate confirmation.
Notification Options #
Premium/Agency settings can opt completion/failure events into administrator reruns and Gravity Flow runs. Normal post-submission feeds already emit their feed event. See the notifications and reruns reference.
