SoftTech AI Registry
Zoho · Zoho Creator

Build Agent application modification

Zoho Creator Build Agent interprets a user's natural-language request, determines changes to supported components of an existing Creator application, presents them as a Change Summary for review, and applies the approved changes to the application. Create and modify only; no deletion; application records are not created, modified or deleted.

Recorded characteristics

Function
Build Agent (Zoho also uses "Zia Build Agent" in places) is "an AI-powered development assistant in Zoho Creator that lets you modify existing applications using natural language prompts". Sequence: user describes changes (optionally @mentioning components and attaching files) → Build Agent interprets the request, identifies affected components, asks follow-up questions where needed, and determines proposed changes, which "may recommend related updates, such as adding supporting fields, generating reports, or updating other application components" → Change Summary with an Actions section grouped by component → user clicks Apply Changes or Cancel → "Build agent updates the relevant application components accordingly"; "approved changes take effect immediately". Unsupported or off-topic requests are rejected, "prevent[ing] any partial implementation of changes". Zoho does not describe it as autonomous. The persistent object is the Creator application's structure, configuration and code — consistent with existing Registry precedent for persistent modification of code, files, spreadsheets and security configuration. Edit and Live modes: available in both; in Live mode it "lets you make changes to your application in live mode" without switching back to Edit mode. For published applications Zoho recommends a development environment, which Build Agent can create automatically (recommended, not stated as mandatory). SUPPORTED CHANGES (create and modify only; deletion not supported for any component): Forms — create and modify forms, add fields, modify supported properties; not supported: form/field deletion, change field type, enable/disable encrypt data, lookup from another application, record-owner (role hierarchy), email notification on submission, field alignment, hide/show buttons, disable location/IP capture, phone customization. Reports — create and modify list, spreadsheet, kanban, calendar, timeline and map reports; not supported: pivot chart/table, live-mode custom sorting/grouping, templates, quick-view layout changes, custom layouts, phone customization, deletion. Pages — add pages and panel, chart, board, gauge, search, form, report, HTML snippet and embed snippet elements; page variables and scripts, background colour, PDF/print; not supported: widgets, AR viewer, ZML snippet generation, panel configuration updates, phone customization, rearranging existing layout, page/element deletion. Workflows — create and modify "On a form event" and "On a function call" workflows and generate their Deluge scripts; approved generated scripts/configuration are inserted when changes are applied (example: calculateWarrantyExpiry() function plus form rule); not supported: Blueprint, approval, payment, batch and schedule workflows, Node.js and Java functions, deletion. Chat agents — create and modify; not supported: changing name, link name or avatar, associating/removing AI agents, deletion (application-development operation, separate from Chat Agent data actions). Application settings — app menu, icon, rename, user permissions, portal user permissions, localization, time format, theme and colour; NOT supported: roles, data sharing, deleting user permissions, deleting portal user permissions, app variables, contextual messages, record templates, schema builder, export via IDE. Build Agent does not currently support modifying roles or data sharing.
Data access
APPLICATION DATA LIMITATION: "Create, modify, and delete operations on application records is not supported"; "Records stored in forms are not affected." Build Agent "operates only within the application from which it is accessed and cannot directly access other Creator applications or external systems." Inputs: prompt, @-mentioned components, uploaded files (images, PDFs, CSV, text; up to 10 files, 10 MB each, PDFs 2 MB).
Actions
Can take actions
External actions
Unknown
Human confirmation
Required
Permission basis
Not established
Administrative control
Human confirmation required: Build Agent prepares proposed changes → Change Summary → Actions grouped by component → user chooses Apply Changes or Cancel → only approved changes are implemented. Submitting a new prompt without applying discards the pending changes. The initial prompt is not treated as approval; Apply Changes is the persistence boundary. Eligibility: "Accessible to Super Admins, Admins, and Developers for modifying applications." Eligibility is not execution authority: whether modifications are constrained to exactly the configuration permissions the invoking user could exercise manually is not established (permission basis not_established). Established controls: only eligible roles can access it; it works within the current application; roles and data sharing are unsupported modification types. Privilege escalation, bypass of Creator permissions, or broader-than-user authority are not established and not inferred. Enablement: Operations → Zia → Features → Access toggle for Build Agent, choosing a configured LLM provider. ENABLEMENT CONFLICT: the Availability box says "Can be enabled by a Super Admin or Admin"; the same page's note and the Zia features page say only a super admin can enable/disable it. The relationship between these current Zoho descriptions is not publicly established. Reversibility: "Changes applied through the build agent cannot be reverted." Development environment guidance is a safeguard, not rollback; whether Creator backup/restore can reverse changes is not established. Logging: per-application conversation History — "Select any conversation to resume it or review the changes made." Not established: Creator Audit Trail recording Build Agent changes, independent audit of applied changes, code diffs, runtime identity logging.
Default state
Conditional
Availability
Lifecycle active: "Available for all paid plans of Creator 6"; no beta or early-access label established (a Related-topics link to the Early Access page does not make it early access). Default conditional: Creator 6 paid plan, Zia configured (Zoho GenAI by default), Build Agent feature enabled, supported AI provider configured, eligible role (Super Admin, Admin, Developer), existing Creator application. Not inherited from #141.
Licensing
Build Agent does not consume Creator AI or API calls; Zoho GenAI usage consumes Development AI Credits (viewable in Billing); external provider usage is billed by that provider and subject to its rate limits.
External model or provider
Uses the LLM provider configured in Zia for the feature: Zoho GenAI (default, processes prompts within Zoho), OpenAI or Anthropic. "Build agent cannot be configured to use Google Gemini as the LLM provider in Zia" — Gemini is not a supported Build Agent provider. Documentation tension: the page's rate-limit section nonetheless links "Google Gemini rate limits"; Gemini support is not inferred. No specific model established. Zoho GenAI is unavailable in CN, UAE and SA data centres; external providers unavailable in CN. System-generated supplementary prompts count toward provider usage. Not inherited from #141's OpenAI-only AI Agent restriction.
Limitations and uncertainty
EXTERNAL ACTION unknown — both statements preserved: Build Agent "cannot directly access other Creator applications or external systems"; and "If integrations are already configured and authorized in the current application, Build agent can use them to perform the requested operations." Distinguish (A) modifying integration-related configuration inside Creator, (B) using an existing authorised integration, (C) causing a persistent effect in an external system; only C would establish external action, and C is not sufficiently established. External action is not stated to be unsupported. APP BUILDER boundary: Zia App Builder creates new applications and is excluded; Build Agent modifies existing applications. BACKGROUND CONFIGURATION CONFLICT: one Zia App Builder passage says backend configuration continues in the background and Build Agent, if enabled, only displays progress ("If Build Agent is not enabled, the application is still created and the backend configuration continues in the background, but its progress is not displayed"); another says "Build Agent then completes the remaining backend configuration, including roles, permissions, blueprints, and workflows". The relationship between these current Zoho descriptions is not publicly established; background configuration is not credited to Build Agent. Zoho advises splitting complex requests to prevent incomplete execution. Unresolved: (1) whether applied changes are constrained by the invoking user's exact manual permissions; (2) meaning of the integrations statement; (3) who may enable Build Agent; (4) whether Build Agent performs background App Builder setup or only displays progress; (5) Audit Trail treatment; (6) relationship between conversation History and applied changes; (7) no fully demonstrated run beyond Zoho videos/examples; (8) Gemini rate-limit link despite no Gemini support; (9) exact underlying model; (10) whether general backup mechanisms can restore Build Agent changes. No monitor: every first-party candidate returned HTTP 200 with 0 substantive characters without a browser.

Evidence