This help page is for users in Creator 6. If you are in the older version (Creator 5), click here
. Know your Creator version
What Does This Page Cover?
Learn about connections and their types that can be used to integrate your Creator application with Zoho and non-Zoho services.
Connections are intended to connect to external facilities. They enable you to integrate your application with various other cloud services. By utilizing Connections, you can effortlessly connect and interact with external services, leveraging the functionality and data they provide, thereby enhancing your application's capability.
Connections in Zoho Creator
Connections are like a gateway to communicate with other Zoho or third-party services from Zoho Creator. In other words, connections wrap the whole authentication process and let you effortlessly connect to your accounts in the supported services. Adding a connection to your account is a one-time process. You can use a connection in the context of a form workflow, a report workflow, an integration field, and so on.
Connections can be used in the following places:
- SMS actions
- Payment workflow
- Push data to a third-party service using the integrations action in form workflow
- Deluge's integration task
- Deluge's invokeUrl task
- Page panels
When the connection is created and connected, you can seamlessly transfer data and perform other related operations based on the target service.
When the connection is not connected, you will be restricted from communicating with the target service.
In Zoho Creator Connections are of three types, as shown below.
- System connection
- Admin connection
- Logged-in user connection
System connections are those that are created by default when certain integrations
are performed by the users. The following are the areas where you can utilize system connection:
- To push data to a different Zoho service using the integrations actions in form workflows
- Integrations in the page panels for displaying the data from other services
- Deluge integration tasks in the absence of the optional connection parameter. In other words, when you create an integration task, it generally requires you to specify the connection parameter. If the connection parameter is optional and left unspecified, the system automatically generates a system connection for the specified service.
Though system connections get created by default, only super admin can authorize them, so that they are linked to the required service.
For example, when a Zoho CRM - Get records
Deluge integration task is executed without the optional connection parameters, the system automatically generates a connection to access all Zoho CRM modules. To execute the integration script successfully, the super admin needs to authorize it using their account credentials. Click here
to learn how to authorize a system connection.
These connections can only be created and authorized by super admin, admins, and developers. Regular users or non-administrative roles cannot authorize the connection, but can consume them through admin authorization and thus making the connection as admin connection. Admin connections can have only one authorization. An administrator can create a connection from the list of available services or by custom connectors and authorize it. This connection can be used in places where integration is required. Click here to learn how to create an admin connection.
- Ideally, the administrator can create more than one connection for the same service. However, for payment services like Paypal, Razorpay, or WorldPay, the system allows for only one connection per service. Additionally, it's important to note that all built-in payment connectors only supports admin connections, limiting the authorization capabilities to administrators.
- The availability of payment services differs based on your country/region. Click here to view the payment services that are applicable to your region.
Logged-in User Connection
These connections are created by the Super admin/Admin/Developers and authorized by the respective logged-in users. Unlike admin connections, these connections can hold individual authorization for all logged-in users and can perform the integrations based on the authorization of the user who executes it. These connections enable the integration of third-party services within an application, providing authorization for individual users with authorized access to specific data and functionality.
For example, In the case of a logged-in user connection with Salesforce service and its integration into a workflow to push data to the Salesforce module upon form submission, each logged-in user must individually authorize the connection using their own Salesforce credentials. This ensures that the integration is personalized for each user. When the workflow is triggered, the data will be pushed to the Salesforce account of the logged-in user who initiated the workflow.
- Zoho CRM
- Zoho Recruit
- Clockwork SMS
- Zoho OAuth
- Zoho Projects
- Zoho Sheets
For creating datasources
using logged-in user connections, the primary account is necessary to channelize integrated services through a single account. For example, consider a scheduler workflow that automatically pushes data from a Creator application to Zoho CRM every day. In such cases, the scheduler runs independently without requiring user or admin actions. The scheduler utilizes the authorization of the primary account to perform its tasks.
In the case of datasource
, lets us consider a Zoho CRM
integration form where the data is pushed to the accounts module of the Zoho CRM
through a connection. In order to create a datasource, it is necessary to have a primary account. Here, the integration form will be created with the fields based on the fields in the specified Zoho CRM
module of the primary account. Each logged-in user can authorize this connection individually and add the data to the integration form, which will be added to the specified module of their Zoho CRM
When an admin authorizes a logged-in user connection for the first time, that account will be designated as a primary account. However, any administrator has the authority to change the primary account status and assign it to another administrator's account if needed. If you have not chosen to use the same authorizations for all environments during the creation of a connection, you can set different primary accounts for each environment
to learn how to mark an account as primary.
Portal users and shared users can also authorize the logged-in user connections directly from the live mode of the application. Click here
to know more about accessing connection in live mode of the application.
- In your organization's hiring process, you utilize Zoho Recruit, a cloud-based hiring platform, along with an employee recruitment Creator application. The Creator application collects candidate data, allowing them to fill in their details and apply for job openings, while Zoho Recruit helps streamline the overall recruitment process. Using integration actions in the form workflow, the collected data such as First Name, Last Name, and Email can be automatically pushed to the Candidates module in your Zoho Recruit account. The system generates a Zoho Recruit system connection, which the super admin can authorize to enable data transfer from Zoho Creator to Zoho Recruit. This integration enhances efficiency and facilitates seamless synchronization of candidate data between the two platforms.
- Consider a customer support Creator application where the user raises support tickets or files a request for support in your organization. The customer data is stored in your Salesforce account. To enhance the user experience, you can establish an admin connection with Salesforce. When a user logs in to raise a support ticket, the application can fetch the customer's data from the Salesforce account by matching their email. This allows for auto-population of the user's data wherever necessary within the application. By establishing this admin connection with Salesforce, you ensure seamless access to customer information and improve support ticket management.
- Consider a task management application where team members collaborate on work items. To enhance communication and keep everyone updated, you can establish a logged-in user connection with Zoho Cliq account through the Zoho OAuth connector. With this integration, whenever a task is completed or sent for team's review, an automated notification message will be posted in the designated Zoho Cliq team group from the task owner's Zoho Cliq account.
Navigation Guide to Connections
To access connections, you can navigate to the Microservices section, as shown below.
Points to Note
- Connections can be created only by super admin, admins, and developers.
- System connections can only be authorized by super admin.
- Logged-in user connections can only be created in C6.
- For creating datasources and schedulers using logged-in user connections, the primary account is required to channelize integrated services through a single account.
- Datasource can be only created if the associated connection has same authorization for all the environment and primary authorization linked.
- The number of connections you can create vary based on your Creator plan. Click here for more information on the connection limits associated with your plan.
- Administrators can create more than one connection for the same service. However, payment services like Paypal, Razorpay, or WorldPay, the system allows for only one connection per service. Additionally, it's important to note that all built-in payment connectors only supports admin connections, limiting the authorization capabilities to administrators.
- The availability of the payment services differs based on your country/region. Click here to view the payment services that are applicable to your region.
- Create and Authorize Connection
- Manage Connections
- Connection in Live and Edit Mode
- Understand Connectors