Skip to main content

Exporting and importing Action Flows

You can export Action Flows and their dependencies from a single package using the command-line interface. Exported dependencies include webhooks, data structures, variables and other. Webhooks and connections are exported as metadata references and can not be imported as-is to the target team.

Exporting Action Flows

To export Action Flows from a package, in your command line interface, run:

content-cli export action-flows -p my-profile-name --packageId <replace-with-package-id> -f <replace-with-metadata-file-name>content-cli analyze action-flows -p my-profile-name --packageId <replace-with-package-id> --outputToJsonFile

  • The -f flag is optional but recommended if you plan to use the ZIP package to import it to a target package. If specified, it will attach the metadata file to the exported ZIP package. This file is expected to be received by the action-flows import command, and manually be populated with the mappings source to target package.

Importing Action Flows

To import previously exported Action Flows from a single package, together with their dependencies, from the command-line interface, run:

content-cli import action-flows -p my-profile-name --packageId <replace-with-package-id> -f <replace-with-exported-zip-file> --dryRun false --outputToJsonFile

  • The zip file is the one that you receive from the action-flows export command, and it includes the JSON metadata.

  • The --dryRun is mandatory boolean true/false. If specified, the import will be executed in a dry run mode where no real import

  • The --outputToJsonFile is optional. If specified, the import result is saved in a JSON file. The command output will give you all the details.