Zira logo
AI plugins
Docs
Browse Guides
    What Is Zira
    Account Access

    5 guides

    Profile Preferences

    3 guides

    Navigation

    2 guides

    AI Vision

    13 guides

    AI Agents

    1 guide

    AI Assistance

    8 guides

    Data Sources

    12 guides

    Forms

    2 guides

    Dashboards

    18 guides

    Install the Zira App
    Chat

    1 guide

    Feed

    1 guide

    Tasks

    1 guide

    People

    2 guides

    Documents

    1 guide

    Applications

    1 guide

    Support

    1 guide

    Scheduler

    1 guide

    Triggers

    1 guide

    Inventory

    1 guide

    TVs

    1 guide

    Operations App

    2 guides

    TV App

    2 guides

    Channels

    1 guide

3 min read
Updated October 18, 2026

AI Form and Data Source Builder

Turn a rough idea into a working form or custom data source with AI-generated fields, options, validation, and calculated fields.

Use AI Form and Data Source Builder when you want to go from “I know what I need to track” to a working structure in one step.

Instead of building everything field by field, you can describe the workflow, the values people should enter, and any validation or calculations you need. AI builds the structure directly into the editor.

The same builder is used in two places:

  • AI Form Builder for custom forms
  • AI Data Source Builder for custom data sources
Open the builder

You can open the builder in more than one flow:

  1. Open a channel.
  2. Do one of the following:
    • Click the Forms tab, click +, choose Blank Form, then click AI Assist in the form editor
    • Click the Data Sources tab, click Add Data Source, choose Custom, then click AI Assist
  3. You can also click AI Assist while editing an existing form or custom data source.

Form editor showing a configured field and live preview.

What it can build for you

The builder can create:

  • a title and description
  • the main field structure
  • clearer labels and sections
  • dropdown options
  • required fields
  • validation rules
  • calculated fields and expressions

This works best when you describe the real workflow instead of just listing a few field names.

Ask for a form with confidence

Good requests often explain:

  • what the form or data source is used for
  • who will fill it out
  • which values must be captured
  • which values should be calculated
  • what should be required or validated

For example, you can ask for:

  • an inspection checklist
  • a work-order intake form
  • a downtime tracking form
  • a quality record with pass or fail logic
  • a production entry form with totals and calculated fields
Review the structure

Before you apply the result, review:

  • the suggested title
  • the description
  • each field
  • metric matching
  • options for list fields
  • validation details
  • any expression that was suggested

The preview is there to help you confirm the structure before it is added to the editor.

AI Form Builder open with a prompt ready to generate the form draft.

Understand field metrics

Every field stores its values against a metric, which is what dashboards and reports read.

For a form, you do not need to set metrics up one by one. When you save, each field that has no metric yet gets its own new metric, named after the field. Until then the field shows New metric on save. To share an existing metric instead, for example to chart two forms together, pick it in the field's Metric box before you save.

For a physical measurement, say its kind and unit in your request (for example "Pallet Length: Physical measurement, Length, unit Inch"); the builder sets both, so the field saves with its metric.

For a data source, new or existing, you do not need to set metrics up one by one either. When you save, each field that has no metric yet gets the existing metric with the same name and type, or a new metric named after the field if none exists. Until then the field shows Metric on save. Name the field exactly like the metric you want; when both a site metric and a shared (global) metric have that name, the shared one is used, because cameras and other devices post readings to shared metrics. Reusing a metric keeps the key name that integrations post readings to.

Apply the structure and keep improving it

Before applying, choose whether to:

  • replace the current fields
  • or append the new fields to what you already have

After the structure is applied:

  • for a custom data source, review the metric for each field
  • refine field names and labels
  • adjust any options or validation
  • test calculated fields carefully before saving

You can also use the same builder again while editing, so AI can help you:

  • add missing fields
  • simplify the structure
  • revise labels and validation
  • extend an existing form instead of starting over

AI Form Builder showing a downtime report with generated fields and preview.

Read next