Automation Rules for import and export

Running import and export by Automation Rules

CSV import and export can be triggered by the Automation Rule (AR). In order to run import or export by the Automation Rule the profile must be created first. (Settings>>Integrations). The Automation Rules option is found in Settings>>Automation Rules on the left navigation in the connection section. Note: you need Admin rights to access both sections.

1. Create a valid and complete import or export profile and copy its ID - it could be found at the top of the profile details page

2. Having a profile created and enabled, go Settings >> Automation Rules and click Create new rule

3. Choose the trigger for this rule (WHEN) from the dropdown list and other conditions if needed (+ AND)

4. In the field + THEN select Other

• for import (use the profile ID you copied and want to run)

    {  
      "type": "action:csv-import:run",  
      "profileId": "2cc80dbf-acac-4736-8ddb-850c45056b33"  
     }
  

• for export (use the profile ID you copied and want to run)

    {  
     "type": "action:csv-export:run",  
     "profileId": "a6a56fa9-4b4e-49a4-be9d-7a0f8ec9a409"  
    }
  

5. Save the automation rule. As soon as it's triggered, the profile will run once.

NOTES AND RECOMMENDATIONS:

1. Only an enabled profile can be run by Automation Rules
2. If an import profile run is attempted to be triggered by an AR while it's already running, such attempt will be ignored
3. It's recommended to assess the duration and impact of a profile run before automating its execution
4. Local Export profile can't be automated - such AR will fail
5. There is no mechanism to restrict the import source or the export destination changes - make sure the profile under automation stays untouched
6. Currently there is no mechanism to trigger AR by the dataset changes or any other events in ADM
7. While import profiles' runs are put to queue if there are too many intentions, the export profile runs have no such queueing mechanism

Running Automation Rules when import or export is completed

To perform additional actions once the import or export has been completed the Automation Rule triggered by this event can be created. To integrate with triggers from import/export following json when the condition listed below should be specified:

• for import

{  
    "type": "source:generic",  
    "clientId": "csv-import",  
    "payloadType": "csv-import"  
  }

• for export

 {  
  "type": "source:generic",  
  "clientId": "csv-export",  
  "payloadType": "csv-export"  
 }

Also the following javascript condition with the proper profileID should be added:

return args.palyload.profileId = '[id_of_the_profile]'