Zoho Creator integration in CRM Sandbox

Zoho Creator can be integrated in the Zoho CRM sandbox environment. Clients can safely build, test, and validate their Creator-powered CRM customizations - such as Custom Tabs, Related Lists, and more - before deploying production.

With this integration, clients can:

Develop and test changes in a safe Creator + CRM Sandbox environment.
Validate how the app behaves inside CRM before any real users are impacted.
Move confidently through development - staging - production in Creator.

How it works

Zoho Creator apps come in two types. Only one is supported in sandbox - and it's the right one for structured, multi-stage development.

Note. Only environment-based Creator apps can be imported into the CRM Sandbox. If a client's app does not use environment-enabled apps, it won't appear in the Sandbox import list.

Here's the environment mapping explained:

To know more, check out our help doc.

Here's a list of what you can (and can't) do in Sandbox:

Let's look at some scenarios -

Scenario I - Testing a new custom tab

A logistics company wants to add a Shipment Tracker Creator app as a tab within their CRM Contacts module but before rolling it out to their 200 users, they run it through a controlled testing process. The developer begins by importing the Creator Dev app into the CRM Sandbox, where they test how the tab appears, verify that the data flows correctly, and confirms that form fields behave as expected.

Since this is a sandbox environment, they can iterate freely - editing the Dev app's form builder directly from within CRM Sandbox without any risk. Once satisfied with the results, the developer moves the app to Stage for final validation before eventually pushing it to Production.

Scenario II - Validating a Related List

A financial services client uses a Creator app to display loan history as a Related List inside the Accounts module. To validate this setup, the team imports the Stage version of the app into their Sandbox environment and confirms that the Related List renders correctly - with the right fields and permissions in place.

One key thing to note: Stage apps are view-only in CRM Sandbox. No form editing is allowed at this stage; the goal is purely visual and functional validation before moving forward.

That said, even in a view-only state, Related Lists can still reflect data interactions. This is where data storage behavior becomes important to understand.

When a Dev or Stage app is connected to CRM Sandbox, any data created through its Related Lists is not stored in Sandbox — it is stored back in the corresponding environment's reports in Creator. This means data created via a Dev app is saved in Dev reports, and data created via a Stage app is saved in Stage reports.

Scenario III - Managing team permissions

A project manager looking to grant a new developer access to a Creator app from within CRM sandbox can do so without any friction. This is fully supported - CRM users can be assigned as developers to the respective Creator Dev or Stage app directly from the Sandbox environment, making team permission management straightforward and contained within the same workspace.

Notes.

Changes made in Sandbox (new Creator tabs, Related Lists) will not appear in the CRM Deployment module yet.
Creator tabs are linked to Teamspace. Since Teamspace cannot be deployed to Production, a conflict warning will appear. Clients can remove the Creator tab from Teamspace settings before deploying other Teamspace changes.
If a CRM Production org is already integrated with a Creator workspace under User A, and User B tries to connect a different workspace in Sandbox, an error will appear. Only one Creator workspace integration is permitted per CRM org.