Skip to main content
Development checkout only: preview and reconcile selected backlink opportunities and sourced outreach outcomes while preserving existing CRM files.

​
Usage

​
Options

  • Every data operation requires --out FILE for a new private plan or receipt. Plan uses --source FILE, --hosted FILE, --project-id ID and optional --field-map FILE/--format json|csv. Apply uses --plan FILE and --source FILE. Rollback uses --receipt FILE and refuses changed records. Outcome planning also requires --bindings FILE, --mapping FILE, --provider hunter|lemlist|instantly|manual|agent and --account-ref OPAQUE. Read campaign --help for each exact command. Inputs are regular files of at most 64 MiB
  • plans preserve source hashes.

​
Exit status

0 for a completed result; 2 when any result row is held, including in a dry-run plan, or for usage, configuration, input or request failure. Read every row result before accepting the batch.
The published agentlinkops 0.6.13 package does not include this file helper. Use it from a reviewed development checkout with node cli/agentlinkops.mjs campaign --help.Hosted prospect and outcome commands are available separately through MCP, generic CLI call, or HTTP. Start with a frozen source export, a complete selected hosted snapshot and an explicit stable-reference field map.Review the plan counts and conflicts, then apply and reconcile by original references and receipts. Applying a prospect saves it without checks.Pull-apply writes back only independently observed link outcomes through a private backup and compare-and-set. Sender accounts, sequences and messages stay in the existing sending tools.
Read configuration and file ownership for environment variables, compatibility aliases and writer locks. Read local file contracts for artifact fields. Browse the CLI index for related commands.
Check the selected environment and workspace access before calling hosted operations. See capability status.