Skip to main content
Version: Divi 5

AI Output Field

Purpose

The AI Output field type displays content generated by Form AI. You set a prompt and trigger (auto, button, or form-submit). Optionally, the AI response can be sent to another form field (e.g. hidden textarea for post content). Persona, temperature, and max words control the response.

When to use

  • Drafting post content, summaries, or suggestions based on other form fields.
  • When Form AI is enabled at the form level and you want a dedicated field for the AI response (or to pipe it into another field).

Key settings

  • Field — Field Type: ai_output, Field Title.
  • AI — AI Prompt, AI API Call Trigger (auto | button | form-submit), AI Output To Field, AI Output Field, AI Output To Field Type, AI Persona, AI Custom Persona, AI Temperature, AI Max Response Word, loading/typing options (preloader, response text, pause, typing speed).
  • Design — AI preload animation colors.

Top features to configure

  • AI prompt — Define exactly what the AI should produce from user input.
  • API call trigger — Choose auto, button, or submit trigger based on the user flow.
  • Output to field — Send generated text into another field when needed for submission/mapping.
  • Persona + custom persona — Control tone and writing style.
  • Temperature + max response word — Balance creativity against consistency and length.

Validation behavior

  • AI output depends on valid Form AI configuration and API connectivity.
  • Trigger mode controls when output is generated and whether users can review it before submit.
  • Output-to-field mappings should use compatible target field types.

Common mistakes

  • Enabling AI Output without completing form-level Form AI setup.
  • Mapping output to a target field with incompatible formatting or limits.
  • Setting very high response length for short-form UX, causing slow or noisy output.

Verify it works

  1. Trigger generation using the configured mode (auto, button, or form-submit).
  2. Confirm output appears in the AI field and any mapped destination field.
  3. Submit a test entry and verify saved AI output in Entries and notifications.
  4. Test a fallback scenario (invalid key or disabled AI) to verify user-facing behavior.

What's Next