Skip to main content

​
Overview

AI Forms collect visitor input, insert the submitted values into a prompt, and stream the AI response on the page. Use them for generators, support reply tools, calculators, lead forms, summaries, and other workflows where the visitor provides structured input. In WordPress admin, go to AI Puffer > AI Forms.

Live AI Forms demos

Open example forms built with AI Puffer.

Create a Form

Build fields, layouts, labels, prompt, and AI settings.

Knowledge Base

Use vector data as context for form responses.

Web Search

Let supported providers search the web during a response.

Connected Apps

Send form submissions and outputs to external apps.

Manage Forms

Edit, duplicate, delete, and organize saved forms.

Publish

Embed forms with shortcodes or the WordPress block editor.

Settings

Configure limits, custom CSS, and provider filtering.

Logs

Review form requests and generated responses.

​
Create a Form

  1. Click Create New Form.
  2. Enter the form title.
  3. In the left Layouts accordion, drag a layout into the center designer.
  4. In the left Form Elements accordion, drag fields into the layout columns.
  5. Click a field in the designer to edit it in Element Settings.
  6. In the right-side panel, select Engine and Model.
  7. Write the form prompt in Prompt.
  8. Click Validate Prompt to check field placeholders.
  9. Click Save.
  10. Click Preview to test the form from the admin screen.
AI Forms Editor
You can also click Generate Form and describe the form you want. AI Puffer drafts the title, fields, layout, and prompt. Review the draft before saving.
AI Form generator modal
Set up at least one AI provider before creating a form. If the model list is empty, configure and sync a provider in AI Providers.

​
Form Elements

Form elements collect the values used by the prompt.
AI Form elements panel
FieldUse it for
Text InputShort text values.
Text AreaLonger text values.
DropdownOne selected option from a list.
CheckboxOne or more selected options.
Radio ButtonsOne selected option from a visible list.
File UploadTXT or PDF upload. The extracted text is passed into the prompt.
When you click a field, Element Settings replaces the left palette. Edit Label Text, Field Variable Name, placeholder text, required state, help text, and options.
AI Form field settings
The field variable name is the value you use in the prompt. It can contain letters, numbers, and underscores. It must be unique inside the form.
For File Upload, the visitor uploads a TXT or PDF file. AI Puffer extracts the file text during upload and stores that text as the field value. Add the file field placeholder to the prompt where you want the extracted text to be used. AI Puffer does not summarize the file before the form runs. If you want a summary, ask for it in the prompt.
File Upload sends extracted text in the prompt. It works with the AI Forms text providers: OpenAI, Google, Claude, OpenRouter, Azure, Ollama, and DeepSeek. It does not use Knowledge Base or vector provider settings.
File Upload is available on Pro sites. It accepts .txt and .pdf files. Text-based PDFs work best; scanned PDFs may not provide usable text. Large files still count against the selected model’s context limit.

​
Layouts

Layouts control the frontend rows and columns.
AI Form layouts panel
LayoutColumns
Single Column1 column
2 Columns (50/50)2 equal columns
2 Columns (30/70)Narrow left, wide right
2 Columns (70/30)Wide left, narrow right
3 Columns3 equal columns

​
Multi-Step

Multi-Step shows one layout row at a time. Use it when the form should feel like a guided flow. In the left Multi-Step accordion:
  1. Turn on Enable Multi-Step.
  2. Choose Display Progress.
  3. Hover a row in the designer.
  4. Click the chat bubble icon to configure that row as a step.
  5. Add a step title and description if needed.
  6. Add a condition if the step should appear only for specific answers.
  7. Save the form.
AI Form Multi-Step settings
Progress optionWhat it shows
FullStep title, description, and progress.
CompactStep title and progress.
MinimalStep title only.
NoneNo step header or progress UI.
Skipped step inputs are cleared before submission.

​
Labels

Use the left Labels accordion to change frontend button text and field selector labels.
AI Form labels panel
LabelDefault
GenerateGenerate
StopStop
DownloadDownload
SaveSave
CopyCopy
EngineEngine
ModelModel
BackBack
NextNext
Step TitleStep {number}
Step ProgressStep {current} of {total}
Validation MsgPlease complete this step before continuing.
Multi-step labels are used only when Multi-Step is enabled.

