When you import or export workflows or customer lists, some nodes do not include the underlying information.
|Import or Export|
Rule or data source
You must create a new rule or data source and assign it to the node.
|API or SFTP||You must create a new API or SFTP data integration and assign it to the relevant node.|
|Nodes that include database, API, or SFTP connection information||
When you export workflows or customer lists, for security reasons, the system does not include connection authentication information (such as usernames or passwords).
When you import a workflow or customer list, you must edit the connection to add the required authentication information.
Workflow Run History or Customer List Run History and Schedule settings are not included. You must create a new schedule for each exported or imported workflow or customer list.
Action Taken When Workflow or Customer List with Identical Name is Imported
- A sub-workflow or sub-customer list in a parent workflow or parent customer list has an identical name to one already in the system. The sub-workflow or sub-customer list will not be imported; the parent workflow or parent customer list will be imported using the existing sub-workflow or sub-customer list.
- An SQL node in a workflow or customer list has an identical database connection name to one already in the system. The database connection will not be imported; the workflow or customer list will be imported using the existing database connection name for the SQL node.