Getting Started with Zoho Creator: Build Your First Custom App
Before You Start: Plan Your App on Paper
The most common Creator beginner mistake is opening the builder and starting to add fields before defining what the app actually needs to do. Spend 15 minutes answering four questions before touching Creator:
- What is the primary record type? What is the central object your app manages? In our example: a client intake submission. One submission = one record.
- What data does each record need to hold? List every field — client name, contact email, service type requested, submission date, assigned staff member, status, internal notes. Do not worry about field types yet — just list the information.
- Who creates records and who reviews them? In our example: the client submits the form (external user or admin), a staff member reviews it and updates the status.
- What should happen automatically? When a new submission arrives, email the assigned staff member. When the status changes to Approved, create a project record in Zoho Projects. These become your workflow actions.
With these four answers documented, the Creator configuration is straightforward — you are translating a clear plan into the tool, not designing as you build.
Step 1: Create the Application
Log in to Zoho Creator at creator.zoho.com. Click “Create Application” and give your app a name (Client Intake). Creator creates an empty application with no forms or views — a blank canvas.
Creator applications have three types of components: Forms (data entry interfaces — how records are created), Views (display interfaces — how records are listed and viewed) and Reports (aggregated data displays). You will build at least one of each.
Step 2: Build Your Form
Click “Add a Form” and name it “Intake Submission”. This creates the data entry form for your primary record type and simultaneously creates the underlying data table that stores the records.
Add your fields from the left panel. For the client intake example:
- Client Name — Single Line field. Mark as Required.
- Client Email — Email field. Mark as Required. Creator validates email format automatically.
- Service Requested — Dropdown field. Add your service options as the dropdown values.
- Description — Multi Line field. Optional — space for the client to describe their requirements.
- Assigned To — Users field. This pulls from your Zoho One user list and allows a staff member to be assigned to each submission.
- Status — Dropdown field. Values: New, In Review, Approved, Declined.
- Internal Notes — Multi Line field. For staff use — not visible to the client if you later create a client-facing portal view.
Set the Status field default value to “New” — every new submission automatically starts as New without the submitter having to select it.
Step 3: Create a List View
A list view is how staff members see all submissions in a table. Click “Add a View” and select List. Name it “All Submissions”. Choose which fields to show as columns — typically: Client Name, Service Requested, Status, Assigned To, Submission Date. Set the default sort to Submission Date descending (newest first).
Create a second list view called “My Submissions” with a filter condition: Assigned To equals Current User. Staff members opening this view see only their own assigned submissions — a cleaner, more practical view for daily work.
Step 4: Add a Workflow Action
A workflow action in Creator is an automated response to a form submission or record change. Click on your form, go to the Workflow tab and add an “On Add” action — an action that fires when a new record is created.
Add an Email Alert action. Configure it to send an email to the Assigned To field value (the assigned staff member). Write a subject line using a merge field: “New intake submission: #{Client_Name}”. In the body, include the client’s name, email, service requested and a link to the submission record.
This single workflow action ensures every new submission generates an immediate notification to the assigned staff member — no manual checking of a shared inbox required.
Step 5: Add a Basic Deluge Function
Creator’s visual workflow tools handle simple actions. For logic — “when this condition is true, do this; when this other condition is true, do that” — a Deluge function is more appropriate.
A practical addition to the client intake app: when a submission is marked Approved, automatically create a Project record in Zoho Projects. Add an “On Edit” workflow action that triggers when the Status field changes to “Approved”, and write this Deluge function:
This function demonstrates the core Creator-to-Zoho-Projects integration pattern. The Deluge introduction guide covers the Deluge language fundamentals if this syntax is new to you.
| // Trigger: Status field changes to “Approved” // Action: Create a project in Zoho Projects for this submission submissionId = input.ID; clientName = input.Client_Name; serviceType = input.Service_Requested; // Build the project details projectDetails = Map(); projectDetails.put(“name”, clientName + ” — ” + serviceType); projectDetails.put(“description”, “Project created from approved intake submission ID: ” + submissionId); projectDetails.put(“owner”, zoho.loginuserid); // Create the project in Zoho Projects response = zoho.projects.createProject(“your_portal_name”, projectDetails); |
|---|
Step 6: Test Before Deploying
Test your app thoroughly before sharing it with your team. Submit five test records covering normal cases (standard service request, assigned to a real user) and edge cases (very long description text, status changed multiple times, submission with no optional fields). Check that every workflow fires correctly and review the execution log for any Deluge errors.
Creator provides a preview mode where you can test the form and views before publishing. Use it. The most common beginner mistake is deploying an untested app to your team and then fixing errors while they are trying to use it.
What You Can Build Next
The client intake app you built in this guide is a foundation. From here, the most common extensions ABR adds for clients:
- A client-facing portal view that gives external clients access to check the status of their own submission without seeing other clients’ records.
- An approval workflow that routes the submission to a manager when the assigned staff member marks it as Ready for Approval.
- A reporting dashboard that shows submission volume by service type, average time to approval and current status distribution.
For the full range of what Creator can build, see the 10 real apps you can build with Zoho Creator guide. For help building a Creator app tailored to your specific business process, see the Zoho Creator consultant hub.
Frequently Asked Questions
What do I need to get started with Zoho Creator?
How long does it take to build a first Zoho Creator app?
Can non-technical users build Zoho Creator apps without a consultant?
What is the difference between a Zoho Creator form and a Zoho CRM module?
Can ABR help us build our first Zoho Creator app?