Skip to main content

Export & Import

The Export & Import feature lets you save your connector's test configuration to a JSON file and restore it later, or import configuration from a Postman Collection.

Exporting Configuration​

What Gets Exported​

A full export includes:

  • Endpoints: Enabled/disabled status and configuration
  • Dependency mappings: All source-to-target data flows
  • Reusable variables: Standard, paired, and merged variables
  • Pagination configs: Per-endpoint pagination settings
  • Body configs: Request body configurations
  • Execution order: Custom endpoint ordering
  • Connector metadata: Name, ID, export timestamp

How to Export​

  1. Click the Export/Import button in the toolbar
  2. Switch to the Export tab
  3. Review the summary showing counts of each item type
  4. Click Download JSON
  5. A file is saved with the connector name and timestamp

Export File Format​

The exported file is a JSON document:

{
  "connectorId": "uuid",
  "connectorName": "Platform Name",
  "exportedAt": "2025-01-15T10:30:00Z",
  "endpoints": [...],
  "dependencyMappings": [...],
  "reusableVariables": [...],
  "paginationConfigs": {...},
  "bodyConfigs": {...},
  "executionOrder": [...]
}

Importing Configuration​

Supported Formats​

FormatDescription
Traces exportJSON previously exported from Traces
Postman CollectionPostman Collection v2.1 format

How to Import​

  1. Click the Export/Import button
  2. Switch to the Import tab
  3. Click to select a file or drag and drop
  4. The system parses and validates the file
  5. Review the diff preview before applying

Diff Preview​

Before applying, you see a detailed breakdown of changes organized into expandable sections:

  • Endpoints: Added, modified, or removed configurations
  • Dependency Mappings: New, changed, or removed data flows
  • Variables: Added, modified, or removed variables
  • Execution Order: Whether the endpoint order will change

Each section shows a change count badge and can be expanded for details.

Applying Changes​

  1. Review all sections of the diff
  2. Note any warnings (see below)
  3. Click Apply Changes
  4. Configuration is replaced with imported data
  5. Test results and samples are preserved
warning

Import replaces your current configuration. It does not merge — existing mappings and variables are removed and replaced with the imported ones. Test results and samples are not affected.

Cross-Connector Import​

When importing from a different connector (different connector ID):

Endpoint Matching​

Endpoints are matched by method + path (not by ID):

  • GET /users in the import matches GET /users in the current connector
  • If an imported endpoint doesn't match any current endpoint, it's listed as unmapped and its mappings are skipped

Warnings​

The import preview shows warnings for:

  • Different connector ID: Amber warning that endpoints are matched by path
  • Unmapped endpoints: Count of imported endpoints not found in the current connector
  • Skipped mappings: Mappings that reference unmapped endpoints

ID Remapping​

All internal ID references (endpoint IDs, variable IDs) are automatically remapped to match the current connector's IDs. This happens transparently — you don't need to manually adjust anything.

Postman Collection Import​

Supported Features​

When importing from a Postman Collection v2.1:

  • Endpoint paths and methods are extracted
  • Request headers, query parameters, and body configurations are imported
  • Variables are mapped where possible

Limitations​

Postman collections don't include Traces-specific features:

  • No dependency mappings (must be configured manually)
  • No pagination configs
  • No reusable variables
  • No execution order

Workflow​

  1. Export your Postman collection as JSON (Collection v2.1)
  2. Import into Traces
  3. Review matched endpoints
  4. Manually configure dependencies, pagination, and variables

Use Cases​

Migrating Configuration Between Versions​

After publishing creates a new connector:

  1. Export config from the current version
  2. If the new version has the same endpoints, import carries over cleanly
  3. Review diff for any endpoint path changes

Sharing Configuration​

Share connector configuration between team members:

  1. One analyst exports their tested configuration
  2. Another analyst imports it into their instance
  3. Both work from the same baseline

Backup Before Major Changes​

Before making significant configuration changes:

  1. Export current config as a backup
  2. Make changes and test
  3. If changes don't work, import the backup to restore

Importing from Postman Workflows​

If you've already tested an API in Postman:

  1. Export the Postman collection
  2. Import into Traces to bootstrap endpoint configuration
  3. Add Traces-specific features (dependencies, variables, pagination)

Troubleshooting​

"Import error: invalid format"​

  • Verify the file is valid JSON
  • Check it's a Traces export or Postman Collection v2.1 format
  • The file may be corrupted — try exporting again

"Many unmapped endpoints"​

  • Endpoint paths may have changed between connector versions
  • Check for path differences (e.g., /api/v1/users vs /api/v2/users)
  • Unmapped endpoints' configurations are silently skipped

"No changes detected"​

  • The imported config matches the current config exactly
  • The Apply Changes button is disabled when there are no changes