What is it?
Connecting your ITONICS Cloud tenant to your ITONICS Enterprise (Nucleus) environment allows you to automatically synchronize data—such as Technologies, Trends, or Startups—between the two platforms via the ITONICS REST API. This ensures consistency across systems and saves manual effort when maintaining your innovation data.
How does it work?
The integration enables a one-way data flow from a dedicated ITONICS Cloud workspace to a corresponding ITONICS Enterprise target system. It allows:
Automatic creation of elements in ITONICS Enterprise based on Cloud data
Automatic updates to existing ITONICS Enterprise elements if Cloud data changes
Manual field mapping between ITONICS Cloud and Enterprise entities to ensure data consistency
Once configured, your teams can maintain data in ITONICS Cloud and see it reflected automatically in ITONICS Enterprise according to your update rules.
Please note: Before proceeding, this integration module must be enabled by ITONICS. The backend configuration steps required for activation have been intentionally excluded here, as they are handled by our team upon request. Please contact your Customer Success Manager for further assistance, especially regarding the cron process for pushing data from your ITONICS Cloud (source) workspace to the ITONICS Enterprise (target) application.
Setting up the connection
Step 1: Enable Cloud integration within an entity type
Go to the desired entity configuration in your ITONICS Enterprise application (e.g., Technology, Trend, Startup)
Enable the Cloud Integration module card for the individual entity type
Select the corresponding source entity from your ITONICS Cloud workspace
Example: A Technology entity in ITONICS Cloud can be linked to a Technology entity in Enterprise
Step 2: Configure field mappings
The Field Mapping tab allows you to map fields between your Cloud entity and the corresponding Nucleus entity. Mapped fields automatically synchronize values between the two systems.
For each ITONICS Enterprise (Nucleus) field, you can select a matching ITONICS Cloud field of the same type.
Important notes:
If a matching ITONICS Cloud field is missing, the mapping cell will appear empty.
Field mappings are cleared if fields are deleted, disabled, or changed in either system.
Dropdown mappings require at least one matched option before saving. Note that any option that is not mapped will not be synchronized.
Supported field types:
| ITONICS Enterprise field type | ITONICS Cloud field type |
| Rich text field | Rich text field |
| Date picker field | Date field |
| Simple text field | Text field |
| Term search field | Tags field |
| List fields (radio, dropdown, pearl chain, etc.) | Dropdown field |
| Single line input (text, number, URL) | Text / number / hyperlink field |
Note that field types like User Search, Element Search, File (references), or Email are not mappable as they depend on internal system structures.
Step 3: Set update preferences
Under the Update Configuration tab, you can define how and when data updates occur.
Automatic create process: If enabled, new ITONICS Cloud elements are automatically created in Nucleus. The system will verify if a respective Cloud element's UID is already represented in the Enterprise system and create a new element if not yet available.
Automatic update process: Updates made in ITONICS Cloud overwrite the mapped fields in ITONICS Enterprise. The system will verify if a respective Cloud element's UID is already represented in the Enterprise system, and update the existing element if available. Changes are tracked in the element timeline.
Webhook URL (global): Applies to all entities with ITONICS Cloud integration enabled
Webhook URL (entity-specific): Applies only to a specific entity type
Data synchronization and logging
Once the integration is active, data synchronization occurs automatically based on your configuration. You can also trigger updates manually via webhooks (for testing purposes) or scheduled cron runs.
Created By / Updated By: If synchronization runs automatically, updates appear as made by External Submitter. If triggered manually by a user, that user’s name appears
Timestamps: Creation and update timestamps are retained from ITONICS Cloud
Logs: On demand, ITONICS can provide a Cloud Logs page listing all synchronized elements and any associated errors, helping to identify issues during data sync.
Tips and best practices
Align field types and dropdown options across both systems to avoid data loss or mismatched values. Note that the integration matches fields based on their machine_name, which is why field title updates are not affecting the mapping.
For large data sets, sync processes run sequentially by entity type; thus, allow enough time for full completion. However, to maintain system performance, ITONICs recommends running a cron once per day to synchronize the data between both instances/systems.
If rich text fields contain formatting unsupported by ITONICS Enterprise, text will be preserved, but formatting (dividers, references) may be stripped. Any RTE formatting supported on both systems will be taken over correctly.