Datasource is used to manage a module from a third party service in Creator with the help of the connection created linking the said service. This enables you to access data housed in an external service and use it in your Zoho Creator applications. Let's assume you have a Zoho CRM account in which you have data in Leads module. If that service provides API support for Create, Read, Update, and Delete actions for the Leads module, you will be able to manage that module in Creator itself. But to connect with that particular account, you need to create a connection and authorize access. This creates a secure form of managing data across platforms.
On successfully creating the datasource, you can create a form based on the required module in your Creator application. The fields in the third party module automatically become the fields of this newly created form. When you submit a record in Creator using the form, a record gets added in the third party module as well. This action is performed with the help of the authorized connection that is created for this service.
Create Datasource
The prerequisite to create a datasource is to create a connection and authorize it. A connection becomes the bridging link between your application and the external service that has the required data. To create a new datasource:
Navigate to Microservices.

Click Create New button.

Click Create under Datasources.

Select the required service.
Select the connection for the service.

Select the Module based on which the datasource needs to be created.
Note: The datasource name will be auto-generated based on the module selected, in the format: <service-name> [space]<module-name> <sequence>, in general. And <service-name> Datasource <sequence> in case of modules involving special characters. This can be edited if necessary by clicking the Name your datasource field.
Click Create button. The datasource is created.

Note: Please note that you need to enable connection access to the application to be able to create datasource.
Datasource Access
The Datasource details page of each of the datasource that you have created provides information specific to it. The Datasource Access section lists the list of applications. You can enable access to those applications. By doing so, the datasource will be available for those applications.
Datasource Configuration
Datasource configuration section lists the respective configuration fields of associated service module. With datasource configuration/reconfiguration, you can revisit the datasource settings and modify the configuration fields as needed. This provides greater flexibility, allowing adjustments as integration requirements evolve.
To modify or add configurations to an existing datasource,
Navigate to Microservices > Datasource.
Select the datasource you want to update. In the Datasource Details page, click Configure. A popup will appear where you can configure the fields that are specific to that datasource.
On clicking Reconfigure, you can modify the configured fields.

The fields available for reconfiguration vary based on the module and service of the datasource. For instance, if you're using Zoho Projects, you can adjust the preconfigured fields like Projects and Portals settings.
Configuring Imported Datasources
Imported datasources doesn't come with predefined datasource configurations. You need to manually configure the applicable fields to ensure they function correctly. This involves configuring the relevant fields according to the chosen module or service from the datasource configuration section on clicking Configure.
After an imported datasource has been configured, you can modify it later using the Reconfigure button.
Delete Datasource
To delete datasource:
Navigate to Microservices. The window will appear with the listing for the microservices.
Hover on the datasource.
Click the ellipse icon.
Select Delete. The delete confirmation pop up will appear.

Click Delete button. The datasource will be removed.
Points to note
When configuring an imported datasource, ensure that all essential fields are keyed in correctly, similar to the initial setup process.
Any modifications to the configuration will clear all existing data.
The updated changes will be reflected across all applications using the datasource.