Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Introduction
The connector package is zip file containing configuration files related to Cutsom Connectors. These configuration files has their own specific format. The intent of this document is to describe the contents of connector package and format of the configuration files to be placed in package zip.
Contents of Connector Package
The connector package zip contains below files
- Image file for Connector.
- XML and JSON Layouts for Trigger and Action entities.
- Triggers And Actions Text file.
- Lookup configuration file.
Follow the below steps to create Connector package
- Identify the Entities for Connector
- Refer the Connector documentation to know about what entities are available in it. For example for an CRM App the entities can be Lead, Contact or Customer etc.
- Make list of entities and endpoints that you want to integrate with.
- Make list of attributes (fields) for each entity.
- Create XML and JSON Layout Files for each entity.
- For Each entity
- Create EntityResponse.xml file and EntityResponse.json file.
- Create EntityRequest.xml file and EntityRequest.json file.
- For example: for entity Lead create file LeadResponse.xml and LeadRequest.xml
- Edit the above created xml and JSON files in Text editor
Paste the below sample XML in xml file.
Entity Layout Expand sourceAdd the entity name as a tag in this xml file. For exmaple for Entity Lead see below xml
Entity Layout<
Root
>
<
leads
>
</
leads
>
</
Root
>
Enter the attributes of this entity as individual elements in this xml and save this file.
Entity Layout Expand sourcePaste below json into JSON file.
Entity Layout Expand sourceAdd the entity name as a children in this json file. For exmaple for Entity Lead see below json
Entity Layout Expand sourceEnter the attributes of this entity as individual elements in this json file and save this file.
Entity Layout Expand source
- Now we should have below files ready (if we have 3 entities Lead, Contact and Customer )
- LeadResponse.xml
- LeadRequest.xml
- ContactResponse.xml
- ContactRequest.xml
- CustomerResponse.xml
- CustomerRequest.xml
- LeadResponse.json
- LeadRequest.json
- ContactResponse.json
- ContactRequest.json
- CustomerResponse.json
- CustomerRequest.json
- For Each entity
- Create Triggers and Actions File.
- Create a new Text file named triggersAndActions.txt and edit it in Text editor.
Paste below JSON data in this text file. This JSON data is sample data having no Triggers and actions in it.
Triggers and Actions JSON Expand sourceFor each entity identified in Step 1, create a Trigger object as shown below. The below JSON shows Trigger object for Entity "Lead"
Trigger Expand sourceAdd the Trigger Object to triggers field in triggersAndActions.txt. By adding a trigger the file would look like as shown below
Triggers and Actions JSON Expand sourceCreate New Trigger objects for each Entity and add to triggers field. Below JSON shows triggersAndActions.txt file with two Triggers.
Triggers and Actions JSON Expand sourceFor each entity identified in Step 1, create a Action object as shown below. The below JSON shows Action object for Entity "Lead"
Triggers and Actions JSON Expand sourceAdd the Action Object to actions field in triggersAndActions.txt. By adding a action the file would look like as shown below
Triggers and Actions JSON Expand sourceCreate New Action objects for each Entity and add to actions field. Below JSON shows triggersAndActions.txt file with two actions.
Triggers and Actions JSON Expand source- Add URL for each Trigger and Action defined in this file.
- Define key value pairs for each trigger and Action.
- The key should be Trigger or Action value defined in triggers or actions field.
- The value should be the complete URL endpoint to be hit for this particular trigger or action.
- Define a special Key Value pair for account Testing. The key should be "testaccount" and value should be the url to test the Connectivity with connector account
Triggers and Actions JSON Expand source - Add method for each Trigger and Action defined in this file.
- Define key value pairs for each trigger and Action.
- The key should be Trigger or Action value defined in triggers or actions field.
- The value should be the complete http method to be used to hit url for this particular trigger or action.
- Define a special Key Value pair for account Testing. The key should be "testaccount" and value should be the http method to be used to hit to test the Connectivity with connector account
Triggers and Actions JSON Expand source - Save this file. triggersAndActionsJson.txt file is ready.
- Create Lookup file.
- Create a xml file named lookupConfiguration.xml
Paste below content into it
Lookup Configuration Expand sourceAdd Each entity in Columns tag as shown below
Lookup Configuration Expand sourceAdd attributes for each entity as shown below
Lookup Configuration Expand sourceAdd Operators for each field Type and apiField type
Lookup Configuration Expand source- Lookup Configuration file is ready.
- Download Image File.
You can download the connector Image file from respective Connector Provider.
The image file should be in PNG format.
The name of the image can be any valid name.
Zip the individual files in a zip file. See the Zip Contents below
Image AddedImage AddedImage AddedImage AddedImage AddedImage Added
Panel | ||||
---|---|---|---|---|
| ||||
What's newBest practicesFrequently asked questionsAdeptia Connect APIsAdeptia security report |