Description:

Vtiger CF works with any fields including custom fields. Vtiger CF takes as input field labels. Using field labels solves the issue of same custom fields/labels having different field names on different Vtiger installations – ex. cf_715, vs cf_801. Custom field names are automatically generated by Vtiger and can’t be modified through the Vtiger CRM UI. Field names are needed for insert etc., db operations. Custom field labels on the other hand are specified in the Vtiger CRM UI.

Node dialog configuration:

Setup tab:

Use configuration file – true/false, whether to read the node configuration from an external json file

File – configuration file name or URL. This could be a local path or file path on the server where KNIME will run in headless mode.

Vtiger URL – Vtiger server URL

Username – Vtiger username

CRM access key – Vtiger user access key

Module – Vtiger module to call, currently only Leads is supported

Operation – operation to perform on the module, currently only Create is supported

License tab:

License Server – license server URL

Licensed Site – domain URL on which the node is licensed and is running on

License Code – license code

Node input: table, one row for each lead to be created in Vtiger

table columns – Vtiger Lead field labels( exactly how they are shown in the Vtiger Lead creation UI ), all are of type String

Source Form
Company
First Name
Last Name
Designation
Primary Email
Primary Phone
Documents
Webinars
Lead Source

Node output: table, one row of data for each new lead created

table columns – Vtiger Leads field names( not field labels, field names are stored in the database), all are of type String, 34 fields

country
firstname
code
lead_no
leadstatus
city
rating
description
industry
salutationtype
modifiedtime
annualrevenue
noofemployees
company
state
id
fax
email
lane
cf_763
website
emailoptout
cf_765
cf_767
secondaryemail
mobile
assigned_user_id
createdtime
lastname
pobox
phone
leadsource
modifiedby
designation

-end-