Add A Frontend Text Button

Frontend text generation lets a visitor create text before submitting the form. It requires Premium or Agency.

Complete-Result Button #

1. Set the feed Trigger Mode to Frontend button — show result when complete.
2. Choose who may use the button.
3. Add [goaif_button feed_id="123" label="Generate draft"] inside the form.
4. Replace 123 with the feed ID.
5. Preview the form, enter the fields referenced by the prompt, and select the button.

The button waits for the full response, validates it against the live destination adapters, and then fills the configured field or fields.

Streamed-Result Button #

1. Set Trigger Mode to Frontend button — show result while generated.
2. Add [goaif_stream_button feed_id="123" label="Generate draft"].
3. Test through the same CDN, caching, and hosting stack used by the live page.

Plain Text, Paragraph, and Hidden single-target responses can update the status while data arrives. Typed single targets and mapped responses use a structured provider contract, so their raw stream is hidden; the completed result is validated and then applied to the fields.

Allow Either Button #

Choose Either frontend button when the same feed may be used with either shortcode in different layouts. This permits both actions; it does not create two generations from one click.

Design The Form #

Place the button after every prompt input the visitor should complete and before the target field when that makes the workflow easier to understand. Give the destination a clear label such as “Generated draft,” let the visitor edit it if appropriate, and explain that selecting the button uses their current form values and provider API usage.

Frontend-only feeds do not run again automatically on submission. The value already placed in the field is saved as part of the entry. Existing Values does not apply because there is no saved entry to inspect before the button runs.