Note: This feature is currently available as an early access feature for all paid plans of Creator 6

1. What is build agent?

Build agent is an AI-powered development assistant in Zoho Creator that lets you modify your application using natural language prompts. Available in both edit mode and live mode, it can be accessed through the build agent icon () in the application interface. The icon is located on the left edge of the screen in edit mode and in the top navigation bar in live mode.

Note: When environments are enabled for your application, the build agent can be accessed only from the edit mode and live mode of the development environment.

1. Create and modify components: Forms, fields, reports, pages, workflows, and functions.
   
2. Configure application settings: User and portal permissions, localization, and general application settings such as time zone format, and app name
   
3. Generate Deluge scripts: For workflows, functions, page scripts, and snippets.
   

Note: 

1. Build agent can create new components and update existing ones. It does not have access to records stored in forms and cannot delete any application component or record.
   
2. It is recommended to use build agent with applications in environments to ensure that changes are tested before reaching production.
   
3. If the build agent is interrupted or encounters an error during the modification process, it rolls back all changes from that request to ensure that partially applied changes are not retained.
   

1.1. How does it work?

Note: Changes applied through the build agent cannot be reverted. Review the Change Summary carefully before applying the changes. 

2. Prerequisites

1. Navigate to Operations > Applications > Early Access Features.
   
2. Search for Build Agent and turn on the toggle to enable it for your account.
   

1. To use build agent, set up Zia to manage AI features across your Creator account. Zia is configured with the Zoho GenAI LLM provider by default, so no additional setup is required. If you prefer a different provider, you can integrate Zia with any of the supported LLM providers (OpenAI and Anthropic). Setting up Zia is a one-time process that grants access to all Zia features, including Build Agent. Learn how to configure Zia.
   
Security tip: Zoho GenAI LLM is available for free and processes all prompts within Zoho, while external LLM providers process data in their own systems. Avoid sharing sensitive or regulated information in your prompts when using external providers.
2. Once Zia is configured, enable the Access toggle for Build Agent under the Enable Features section to start using it in your applications.
   

Note: Build agent is not supported when Google Gemini is configured as the AI provider. Switch to a supported provider in Zia settings to access this feature.

3. Navigation guide to build agent

The build agent icon () appears in different locations depending on which mode you are in.

1. In edit mode
   The build agent icon () appears on the left edge of the screen. Click it to open the chat panel as a left-side slider.
   
   
   
2. In live mode
   The build agent icon () appears in the top navigation bar. Click it to open the chat panel on the right side of the screen.
   

4. Build agent interface

1. Session toolbar
   Located at the top of the panel, the toolbar contains three controls:
1. New session (): Starts a fresh conversation. Use this when switching to an unrelated task or when the context from the current session is no longer relevant.
   
2. Conversations (): Opens a list of your previous conversations for the current application. Select any conversation to resume it or review the changes made.
   
3. Slider icon() / Close (X): In edit mode, collapses the chat panel back to the left edge of the screen. In live mode, closes the chat panel. In both cases, your session is preserved.
   
2. Conversation area
   The main body of the panel where build agent responds to your prompts. It shows the exchange between your requests and build agent's responses, along with the Change Summary when changes are proposed.
3. Prompt field
   The input area at the bottom of the panel. Type your requirement here in plain language. The prompt field also includes two additional controls:
1. @Mention: Type @ or click the @ icon and select a component to reference it in your prompt. This helps Build Agent identify the exact part of the application you want to modify.
   
2. File upload (): Attach images, PDFs, CSV files, or text files to your prompt to provide additional context. For example, you can upload screenshots, sample data files, or reference documents to help Build Agent better understand your requirements. 
   

Note: You can attach up to 10 files per prompt, with a maximum size of 10 MB per file.

5. Use cases

5.1. Adding a report to an existing application

5.2. Adding a field to a form

5.3. Setting up a workflow through conversation

6. Write effective prompts for build agent

6.1. Tips for best results

1. Name the exact component -  Use @-mentions to refer to the specific form, report, or page you want to modify instead of describing it generically. Referencing the correct component helps build agent generate the intended result.
   
2. Specify field types and constraints upfront - Include the required field type, such as text, dropdown, or date, along with any constraints, such as mandatory or unique. Providing these details early helps avoid unnecessary validation cycles.
   
3. Build in the right order - Create forms and fields before workflows and functions, and create workflows and functions before pages, as pages rely on the underlying data model.
   