​
AI

Each form has its own Engine and Model in the right-side panel.
AI Form engine and model settings
Click the settings icon beside Model to open Settings, then choose Parameters.
AI Form parameters popover
SettingUse it for
TemperatureResponse variation. Lower values are more predictable.
Max TokensMaximum response size.
Top PSampling control. Leave at the default unless you know why you are changing it.
Frequency PenaltyReduces repeated wording.
Presence PenaltyEncourages the model to introduce new wording or topics.
Reasoning EffortReasoning level for supported models. Keep it set to None for faster responses.
AI Forms use the providers configured in AI Providers. Ollama appears in the Engine list only on Pro sites.

​
Prompt

AI Forms use field placeholders inside the prompt. Add a field value by wrapping its variable name in braces.
AI Form prompt editor
Example: 
Write a customer support reply.

Customer message:
{customer_message}

Tone:
{tone}

Next step:
{next_step}
For dropdown and radio fields, AI Puffer inserts the selected option label. For checkbox fields, it inserts selected option labels separated by commas. If a field is empty, the placeholder is replaced with an empty value. Use the expand icon inside Prompt when you want a larger prompt editor. AI Forms do not keep chat history. Each submission uses the current form values and the saved form configuration.

​
Knowledge Base

Knowledge base lets a form use trained content before generating the response. Click the settings icon beside Model to open Settings, then choose Context.
  1. Turn on Knowledge base.
  2. Select Vector provider.
  3. Choose the vector store, index, or collection.
  4. For Pinecone or Qdrant, select the same Embedding model used when the content was indexed.
  5. Set Limit and Score threshold.
  6. Save the form.
AI Form context settings
Vector providerRequired setup
OpenAISelect up to two Vector stores.
PineconeSelect Index, add the Pinecone API key if needed, and select Embedding.
QdrantAdd URL, API key if needed, select Collection, and select Embedding.
For Pinecone and Qdrant, the must match the model used when the content was added to the index or collection.
Limit controls how many matching chunks AI Puffer can include. Score threshold controls how strict the match must be. A lower threshold allows more matches; a higher threshold only uses stronger matches. Web search lets supported providers use current web results while generating the form response. Click the settings icon beside Model to open Settings, then choose Tools. The available web search options depend on the selected Engine.
  1. Select OpenAI, Google, Claude, or OpenRouter as the form Engine.
  2. Choose Tools.
  3. Turn on Web Search.
  4. Configure the provider options.
  5. Save the form.
AI Form web search settings
OptionUse it for
Search Context SizeHow much web context OpenAI can use.
User LocationOptional approximate country, city, region, and timezone.
Web search is not shown for Azure, DeepSeek, or Ollama forms.

​
Connected Apps

Connected Apps send completed form submissions to external apps through recipes. The form.submitted event is emitted after the AI response is complete, so mappings can use both submitted inputs and the generated response. Supported destinations are Slack, HubSpot, Notion, Pipedrive, Zapier, Make, and n8n.
  1. Go to AI Puffer > Settings > Apps.
  2. Connect the app account or webhook destination.
  3. Create or enable a recipe that uses the AI Form Submitted event.
  4. Choose the scope: All AI Forms, This AI Form, or Selected AI Forms.
  5. Return to AI Puffer > AI Forms.
  6. Edit the form and check the right-side Connected Apps card.
  7. Submit the form on the frontend to test the recipe.
Common mapping sources:
SourceValue
data.form.idForm ID.
data.form.nameForm title.
data.submission.idSubmission ID.
data.submission.countSubmission count for the form.
data.actor.typeguest or user.
data.ai.providerProvider used for the submission.
data.ai.modelModel used for the submission.
data.response.textGenerated AI response.
data.inputsSubmitted field values.
data.inputs.{field_id}A specific submitted field value.

​
Manage Forms

The AI Forms screen lists saved forms with their title, model, shortcode, and actions.
ActionWhat it does
EditOpens the form builder.
PreviewOpens an admin preview.
DuplicateCreates a copy of the form.
ExportDownloads one form as JSON.
DeleteDeletes the form.
Export AllDownloads all forms as JSON.
ImportImports forms from an exported JSON file.
Delete AllDeletes all AI Forms.
Imported forms are added as new forms. Existing forms are not overwritten.

