Our Connector users have always benefited from our handpicked list of fields that can be mapped to enrich data fields in their CRMs. But our entire data catalogue actually extends way further, so we decided to grant all Connector users access to our API fields as well. Instead of bloating the data management menu with hundreds of new data points, these additional data points can be mapped by using the Custom Input option.
Custom Input can be found when mapping any field through the Data management panel. Open the dropdown menu and select Custom Input to start configuring the field.
The most important step in configuring the Custom Input is to write the query that references that specific data point in our APIv3. This might look or sound intimidating, but the pattern is actually rather simple:
${company.api_field_name}The api_field-name part needs to be changed to the API name of the field you are attempting to map.
You can also combine text and an API field by writing for example:
Registration date is ${company.registration_date}
Or you can go one step further, and combine multiple API fields and text:
Registration date of ${company_name} is ${company.registration_date}
And that covers most of the basic use cases. You don't need API keys or any other API configurations. Just add data points to Custom Input fields and start gathering even more useful data to your CRM.
📒 We list all available API fields in this document. It is however worth noting that the document describes our APIv2, whereas this feature uses our updated APIv3 which does not have a public documentation as of yet. The data fields and their names are largely similar in both versions, but there are differences in availability and nomenclature. Finding the exact field you are looking for might take some trial & error.
Mapping list fields
The logic described above works well for all data points that only contain a single value. For example, all companies certainly only have one registration date. But in some cases the data points contain multiple values and are therefore considered list fields.
When mapping list fields you need to make a decision on whether or not you want to map the entire list or a specific item from the list. Let's take a company's business units as an example:
${company.business_units.*.visiting_address.city}The * operator is key here. In this case it informs that all values from that data points should be fetched. The end result might look something like this:
Helsinki, Tampere, Vantaa
${company.business_units.0.visiting_address.city}In this example * has been replaced by a number. 0 refers to the first value on the list, 1 would be the second, etc. So using the previous example, the end result would now look something like this:
Helsinki