Use this pattern when the visitor does not need to press an AI button and generation should begin from the saved entry.
Recommended Setup #
- Create an AI Text feed and choose After form submission.
- Put reusable behavior rules in System Prompt.
- Put the task and merged form values in User Prompt.
- Choose Single target field or configure a JSON field map.
- Choose Synchronous only when the immediate confirmation or another immediate operation needs the result. Otherwise choose Async.
- Add conditional logic if some entries should not generate.
- Save, submit realistic test entries, and inspect both successful fields and entry notes.
Synchronous Example #
A form confirmation displays a generated short reference explanation. The feed must finish before the confirmation is prepared, so choose Synchronous and keep Max Tokens modest.
Async Example #
An internal summary is used by staff later. Choose Async so the visitor is not held on the submission request. Do not expect the generated value to exist in the immediate confirmation.
Notification Timing #
Create Gravity Forms notifications using the AI text completion or failure events when messages must wait for generation. A notification tied to the normal form-submission event can run before an async result exists.
Test Failure Paths #
Temporarily use conditional logic that does not match and confirm no provider request is made. Test a key failure on a non-production form and confirm the failure event and entry note are useful. Then restore and retest the credential before publishing.
