Create extensions using cloud editor

Overview

Zoho Marketplace is an online store where you can upload the extensions you develop for any of the products of Zoho. You can also use the available extensions in our store for your business. This developer guide will help you build an extension and deploy it to our Marketplace.

Things to remember before you start

The manifest file

Every extension must have its own plugin-manifest.json file that defines its behavior. After defining this file, you can use client-side technologies like HTML, JavaScript, and CSS to build your extension. You can host the extension privately or declare it public.

Private and public extension

You will have to declare the extension as private or public when you submit it to us. However, learning their differences might help you to plan your work better:

BehaviorPrivate ExtensionPublic Extension
VisibilityWhoever has the installation URL will be able to access the extension.Everyone
Review after submission NAYes.
The extension will be reviewed and published by us to Zoho Marketplace.

Create extensions using cloud editor

Create extensions with cloud editor, provided by Zoho Sigma. Sigma supports Zoho services such as, Projects, BugTracker, Desk, Orchestly. Create a private workspace and start building your extensions in Zoho Sigma. Once built, you can test your extensions and publish it right away. The following are a few highlights of the cloud editor:

  • Your extension development can be entirely managed online.
  • The installations of 'Node.js' and 'ZET ( Zoho Extension Toolkit )' are not needed and the user can start coding their app once they are on-boarded to their workspace.
  • The app folders and the default 'plugin-manifest.json' file are automated so one need not spend time in creating them manually using the CLI.
  • You can choose to build an extension from scratch or import the file from a local editor and manage it here.
  • The editor supports version management so you can revert your extension to its previous version if necessary.
  • Handle events with the help of the triggers available in the editor.