Managing Form Schema
Use the AI assistant to add, update, and remove form fields in your lead generation campaigns.
Form schema management in Firebuzz is handled through the AI assistant in the landing page editor. This AI-powered approach makes it easy to configure forms without navigating complex interfaces.
How Form Management Works
When you're editing a landing page in a lead generation campaign, you can talk to the AI assistant to manage your form fields. The AI understands natural language requests and translates them into schema changes.
Form management is only available when you're in the landing page editor for a Lead Generation campaign. The AI assistant handles all form changes automatically.
Available Operations
The AI can perform four types of form operations:
Get Schema
View current form fields and their configurations.
Add Fields
Create new fields with specific types and properties.
Update Field
Modify existing field properties like title or placeholder.
Deprecate Field
Remove fields while preserving historical submission data.
Adding Fields
To add fields to your form, simply describe what you need to the AI assistant:
Example Requests
Basic field:
"Add an email field"
Field with properties:
"Add a required field for company name with placeholder 'Enter your company'"
Selection field:
"Add a dropdown for industry with options: Technology, Healthcare, Finance, Retail, Other"
Multiple fields:
"Add fields for first name, last name, and phone number. Make email and first name required."
What the AI Creates
When you request a new field, the AI automatically:
- Assigns a unique field ID
- Sets appropriate data and input types
- Configures default visibility (visible to users)
- Applies any properties you specified (required, placeholder, etc.)
Be specific about field requirements. Saying "add a required email field with placeholder 'work@company.com'" gives better results than just "add email".
Updating Fields
You can modify existing fields by describing the changes:
Change the title:
"Rename the email field to 'Work Email'"
Update placeholder:
"Change the placeholder for company name to 'ACME Corp'"
Toggle required status:
"Make the phone field optional"
Add description:
"Add helper text to the email field: 'We'll send confirmation here'"
What Can Be Updated
| Property | Can Update? | Notes |
|---|---|---|
| Title | ✓ | Display label can change |
| Placeholder | ✓ | Hint text can change |
| Description | ✓ | Help text can change |
| Required | ✓ | Toggle on/off |
| Default value | ✓ | Pre-filled value |
| Options | ✓ | For select/radio fields |
| Field ID | ✗ | Preserved for data integrity |
| Input type | ✗ | Create new field instead |
Deprecating Fields
When you need to remove a field, the AI "deprecates" it rather than deleting it completely:
Request removal:
"Remove the phone number field"
How Deprecation Works
- The field becomes invisible in new form submissions
- Existing submission data is preserved
- Historical data still appears in the submissions table
- The action cannot be undone through the AI
Deprecating a field hides it permanently. Think carefully before removing fields, especially if you're actively collecting data.
Viewing Current Schema
Ask the AI to show your current form configuration:
"What fields does my form have?"
"Show me the current form schema"
The AI will respond with a summary showing:
- Total number of user-defined fields
- Submit button text
- Field names and types
Best Practices
Planning Your Form
- Start with essentials — Add key fields like email and name first
- Keep it short — More fields = lower conversion rates
- Use appropriate types — Email fields validate format, phone fields show numeric keyboards
- Write clear titles — "Work Email" is better than just "Email"
Managing Changes
- Test before publishing — Use preview mode to test form changes
- Don't remove active fields — Deprecating fields affects data collection
- Be specific with AI — Clear instructions give better results