Connections: Services with distinctive authentication requirements
Description
Deluge facilitates the integration of third-party services with your Zoho service. Connections specify the service to integrate, and invokeUrl Deluge task allows you to perform webhook calls on the connected service.
To create a connection, you need to provide its connection name. Furthermore, some services let you choose from the list of available scopes.
Note:
The connection name is the link name of the connection, used in the invokeUrl task.
The scope specifies the operations which can be performed using the connection. The operations likely to be done with a connection, vary according to the third-party service that is connected.
Once a connection is created, it has to be connected. It is typically connected by providing your login credentials of the respective service. If you are already logged into the service, it is connected right away as you click allow on the user permission dialog box which pops up. However, to connect with some services you need to provide additional specifications besides the login credentials.
The default services under the Pick Your Service with additional authentication requirements are listed below.
| Service | Requirement | Description |
Shop's name |
| |
API key, API secret |
| |
Complete domain URL |
| |
API key |
| |
Access token |
| |
Zendesk subdomain name |
Note: The invokeUrl task appends the subdomain name to the URL supplied to it. So, the URL specified by the user should not be subdomain appended. For example, the URL specified in the Zendesk API to access tickets is https://{subdomain}.zendesk.com/api/v2/tickets.json. However, the user should exclude the subdomain name from the URL (i.e., https://zendesk.com/api/v2/tickets.json) to supply it to the invokeUrl task. The above mentioned is a general rule of thumb for every third-party service that requires a subdomain name to connect with your Zoho service. | |
Jira subdomain name |
|