Creating or editing an endpoint for Insightly activity
Endpoints provide the configuration information that the Studio and the Integration Appliance used to connect to Insightly platform. Insightly uses Basic API Key based authentication mechanism so as to authorize users to perform operations.
Selecting or editing an Insightly endpoint
- In the Create Endpoint or Edit Endpoint pane,
configure the Insightly endpoint as described in the following table.Note: Changing the configuration properties of an endpoint affects all orchestrations that use that endpoint in the project. The edits are global, not local.
- Click Test Connection to confirm that the connection details are valid and you are able to connect to the Insightly successfully.
- Click OK.
Field Name | Description |
---|---|
Host Name | Host Name for Insightly instance. |
API Key | Authentication API Key for accessing Insightly instance. |
Following parameters are required in endpoint test connection screen to make connection via Proxy | |
Host Name | Host Name of Proxy Network |
Port | Port Number of the Proxy Network. |
User Name | Specifies the user name for accessing service via proxy network. |
Password | Specifies the password for accessing service via proxy network. |
Objects Supported by the Insightly Connector
Insightly connector supports the Insightly objects: Contacts and Organisation. Also, the connector supports the Create, Update, Delete and Retrieve operation for these objects.
Insightly Objects | Create | Update | Delete | Retrieve |
---|---|---|---|---|
Contacts | Yes | Yes | Yes | Yes |
Organisation | Yes | Yes | Yes | Yes |
Custom Fields support
Insighlty supports custom fields. Provision is given in the connector to create, update and retrieve objects having custom fields.
For Create and Update activities, in the Map Inputs, each object and its child nodes will have additional nodes for custom fields so that user can provide values for them.
For Retrieve activity, the response object will have additional nodes to identify the custom fields.
<customFields> <customFieldName>secondemailid</customFieldName> <customFieldValue>test.test@gmail.com</customFieldValue> </customFields>