​
Publish

​
Shortcode

Each saved form has a in the form list. 
[aipkit_ai_form id=123]
Replace 123 with the form ID. Click the shortcode settings icon in the form list to enable display options and copy the updated shortcode.
AI Form shortcode settings
OptionShortcode attribute
Show Provider Selectshow_provider="true"
Show Model Selectshow_model="true"
Copy Buttoncopy_button="true"
Save as Postsave_button="true"
Save as PDFpdf_download="true"
Themetheme="light", theme="dark", or theme="custom"
Examples: 
[aipkit_ai_form id=123 theme="dark"]
[aipkit_ai_form id=123 show_provider="true" show_model="true"]
[aipkit_ai_form id=123 save_button="true" copy_button="true"]
[aipkit_ai_form id=123 pdf_download="true"]

​
Block

Use the AI Form block if you prefer the block editor.
  1. Edit the page or post.
  2. Add the AI Form block.
  3. Select the form.
  4. Choose the theme and display options.
  5. Save the page.
AI Form block in the WordPress block editor
The block renders the same form as the shortcode.

​
Result Actions

Result actions appear after the form generates an output.
ActionWhat it does
CopyCopies the generated response.
Save as PostSaves the generated response as a draft WordPress post. The user must be logged in and allowed to edit posts.
Save as PDFDownloads the generated response as a PDF when pdf_download="true" is enabled.
Save as Post uses the form title as the post title and saves the output as draft content.

​
Settings

​
Limits

Limits control how much AI Forms usage is allowed for guests and logged-in users. Go to AI Puffer > AI Forms, click the header Settings button, then choose Limits.
  1. Set Guest quota.
  2. Choose Quota mode for logged-in users.
  3. Set User quota or Role-based quotas.
  4. Choose Reset period.
  5. Edit Quota reached message.
  6. Configure optional primary and secondary buttons.
AI Forms limits settings
ValueMeaning
EmptyUnlimited.
0Disabled.
Positive numberMaximum allowed usage for the reset period.
Reset periods are Never, Daily, Weekly, and Monthly. Action buttons can link users to the usage dashboard, credits dashboard, purchases dashboard, buy credits page, or a custom URL.
For credit-based form access, define pricing rules in Usage. To sell prepaid credits, create WooCommerce credit packages in Usage.

​
Custom CSS

Custom CSS applies to forms embedded with theme="custom". Go to AI Puffer > AI Forms, click the header Settings button, then choose Custom CSS.
AI Forms custom CSS settings
.aipkit-ai-form-wrapper.aipkit-theme-custom {
  /* custom form styles */
}

​
Provider Filtering

Provider filtering controls which models visitors can select when the shortcode or block shows the frontend provider or model selector. Go to AI Puffer > AI Forms, click the header Settings button, choose Provider filtering, then select the models visitors can use. If no models are selected, all configured frontend models are allowed.
AI Forms provider filtering settings

​
Logs

Each form submission creates logs for the submitted request and the AI response. Logs include the form ID, submitted inputs, constructed prompt, provider, model, token usage, vector search scores when knowledge base is used, and the generated response. AI Forms usage is recorded with:
FieldValue
Moduleai_forms
Operationform_submit
Scope typeai_form
Scope IDForm ID
This lets usage rules target all AI Forms or a specific form.

​
Troubleshooting

Check the form ID in the shortcode or block. The form must exist and be published. Admin users see shortcode errors; visitors see empty output.
Configure and sync the provider in AI Providers. If the frontend selector is enabled, also check AI Puffer > AI Forms, header Settings > Provider filtering.
Check the field’s Field Variable Name in Element Settings and make sure the prompt uses the same placeholder, for example {customer_message}.
Make sure the checkbox field has options and that the visitor selects at least one option before submitting.
Use a TXT or text-based PDF file. If the server rejects uploads, check WordPress upload limits and security plugin rules.
The visitor must be logged in and must have permission to create or edit posts.
Enable Save as PDF in the shortcode settings, or add pdf_download="true" to the shortcode.
Check that the recipe is enabled, the app connection is valid, the scope includes this form, and the recipe uses the AI Form Submitted event.