---
title: Generate Text After Submission
description: "Use this pattern when the visitor does not need to press an AI button and generation should begin from the saved entry. ## Recommended Setup 1. Create an AI Text feed and choose **After form submission**. 2. Put reusable behavior…"
url: "https://brightleafdigital.io/docs/generate-text-after-submission/"
updated: "2026-11-18"
category: GravityOps AI Feed / How To Guides
---

# Generate Text After Submission

Use this pattern when the visitor does not need to press an AI button and generation should begin from the saved entry.

## Recommended Setup

1. Create an AI Text feed and choose **After form submission**.
2. Put reusable behavior rules in System Prompt.
3. Put the task and merged form values in User Prompt.
4. Choose Single target field or configure an Output Map with instructions for each value.
5. Choose **Fill only empty targets** to preserve existing values and avoid asking the provider for them, or **Overwrite configured targets** when regeneration should replace them.
6. Choose Synchronous only when the immediate confirmation or another immediate operation needs the result. Otherwise choose Async.
7. Add conditional logic if some entries should not generate.
8. Save, submit realistic test entries, and inspect successful fields, partial warnings, skipped runs, 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.

## Stuck? Ask in GravityOps Help

Search past answers or post your question, tagged "ai-feed".

- [GravityOps AI Feed: a feed did not run on submission](https://brightleafdigital.io/community/gravityops-help/4147/)GravityOps Help - 0 replies - 2 weeks ago
- [GravityOps AI Feed is live: Claude and OpenAI as Gravity Forms feeds](https://brightleafdigital.io/community/announcements/3931/)Announcements - 0 replies - 4 weeks ago

[Ask in GravityOps Help](https://brightleafdigital.io/community/gravityops-help/?gofrm_tag=ai-feed)[Open a support request](https://brightleafdigital.io/support/)

GravityOps Weekly

[This iframe contains the logic required to handle Ajax powered Gravity Forms.](about:blank)
