Import actions are used for automating imports and updates from another system, or from special format fields in your system. Export actions are used to export information from your system into a new file. Both Import and Export actions are typically initiated by time-based rules that run after hours, which helps mitigate the impact of a large-sized import or export on the system.
If real-time sync is not needed, you can automatically import changed data from another system into by using an Import action to update or create the relevant records. Conversely, you can schedule a nightly Export action to export data from for importing into another system. |
When you create an import action, you configure options with a wizard that is very similar to the normal import wizard used for manually importing data. If your goal is to synchronize data between systems, which is often the case, place the import action in a time-based rule in the table into which you want to import data.
On the General tab, name your action and give it a description.
Once your action is saved, the system automatically adds a T: before your given title to distinguish the action as Import. |
Navigate through the remaining tabs of the Import wizard. For more information on the import options, see Importing Record Data . Note that you cannot import data from a local hard drive with an Import action.
In addition to importing content from outside your system, Import actions can also be used with special format fields in the same KB. For example, some AI models generate JSON output for debugging purposes, and some third-party API integrations use JSON formatting to send data. You can use an Import action to parse the content into other fields so it becomes usable in .
To create an Import action for internal fields:
On the General tab, name your action and give it a description.
Once your action is saved, the system automatically adds a T: before your given title to distinguish the action as Import. |
On the Data Source tab, select "Text field in the current table" and choose the field from the drop-down menu. This menu lists fields whose format is text, XML, or JSON.
The wizard for Export actions is very similar to the Export wizard for manual, one-time exports.
To create an Export action:
On the General tab, name your action and give it a description.
Once your action is saved, the system automatically adds an X: before your given title to distinguish the action as Export. |
Complete the Destination and Data Format tabs as desired. You cannot export data to a local hard drive with an Export action.
Complete the Options tab. For more information on available export options, see Exporting Record Data. Two additional options not included in the Export wizard for manual, one-time exports are also available:
Filename: Defines the name of the export file. Two options are available when defining the filename:
Overwrite the file: Overwrites the existing export file with the new export file.
Add Date and Time to new file: Appends the current date and time to the export filename, and any existing export files are not overwritten. If you select this option, you must include the default $date
and $time
variables at the end of the filename, such as $label_export_$date$time
. Otherwise, any existing export files will be overwritten and the date and time will not be appended to the filename.
Email log file to: Defines email addresses to receive the log file that's generated when the Export action runs. You can choose to send the log file in the body of the email or as an attachment. If the field is left blank, the log file is not sent.
Related articlesRelated articles appear here based on the labels you select. Click to edit the macro and add or change labels. |