SmartConnector Export, Import, and Duplication
Audience: Administrators, Developers, Integrators, Solution Architects
Purpose: Explains how to export, import, and duplicate SmartConnectors, what each action includes, and why imported and duplicated SmartConnectors must be reviewed before activation.
Overview
There are three ways to move or copy a SmartConnector: export, import, and duplication. Use export and import together to either move a SmartConnector across environments, or share with another business. Use duplication to make a copy of a SmartConnector within the same business, usually when you want to modify it before activating it.
Each mechanism includes a different set of SmartConnector configuration, and each has specific behaviors that affect what you need to review before the new or copied SmartConnector can process data.
Export
Exporting a SmartConnector packages its configuration into a downloadable file that can be imported into another business.
An export includes:
The SmartConnector name
The Live SQL script
The reference data file
Caution: The Sample File is packaged inside the exported file and will be accessible to anyone who receives it. Before exporting a SmartConnector that will be shared outside your business, review the Sample File and remove any sensitive or business-specific data.
Import
Importing a SmartConnector creates it in the target business from an exported package. The SmartConnector is created as-is. You cannot edit it during import, so make any changes after it is created.
What is created
The exported package contains only the Live SQL script. On import, it becomes the new Live script, and a Draft script is created from it.
If a SmartConnector with the same name already exists in the target business, the import is skipped. Delete or rename the existing one first if you need to re-import.
What happens during import
After the SmartConnector is created, pre-activation checks run automatically. There are three possible outcomes:
All checks pass: The status is set to Operational.
Warnings are detected: The import succeeds, but some references need manual review. The status is set to Operational (Needs Attention), and the warnings are listed in the import confirmation email. There is no in-app warning indicator, so check the email before activating.
Other errors are detected: The import fails.
Warnings apply to these reference types:
Agentic Workflow references
Filter group for seeding
Matching or mapping field references
What to do after import
The active toggle is always off on import, so a newly imported SmartConnector will not process data until you turn it on. Before activating:
Review the import confirmation email.
Open the SmartConnector and confirm that the flagged references resolve correctly.
Verify the configuration matches what you expect.
Turn on the active toggle.
Caution: The Operational (Needs Attention) status tracks the most recent live run, not whether import warnings were resolved. If you run the SmartConnector before fixing the warnings and the run succeeds, the status changes to Operational even though the warnings still exist. Always resolve warnings from the import email before relying on status.
Duplication
Duplicating a SmartConnector creates a copy within the same business. Duplication is intended for users who have edit permissions on the original SmartConnector and plan to modify the copy before activating it.
A duplicated SmartConnectorr includes:
All configuration from the original
Both the Live SQL script and the Draft SQL script
The Sample File
Agentic Workflow references
The following are updated on the duplicate:
Name
API name
Owner: set to the user who performed the duplication
The key difference between duplication and import is scope. Duplication includes both the Live and Draft SQL scripts and is designed for a user who will continue editing the SmartConnector before going live. Import includes only the Live SQL and regenerates the draft, because the imported SmartConnector is expected to be reviewed and activated rather than edited further.
Caution: The active toggle is always disabled on the duplicated SmartConnector. Review the duplicate, make any required changes, and activate it manually when you are ready for it to process data.
What's Next
Continue to SmartConnector Data Model to learn how SmartConnectors, executions, and output are represented as data model entities within the platform.
Last updated
Was this helpful?