The Tripletex integration allows you to synchronize employees and/or products between AppsCo One and your Tripletex account.
The synchronization of products can be carried out from Tripletex into AppsCo, while the transfer of employees can happen both ways - from Tripletex into AppsCo and vice versa.
When a successful integration has been set up, the automatic synchronization process will happen just after midnight every night.
How to set up a Tripletex integration:
1. Go to Settings → Integrations and click on the + icon.
2. In the window that opens, select Tripletex.
3. In order to set up the integration, you will need an API token from Tripletex, which you can find in your Tripletex account (my profile) in the API access tab.
4. Add a new token in Tripletex and click on Create token.
5. Add the token from Tripletex into the dedicated API field. Use production parameters will be activated by default. Deactivate if needed.
6. Click Add.
7. The integration will be added to the integration overview.
8. The overview will display all integrations connected to your AppsCo organization. The following will be displayed: the name of the integration, if it is active, the last time it was used and the number of potential errors.
Generate and map fields automatically → This field allows you to automatically map fields from Tripletex into AppsCo. Confirm to complete the mapping.
Deactivate – Clicking on this button deactivates the integration and stops the integration process. Confirm to complete the deactivation.
Synchronize – Clicking on this button starts the synchronization of customers, products or customers. The choices available in the sync drop-down will depend on the sync setup. Confirm to complete the synchronization.
Support documentation – Link to the existing support documentation. (Coming soon)
Delete – Clicking on the Delete button deletes the integration process. Confirm to complete the deactivation.
Connection settings - Here you can find the current API key / token from Tripletex.
Settings for synchronization - Choose the type of synchronization from the drop-down menu: No synchronization, AppsCo One to Tripletex or Tripletex to AppsCo One.
Synchronization of employees - Select which type of synchronization should take place, if any: No synchronization, AppsCo One to Tripletex or Tripletex to AppsCo One.
Synchronization of products: Select between No synchronization or Tripletex to AppsCo One.
Synchronization of customer: Select between No synchronization or Tripletex to AppsCo One.
Category name filter for customers sync: Add a specific Tripletex category name for sync.
Integration field mapping
On this page you will find all supported Tripletex fields that are imported and synchronized with AppsCo fields.
The left column displays all Tripletex fields (required fields marked with *). The column on the right displays the corresponding AppsCo One fields. When mapping fields automatically, the system will choose the best possible option by default, but the choice can be customized by choosing any other field in the dropdown menu. Fields that are mappable will automatically be updated with the next sync. Fields that are not mappable will be marked and the user will be informed why.
The reasons for not mapping a field could include that the field is part of a work agreement or that the field will be auto-mapped through the customer or employee profiles?
Change log – This tab displays the change log for all fields which includes the field name, message (if the mapping was successful or not and why), what the field was changed from and to, time and date stamp, name of the person who carried out the synchronization as well as the status (success or warning).
Execution log - this tab shows all successful synchronizations] with the most recent on top of the page.
The processes will either have a successful or failed status. By clicking on an execution in the log with failed status, details about why the error that occurred will be displayed. Furthermore, clicking on the failed code will display the error log data and point to what needs to be fixed for the sync to be successful.