What is it?
ITONICS allows you to connect to Trendone to pull different trend data into your application. The following steps describe how to set up the connection and pull the data from the Trendone API into your ITONICS instance.
How does it work?
Please note: ITONICS does not provide a basic Trendone license, but the integration interface to connect to the Trendone API using your own license key. This feature needs to be activated by ITONICS. Please contact your Customer Success Manager for further assistance, especially in setting up the cron process for creating Trendone elements in ITONICS.
Setting up the Trendone-ITONICS connection
The first step is to enable the Trendone module for a specific entity you want to work with, likely a Trend entity type. Go to Settings > Entity Configuration > Entity Configuration and open the entity by clicking the edit (pen) icon.
Look for the Trendone card under the Modules/Features section and check the box on the left corner of the module card. (Please contact your Customer Success Manager if the card is not visible).
On the module card, select the source entity from Trendone, which are either microtrends, macrotrends, or megatrends. Note that once the selection is done for a particular source entity, this selection cannot be reverted again, unless the Trendone module is disabled and re-enabled again completely for an entity type. Note that one the mapping for a particular Trendone entity type can only be mapped to one corresponding ITONICS entity type at a time.
Once the checkbox is marked, the card should change the layout color from light grey to the system color. Do not forget to press the Save button at the bottom of the page.
After enabling the module, you can configure it according to your preferences. To access the Trendone Configuration, click on the respective entity (e.g. Trend) and go to Manage Trendone Integration.
The API Key was already activated by default. That is why you only have to conduct the field mapping to determine which ITONICS field has to be enriched with which Trendone information. Here is how you use the Field Mapping:
ITONICS recommends the following mapping for a correct integration:
- Choose the respective ITONICS Field (1).
- Choose the Trendone Field to enrich the ITONICS Field (2).
- Remove the field mapping (3).
- Add more fields to the mapping (4).
Note that the following fields must be mapped for the integration to work:
- Entity type title field and Trendone title field
- Entity abstract field and Trendone description field
Within the Update Configuration, it is possible to enable different crons for creation, update, and archive/delete of Trendone elements, and to define corresponding Webhook keys that can be used for testing and/or triggering a request between your ITONICS instance and corresponding Trendone API application. Note that per default, all three crons will be deactivated in newly configured entity types.
Please note: The webhook generation and update should be done conjointly with ITONICS experts to ensure proper configuration and functioning. When a cron (recurring job) is configured, the respective request to Trendone needs to be created, which can not be done by platform administrators. Hereby, it is also possible to define a date threshold, to restrict the amount of data to be fetched from the Trendone API. Please contact your respective Customer Success Manager.
Automatic element creation
Once the mapping is configured, the create cron can be enabled (1) to push all information received from the Trendone API to the application to create an element. Hereby, the system will validate the ID to determine whether a corresponding Trendone element has already been created within the ITONICS system. Each time the setup cron is run, the application validates whether any new element data from Trendone does not yet have a corresponding, existing ITONICS element.
Be aware that if there are any mandatory ITONICS fields mapped to a corresponding Trendone field, for which no value is provided during the creation process of Trendone element in the ITONICS system, then the respective element is created in Draft status.
Automatic update process
Further, the Trendone integration does now support an update use case for already existing elements. Check the Automatic update process option (2) to enable the update cron. Once set up and run, the system will validate if the Last change date stored on ITONICS side matches the Last change date provided on Trendone side. If the latter is greater than the date stored on ITONICS side, the existing element will be overwritten with the updated data provided by Trendone. If there has not been any update of field information by Trendone, the element data will not be updated from the cron. Thereby, only the fields mapped in the Field Mapping configuration are updated via the update cron. If no field having an update on Trendone side is mapped on ITONICS side, the system will not update any existing data, but update the Last change information accordingly. Be aware if any manual changes have been performed for fields mapped in the Field Mapping configuration, and the update cron runs for the individual element, the manually added data will be overwritten with the data provided by the Trendone API.
In either case, to manually test, or run the create and/or update cron (dependent on which is/are enabled), you can trigger the webhook URL (3). Otherwise, the crons will run automatically based on the frequency set up by and defined jointly with ITONICS.
However, as outlined above, there is also the option to limit the scope of elements being pushed from the Trendone API into ITONICS based on a configured date threshold, i.e. to not fetch any Trendone data older than 2023.
Note: To prevent overwriting issues, ITONICS recommends to not configure the same fields within the mapping configuration of the Crunchbase, Tracxn, Trendone, respectively Salesforce, if they are utilized simultaneously for the same entity type.
Note: If a particular Trendone element is deleted in the system, it will again be pushed into the application once the next automatic create process to create elements is run. To prevent this from happening, instead archive any respective Trendone element. However, if an element is removed from the pool of elements on Trendone side, this can be reflected on ITONICS side by configuring the below outlined archive/delete cron.
Automatic archive/delete process
You can archive elements created via the Trendone create cron manually within the system, or you may enable the automatic archive cron for deprecated elements (4). Per default the cron is set to archive deprecated Trendone elements, however, the cron can also be set to automatically delete deprecated Trendone data from the ITONICS system (5). Elements are considered “deprecated” based on the information provided by the Trendone API logs. Once Trendone considers element data to be outdated, respectively not relevant anymore, the particular element IDs will be logged as “deprecated”. Once the automatic archive/delete cron is set up, the system will check the logs provided by Trendone, compare with the existing data in the particular ITONICS system, and, based on the configuration, either archive or delete the corresponding elements on ITONICS side.
Again, to manually test, or run the archive/delete cron (dependent on which option is enabled), you can trigger the corresponding webhook URL (6). Otherwise, the cron will run automatically based on the frequency set up by and defined jointly with ITONICS.
Do not forget to save any configuration done in the Trendone Update Configuration via the Save button (7), or optionally abort any change done via Cancel (8).
Trendone Logs
Refer to the Trendone Log page to track if and when a cron job has run between the Trendone API and the ITONICS system. You can find the log page by navigating to Settings > Logs > Trendone. The Trendone Logs interface will show a list of all run cron jobs, including creation, update, and archive/deletion cases. Further, any create, update, archive, or delete action is also logged in the element-specific and global timeline.