Help
Common Problems
Fast fixes for the most common sign-in, data, sync, and docs issues in Salesprompter.
Use this page when something fails and you want the quickest recovery path.
Auth issues
not logged in. Run salesprompter auth:login.
Cause:
- no local session file exists in the configured config directory
Fix:
node ./dist/cli.js auth:login
node ./dist/cli.js auth:whoami --verify
If you intentionally use a non-default config directory, verify SALESPROMPTER_CONFIG_DIR.
session expired. Run salesprompter auth:login.
Cause:
- the stored
expiresAtis now in the past
Fix:
node ./dist/cli.js auth:login
Device login is not configured on this Salesprompter app
Cause:
- the backend does not expose working device auth endpoints
Fix:
- issue a CLI token from the app
- run:
node ./dist/cli.js auth:login --token "<token-from-app>"
CLI setup issues
node: command not found or npm: command not found
Cause:
- Node.js is not installed or not on
PATH
Fix:
- install a current Node.js release
- confirm with:
node --version
npm --version
The CLI builds but a command is missing
Cause:
- the local build is stale
Fix:
- rebuild the CLI:
npm install
npm run build
node ./dist/cli.js --help
Instantly issues
Instantly campaign id is required
Fix:
- pass
--campaign-id - or set
INSTANTLY_CAMPAIGN_ID
Instantly API key is required
Fix:
- set
INSTANTLY_API_KEY
A dry run succeeded but no leads were created
Cause:
- dry run is the default behavior
Fix:
- rerun with
--applyonly after reviewing the target campaign and payload
Fewer leads synced than expected
Likely cause:
- dedupe skipped emails already present in the campaign
Fix:
- inspect the reported
skippedcount - use
--allow-duplicatesonly if duplicates are intentional
Lead workflow issues
Lead generation returns fewer results than expected
Common causes:
- the ICP is too narrow
- the target account is too specific
- required signals remove most matches
Fix:
- loosen the ICP slightly
- reduce the number of required filters
- test with a smaller set of countries, titles, or company sizes
Enrichment or scoring output is mostly fallback
Cause:
- the default provider implementation is returning heuristic output
Fix:
- inspect the generated files before using them downstream
- treat
fallbackoutput as a draft for review, not as verified data
Sync issues
The sync preview looks correct but nothing changed downstream
Cause:
- sync commands default to dry-run in the safe path
Fix:
node ./dist/cli.js sync:outreach --target instantly --in ./data/scored.json --campaign-id "$INSTANTLY_CAMPAIGN_ID"
Review the payload, then rerun with --apply when you are ready.
Docs issues
A docs page moved or no longer exists
Cause:
- the public docs were simplified to remove internal implementation material
Fix:
- start from the public docs home
- use Quickstart or Find and Qualify Leads
- contact support if you need help with a custom setup