Registry / devops / leadconduit-migration-tool

leadconduit-migration-tool

library0.1.0jsnpmunverified

A command-line tool for migrating LeadConduit flows that use the deprecated WhitePages `address_validation` endpoint to the new `global_address_validation` endpoint. Version 0.1.0, initial release. It scans an account for flows using the old endpoint and interactively updates integration steps, mappings, and rules. The tool writes before/after JSON snapshots but does not deploy flows; deployment must be done separately. Designed for one-time migration rather than ongoing use.

devops

npm install leadconduit-migration-tool

package ↗

INSTALL

IMPORT

SIG · LEADCONDUIT-MIGRAT

leadconduit-migration-tool

devopsjavascriptv0.1.0

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Shows how to set the API key environment variable and run the migration tool. It uses the staging URL by default.

#!/usr/bin/env bash # Set API key for staging export AP_STAGING='your-actual-api-key-here' # Run without arguments; will prompt for each flow node bin/migrate.js

Debug

Known issues

gotchaTool does not deploy updated flows. You must deploy them separately via API or UI after migration.

fix

After running migration, deploy each flow using the LeadConduit API or UI.

affects: >=0.1

deprecatedThis tool is hardcoded to migrate from WhitePages address_validation to global_address_validation. It will not handle other endpoint migrations.

fix

This is a one-time migration tool; for other endpoints, use a different tool or manual updates.

affects: >=0.1

gotchaThe tool prompts for confirmation for each flow found. Running in a non-interactive environment (e.g., CI) will hang.

fix

Run in an interactive terminal, or modify the script to accept a 'yes' flag.

affects: >=0.1

gotchaThe script uses a hardcoded staging URL by default. To run against production, you must manually edit the script.

fix

Change the value of `getUrl` in the script to use the production endpoint (e.g., https://X:${AP_STAGING}@next.leadconduit.com/flows).

affects: >=0.1

Errors

Common errors & fixes

'addEventListener' is not a function

The script expects a browser-like environment but runs in Node.js.

fix

This is not a typical error for this tool; ensure you are using Node.js and not running in a browser.

Cannot find module '../lib/migrate'

Running the tool from the wrong directory or missing dependencies.

fix

Run the tool from the project root directory, or ensure you have installed the package (npm install leadconduit-migration-tool).

Error: getaddrinfo ENOTFOUND next.leadconduit.com

The production URL domain is not reachable (e.g., VPN, DNS issue).

fix

Check network connectivity and ensure you can resolve 'next.leadconduit.com'. Use staging URL if appropriate.

Upgrade

Version history

0.1.0latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

5 hits · last 30 days

node

Amazon

Resources

packageleadconduit-migration-tool ↗