4. Plan before making major changes - For large or multi-step requirements, ask build agent to generate a plan first. Review the proposed approach and proceed with the implementation in phases.
   
5. Use the right vocabulary - Specific right terms in prompts to produce specific results. For example, using Function lets build agent to create a function logic which can be reused, while specifying an HTML snippet instructs it to generate a custom-styled element. Similarly, terms such as workflow and lookup help build agent identify the appropriate components and generate more accurate results.
   
6. Describe workflow logic step by step - When creating workflows or functions, describe each step in simple language and refer to the exact field and form names. If the result is not as expected, rephrase the requirement instead of submitting the same prompt again.
   
7. Restate context when you switch topics - During long conversations, build agent may summarize earlier interactions. Providing a brief recap when introducing a new topic helps maintain context and improve accuracy.
   
8. Read the change summary before approving - The change summary is your opportunity to review the proposed changes. It outlines the modifications build agent will make and highlights any default choices applied during generation.
   

6.2. Example prompts

1. Creating a form with specific field types
   "Create a Customer form with fields: Name (text, mandatory), Email (email, unique), Phone (phone), Status (dropdown: Active/Inactive)."
   Specifying field types and constraints upfront helps build agent create the form accurately.
   
   
2. Adding a filtered report
   "Create a report on Tasks showing only records where Priority is High."
   Clearly stating the filter criteria helps build agent generate a report that displays only the relevant records.
   
   
3. Creating reusable logic
   "Create a Function discount_by_tier, then call it from the Order and Quote forms."
   Using the word Function tells build agent to create a reusable Deluge script rather than inlining the same logic in multiple places.
   
   
4. Building a custom-styled dashboard tile
   "Build this dashboard tile as an HTML snippet so I can style it myself."
   Mentioning HTML snippet prevents build agent from generating a standard chart or gauge.

7. Points to note

1. Applied changes cannot be reverted. Review the Change Summary carefully before clicking Apply Changes, as approved changes take effect immediately.
   
2. Only application components such as forms, fields, reports, pages, workflows, and functions can be created or modified. Records stored in forms are not affected.
   
3. Build agent operates only within the application from which it is accessed and cannot directly access other Creator applications or external systems.
   
4. If integrations are already configured and authorized in the current application, Build agent can use them to perform the requested operations.
   
5. If the submitted request is off topic or unsupported, build agent rejects the request and prevents any partial implementation of changes.
   
6. Requests are based on your prompt and any components you @-mention. If no components are specified, build agent uses contextual understanding of your prompt to identify the component to modify.
   
7. Requests that are too complex for a single session should be broken down into smaller tasks. For instance, a large request such as creating multiple workflows on a form should be split into separate prompts instead of being combined into a single prompt. This helps prevent incomplete execution and improves accuracy and reliability of results.
   

1. Zoho GenAI LLM is available for free and it processes all prompts within Zoho, while external LLM providers process data in their own systems. Avoid sharing sensitive or regulated information in build agent when using external providers with Zia.
   
2. Build agent does not consume any AI calls or API calls from Zoho Creator. However, the LLM provider configured with Zia may still enforce API rate limits. These limits are restrictions that the LLM provider imposes on the number of times a user or client can access their services within a specified period of time and vary based on their usage tier and the model consumed. Rate limits for LLM providers can be referred by their respective official documentation.
   
1. OpenAI rate limits
   
2. Anthropic rate limits
   
3. Along with your prompts, the system may add supplementary prompts to enhance the accuracy of build agent responses. These system-generated prompts are also counted toward AI usage by the LLM provider configured in Zia.
   

1. The following operations are currently not supported with build agent:
   
1. General: Record based operations, including adding, modifying, or deleting records, and deletion of application components.
   
2. Forms: Field encryption, field deletion and field type changes, role hierarchy settings, form submission notifications, mobile and tablet customizations, cross-application relationships, and form deletion.
   
3. Reports: Pivot reports, custom sorting and grouping, record templates, advanced layouts, mobile and tablet customizations, and report deletion.
   
4. Workflows: Cloud functions written in Node.js or Java, and approval, payment, and batch workflows.
   

8. Related topics

1. Configuring Zia
   
2. Understand Zia features in Creator
   
3. AI features in Creator powered by Zia
   
4. Modes of an application
   
5. Early access features