Need for custom code
Examples of situations when custom code may be a better option can include:
- Major data transformation needs to be performed
- Complex calculations need to be performed
- Faster development times for developers
- Need for cleaner and more maintainable data
For example, if data from two fields need to be concatenated (combined) into a single field in the target application, this can easily be done with the integrator.io wizard. However, if the fields are only to be concatenated based on a value of another field or other dependency, custom code can make it much easier to set this up.
Setting up integrator.io for custom code
In order to access the newly developed record type called Script, you must have the role of a manager for your Celigo integrations and enable Developer Mode within your account profile. Once you enable this, you should see the Script option as part of the waffle box menu of your integrator.io account.
- Pre Save Page: This hook gets invoked at the very end of your export process, right before each page of data is saved and passed along to downstream applications. This hook can be used to modify, add, or delete records.
- Pre Map: This hook gets invoked before your source records are mapped to the destination application and can be used to modify records, ignore records, or return errors related to specific records. Note that changes made to source records in this hook will only persist for the duration of the import, and will not carry over to downstream applications in your flow.
- Post Map: This hook gets invoked after your source records are mapped to the destination application and can be used to modify records, ignore records, or return errors related to specific records. Note that changes made to source records in this hook will only persist for the duration of the import, and will not carry over to downstream applications in your flow.
- Post Submit: This hook gets invoked after your source records are submitted to the destination application. This hook can be used to modify the response data returned by the destination application. For example, you could enhance error messages with fields from the source records, or you could change errors into successes if specific errors are not actionable, etc.
Other custom code options in integrator.io
There are several other options for using custom code in integrator.io:
- SuiteScript: If you are integrating NetSuite, you have the ability to run SuiteScript code within NetSuite as part of your integration.