autotouch-cli 0.2.103__tar.gz → 0.2.104__tar.gz

{autotouch_cli-0.2.103 → autotouch_cli-0.2.104}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.103
+Version: 0.2.104
 Summary: Autotouch Smart Table CLI
 Project-URL: Homepage, https://app.autotouch.ai
 Project-URL: Documentation, https://github.com/nicolonic/autotouch_main/tree/main/docs/research-table/reference
@@ -34,6 +34,19 @@ The CLI talks to the same API the product uses. For automation, prefer `--output
 For a machine-readable local command contract, use `autotouch cli-manifest --output json`.
 For a shipped human-readable reference generated from the installed parser, use `autotouch cli-reference`.
 
+## Product Model
+
+Autotouch helps GTM teams source records, land them in Smart Table, research and operate on those rows, then turn qualified accounts/leads into outreach actions.
+
+Use the lifecycle to choose commands:
+
+1. Source Records: use `autotouch list-build`, `autotouch search`, `autotouch agents`, imports, or webhooks.
+2. Land In Smart Table: use `autotouch list-build sync-to-table`, `autotouch tables`, `autotouch rows`, or import/webhook ingest.
+3. Research And Operate: use `autotouch columns recipe`, `autotouch columns run-next`, `autotouch jobs`, `autotouch rows`, and `autotouch cells`.
+4. Engage: use `to_leads`, `to_sequence`, `to_outreach`, `to_crm`, `autotouch sequences`, and `autotouch tasks`.
+
+Smart Table is the operating layer. Most workflows should land records there before enrichment, dedupe, routing, or engagement. Run `autotouch workflows list --output json` for lifecycle-grouped plans.
+
 ## Install
 
 Released package:
@@ -180,7 +193,7 @@ Use `autotouch search similar-companies` as a convenience wrapper for Exa Compan
 
 Use `autotouch search people` for provider-hidden people search when the target is niche, semantic, or hard to express with structured filters. People search currently returns at most 10 results per API call and costs 1 credit per API call.
 
-Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable LinkedIn/Sales Navigator list construction. This is the only CLI path for building LinkedIn-sourced company and lead lists. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, add the records to a research table, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This path uses Autotouch-managed provider access, so users do not need to connect their own LinkedIn account. Use filters like geography IDs, company size, industry IDs, title/persona, and current company IDs; call `autotouch list-build inputs` for supported values. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
+Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable LinkedIn/Sales Navigator list construction. This is the only CLI path for building LinkedIn-sourced company and lead lists. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, sync the records to a research table with `autotouch list-build sync-to-table`, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This path uses Autotouch-managed provider access, so users do not need to connect their own LinkedIn account. Use filters like geography IDs, company size, industry IDs, title/persona, and current company IDs; call `autotouch list-build inputs` for supported values. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
 
 LinkedIn is an optional campaign channel, not the default for every outbound workflow. Use it when the user explicitly wants LinkedIn-sourced lists, profile visits, connection requests, or LinkedIn follow-up tasks. Prefer email/call/custom sequences or research-table workflows when LinkedIn would unnecessarily constrain output because of provider limits, cooldowns, missing profile URLs, or campaign fit.
 
@@ -203,7 +216,7 @@ discover -> plan -> scaffold -> run primitives -> inspect
 - `autotouch workflows scaffold --type <TYPE> --out-dir <DIR>` writes payload files and a command runbook.
 - `autotouch columns recipe` and `autotouch sequences recipe` remain leaf-level templates.
 
-Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
+Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `agent-to-leads`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
 
 ## Sources And Destinations
 
@@ -273,16 +286,17 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.103` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` workflow scaffold, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, website visitor/external intent webhook workflow guidance, and create-time agent assignment defaults
+- `autotouch --version` should be `0.2.104` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` and `agent-to-leads` workflow scaffolds, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, website visitor/external intent webhook workflow guidance, create-time agent assignment defaults, and company-page signal configuration guidance
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch integrations list` and `autotouch integrations status --provider <provider>` before choosing source/destination workflows
 - `autotouch workflows plan --type bulk-outreach` and `autotouch workflows scaffold --type bulk-outreach --out-dir workflow` for goal-level workflow planning
+- `autotouch workflows plan --type agent-to-leads` and `autotouch workflows scaffold --type agent-to-leads --out-dir workflow` for scheduled agent discovery into qualified Autotouch Leads without sequence tasks
 - `autotouch workflows plan --type agent-to-sequence` and `autotouch workflows scaffold --type agent-to-sequence --out-dir workflow` for scheduled agent discovery into Autotouch Sequence tasks
 - `autotouch workflows plan --type website-visitors` and `autotouch workflows scaffold --type website-visitors --out-dir workflow` for website visitor or external intent provider webhook workflows
 - `autotouch integrations recipe --type from_crm --provider hubspot` for CRM-to-research-table imports
 - `autotouch columns recipe --type to_crm|to_outreach|to_leads|to_sequence` for research-table destination workflows
 - `autotouch list-build inputs` and `autotouch list-build pricing` before creating durable list-build jobs
-- `autotouch list-build companies` and `autotouch list-build leads` for durable LinkedIn-sourced company and lead list builds with Smart Table-owned background workers, visible progress, and no user-owned LinkedIn connection requirement
+- `autotouch list-build companies`, `autotouch list-build leads`, and `autotouch list-build sync-to-table` for durable LinkedIn-sourced company/lead list builds and the first-class Smart Table handoff
 - `autotouch linkedin status` and `autotouch linkedin limits` for connected-account diagnostics
 - `autotouch sequences recipe --type linkedin_outreach` only when the campaign should include LinkedIn touches; the emitted branch waits for connection acceptance before LinkedIn chat and uses email fallback after the wait window
 - `autotouch rows list` / `autotouch rows get` / `autotouch cells get` for read-back and audit

{autotouch_cli-0.2.103 → autotouch_cli-0.2.104}/README.md

@@ -9,6 +9,19 @@ The CLI talks to the same API the product uses. For automation, prefer `--output
 For a machine-readable local command contract, use `autotouch cli-manifest --output json`.
 For a shipped human-readable reference generated from the installed parser, use `autotouch cli-reference`.
 
+## Product Model
+
+Autotouch helps GTM teams source records, land them in Smart Table, research and operate on those rows, then turn qualified accounts/leads into outreach actions.
+
+Use the lifecycle to choose commands:
+
+1. Source Records: use `autotouch list-build`, `autotouch search`, `autotouch agents`, imports, or webhooks.
+2. Land In Smart Table: use `autotouch list-build sync-to-table`, `autotouch tables`, `autotouch rows`, or import/webhook ingest.
+3. Research And Operate: use `autotouch columns recipe`, `autotouch columns run-next`, `autotouch jobs`, `autotouch rows`, and `autotouch cells`.
+4. Engage: use `to_leads`, `to_sequence`, `to_outreach`, `to_crm`, `autotouch sequences`, and `autotouch tasks`.
+
+Smart Table is the operating layer. Most workflows should land records there before enrichment, dedupe, routing, or engagement. Run `autotouch workflows list --output json` for lifecycle-grouped plans.
+
 ## Install
 
 Released package:
@@ -155,7 +168,7 @@ Use `autotouch search similar-companies` as a convenience wrapper for Exa Compan
 
 Use `autotouch search people` for provider-hidden people search when the target is niche, semantic, or hard to express with structured filters. People search currently returns at most 10 results per API call and costs 1 credit per API call.
 
-Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable LinkedIn/Sales Navigator list construction. This is the only CLI path for building LinkedIn-sourced company and lead lists. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, add the records to a research table, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This path uses Autotouch-managed provider access, so users do not need to connect their own LinkedIn account. Use filters like geography IDs, company size, industry IDs, title/persona, and current company IDs; call `autotouch list-build inputs` for supported values. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
+Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable LinkedIn/Sales Navigator list construction. This is the only CLI path for building LinkedIn-sourced company and lead lists. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, sync the records to a research table with `autotouch list-build sync-to-table`, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This path uses Autotouch-managed provider access, so users do not need to connect their own LinkedIn account. Use filters like geography IDs, company size, industry IDs, title/persona, and current company IDs; call `autotouch list-build inputs` for supported values. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
 
 LinkedIn is an optional campaign channel, not the default for every outbound workflow. Use it when the user explicitly wants LinkedIn-sourced lists, profile visits, connection requests, or LinkedIn follow-up tasks. Prefer email/call/custom sequences or research-table workflows when LinkedIn would unnecessarily constrain output because of provider limits, cooldowns, missing profile URLs, or campaign fit.
 
@@ -178,7 +191,7 @@ discover -> plan -> scaffold -> run primitives -> inspect
 - `autotouch workflows scaffold --type <TYPE> --out-dir <DIR>` writes payload files and a command runbook.
 - `autotouch columns recipe` and `autotouch sequences recipe` remain leaf-level templates.
 
-Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
+Goal-level workflow types include `bulk-outreach`, `company-table-to-people`, `table-to-outreach`, `research-to-sequence`, `agent-to-sequence`, `agent-to-leads`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, scheduled agents, webhooks, visitor sources, and external intent sources as sources/destinations inside one organized workflow layer instead of creating one-off top-level commands.
 
 ## Sources And Destinations
 
@@ -248,16 +261,17 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.103` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` workflow scaffold, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, website visitor/external intent webhook workflow guidance, and create-time agent assignment defaults
+- `autotouch --version` should be `0.2.104` or newer for structured company list builds without user-supplied keywords, stored list-build input lookup, research-workspace list-build guidance, the cleaned single LinkedIn-sourced list-build path, Exa Company Search up to 100 results, scheduled agent `--target ACCOUNTS|LEADS`, `agents signals --target`, the `agent-to-sequence` and `agent-to-leads` workflow scaffolds, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee and active-sequence-conflict guard config, backend-owned directional source/destination helpers, goal-level workflow plans, website visitor/external intent webhook workflow guidance, create-time agent assignment defaults, and company-page signal configuration guidance
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch integrations list` and `autotouch integrations status --provider <provider>` before choosing source/destination workflows
 - `autotouch workflows plan --type bulk-outreach` and `autotouch workflows scaffold --type bulk-outreach --out-dir workflow` for goal-level workflow planning
+- `autotouch workflows plan --type agent-to-leads` and `autotouch workflows scaffold --type agent-to-leads --out-dir workflow` for scheduled agent discovery into qualified Autotouch Leads without sequence tasks
 - `autotouch workflows plan --type agent-to-sequence` and `autotouch workflows scaffold --type agent-to-sequence --out-dir workflow` for scheduled agent discovery into Autotouch Sequence tasks
 - `autotouch workflows plan --type website-visitors` and `autotouch workflows scaffold --type website-visitors --out-dir workflow` for website visitor or external intent provider webhook workflows
 - `autotouch integrations recipe --type from_crm --provider hubspot` for CRM-to-research-table imports
 - `autotouch columns recipe --type to_crm|to_outreach|to_leads|to_sequence` for research-table destination workflows
 - `autotouch list-build inputs` and `autotouch list-build pricing` before creating durable list-build jobs
-- `autotouch list-build companies` and `autotouch list-build leads` for durable LinkedIn-sourced company and lead list builds with Smart Table-owned background workers, visible progress, and no user-owned LinkedIn connection requirement
+- `autotouch list-build companies`, `autotouch list-build leads`, and `autotouch list-build sync-to-table` for durable LinkedIn-sourced company/lead list builds and the first-class Smart Table handoff
 - `autotouch linkedin status` and `autotouch linkedin limits` for connected-account diagnostics
 - `autotouch sequences recipe --type linkedin_outreach` only when the campaign should include LinkedIn touches; the emitted branch waits for connection acceptance before LinkedIn chat and uses email fallback after the wait window
 - `autotouch rows list` / `autotouch rows get` / `autotouch cells get` for read-back and audit

{autotouch_cli-0.2.103 → autotouch_cli-0.2.104}/autotouch_cli/cli.py

@@ -119,6 +119,7 @@ from autotouch_cli.commands.list_build import (
     cmd_list_build_pricing as cmd_list_build_pricing_impl,
     cmd_list_build_results as cmd_list_build_results_impl,
     cmd_list_build_status as cmd_list_build_status_impl,
+    cmd_list_build_sync_to_table as cmd_list_build_sync_to_table_impl,
 )
 from autotouch_cli.commands.rows import (
     RowCommandRuntime as RowCommandHandlerRuntime,
@@ -376,6 +377,7 @@ from autotouch_shared.list_build_contract import (
     list_build_capabilities_contract,
     list_build_endpoint_entries,
 )
+from autotouch_shared.product_lifecycle import product_lifecycle_contract
 from autotouch_cli.exceptions import (
     AutotouchAPIError,
     AutotouchInputError,
@@ -1608,6 +1610,7 @@ _register("list_build_companies", cmd_list_build_companies_impl, _list_build_com
 _register("list_build_leads", cmd_list_build_leads_impl, _list_build_command_runtime)
 _register("list_build_status", cmd_list_build_status_impl, _list_build_command_runtime)
 _register("list_build_results", cmd_list_build_results_impl, _list_build_command_runtime)
+_register("list_build_sync_to_table", cmd_list_build_sync_to_table_impl, _list_build_command_runtime)
 _register("list_build_inputs", cmd_list_build_inputs_impl, _list_build_command_runtime)
 _register("list_build_pricing", cmd_list_build_pricing_impl, _list_build_command_runtime)
 
@@ -1954,7 +1957,7 @@ def cmd_context_resolved(args: argparse.Namespace) -> None:
     _print_json(data, compact=args.compact)
 
 
-def _with_bundled_linkedin_capabilities(data: Any) -> Any:
+def _with_bundled_capabilities(data: Any) -> Any:
     if not isinstance(data, dict):
         return data
     merged = dict(data)
@@ -1962,6 +1965,7 @@ def _with_bundled_linkedin_capabilities(data: Any) -> Any:
     merged["endpoints"] = {**endpoints, **linkedin_endpoint_entries(), **list_build_endpoint_entries()}
     merged["linkedin"] = linkedin_capabilities_contract()
     merged["list_builds"] = list_build_capabilities_contract()
+    merged["product_lifecycle"] = product_lifecycle_contract()
     return merged
 
 
@@ -1976,7 +1980,7 @@ def cmd_capabilities(args: argparse.Namespace) -> None:
         timeout=args.timeout,
         verbose=args.verbose,
     )
-    data = _with_bundled_linkedin_capabilities(data)
+    data = _with_bundled_capabilities(data)
     if OUTPUT_MODE == "human" and isinstance(data, dict):
         execution = data.get("execution_policies") if isinstance(data.get("execution_policies"), dict) else {}
         llm = execution.get("llm") if isinstance(execution.get("llm"), dict) else {}
@@ -1994,6 +1998,25 @@ def cmd_capabilities(args: argparse.Namespace) -> None:
         if isinstance(scopes, list):
             print(f"Scopes      : {', '.join(str(s) for s in scopes)}")
 
+        lifecycle = data.get("product_lifecycle") if isinstance(data.get("product_lifecycle"), dict) else {}
+        stages = lifecycle.get("stages") if isinstance(lifecycle.get("stages"), list) else []
+        if lifecycle:
+            print("")
+            print("Product lifecycle")
+            print("-----------------")
+            summary = lifecycle.get("product_summary")
+            if summary:
+                print(str(summary))
+            principle = lifecycle.get("operating_principle")
+            if principle:
+                print(str(principle))
+            if stages:
+                print("Stages:")
+                for stage in stages:
+                    if not isinstance(stage, dict):
+                        continue
+                    print(f"  - {stage.get('label', stage.get('key', 'stage'))}: {stage.get('description', '')}")
+
         print("")
         print("LLM output modes")
         print("----------------")

{autotouch_cli-0.2.103 → autotouch_cli-0.2.104}/autotouch_cli/commands/list_build.py

@@ -86,6 +86,26 @@ def _wait(job_id: str, args: argparse.Namespace, *, runtime: ListBuildCommandRun
         time.sleep(max(1, int(getattr(args, "poll_interval", 5) or 5)))
 
 
+def _wait_sync(sync_job_id: str, args: argparse.Namespace, *, runtime: ListBuildCommandRuntime, token: Optional[str]) -> Any:
+    started = time.time()
+    while True:
+        data = runtime.request_api(
+            "GET",
+            f"/api/list-builds/sync-jobs/{sync_job_id}",
+            base_url=args.base_url,
+            token=token,
+            use_x_api_key=args.use_x_api_key,
+            timeout=args.timeout,
+            verbose=args.verbose,
+        )
+        if str(data.get("status") or "").lower() in {"completed", "error", "cancelled"}:
+            return data
+        timeout = int(getattr(args, "wait_timeout", 0) or 0)
+        if timeout and time.time() - started >= timeout:
+            raise AutotouchTimeoutError(f"Timed out waiting for list-build sync {sync_job_id}")
+        time.sleep(max(1, int(getattr(args, "poll_interval", 5) or 5)))
+
+
 def _create(args: argparse.Namespace, *, runtime: ListBuildCommandRuntime, kind: str) -> None:
     token = runtime.resolve_token(args.token, required=True)
     data = runtime.request_api(
@@ -103,6 +123,34 @@ def _create(args: argparse.Namespace, *, runtime: ListBuildCommandRuntime, kind:
     runtime.print_json(data, args.compact)
 
 
+def cmd_list_build_sync_to_table(args: argparse.Namespace, *, runtime: ListBuildCommandRuntime) -> None:
+    token = runtime.resolve_token(args.token, required=True)
+    payload: Dict[str, Any] = {
+        "identity_key": args.identity_key,
+        "dedupe_mode": args.dedupe_mode,
+        "merge_mode": args.merge_mode,
+    }
+    for attr in ("type", "table_id", "table_name", "table_mode"):
+        value = getattr(args, attr, None)
+        if value:
+            payload[attr] = value
+    if getattr(args, "allow_partial", False):
+        payload["allow_partial"] = True
+    data = runtime.request_api(
+        "POST",
+        f"/api/list-builds/{args.job_id}/sync-to-table",
+        base_url=args.base_url,
+        token=token,
+        use_x_api_key=args.use_x_api_key,
+        payload=payload,
+        timeout=args.timeout,
+        verbose=args.verbose,
+    )
+    if getattr(args, "wait", False) and data.get("sync_job_id"):
+        data = _wait_sync(str(data["sync_job_id"]), args, runtime=runtime, token=token)
+    runtime.print_json(data, args.compact)
+
+
 def cmd_list_build_companies(args: argparse.Namespace, *, runtime: ListBuildCommandRuntime) -> None:
     _create(args, runtime=runtime, kind="companies")
 
@@ -253,6 +301,26 @@ def register_list_build_subcommands(
     add_api_common_arguments(results)
     results.set_defaults(func=handlers["results"])
 
+    sync = sub.add_parser("sync-to-table", help="Sync list-build results into a Smart Table")
+    sync.add_argument("--job-id", required=True)
+    sync.add_argument("--type", choices=["items", "companies", "leads", "all"], help="Result type to sync; defaults to the job kind")
+    sync.add_argument("--table-id", help="Existing Smart Table id for append/upsert")
+    sync.add_argument("--table-name", help="New Smart Table name when creating a table")
+    sync.add_argument("--table-mode", choices=["create", "append"], help="Create a new table or append/upsert into --table-id")
+    sync.add_argument(
+        "--identity-key",
+        default="auto",
+        help="Dedupe identity key: auto, linkedin_url, linkedin_company_id, linkedin_company_url, or domain",
+    )
+    sync.add_argument("--dedupe-mode", choices=["allow", "skip", "upsert"], default="upsert", help="How to handle matching rows")
+    sync.add_argument("--merge-mode", choices=["fill_empty", "overwrite_mapped"], default="fill_empty", help="How upserts merge values")
+    sync.add_argument("--allow-partial", action="store_true", help="Allow syncing before the list-build job is completed")
+    sync.add_argument("--wait", action="store_true", help="Poll until sync completes")
+    sync.add_argument("--poll-interval", type=int, default=5, help="Polling interval seconds for --wait")
+    sync.add_argument("--wait-timeout", type=int, default=0, help="Max seconds to wait (0 = no timeout)")
+    add_api_common_arguments(sync)
+    sync.set_defaults(func=handlers["sync_to_table"])
+
     inputs = sub.add_parser("inputs", help="Show valid list-build filter IDs and values")
     inputs.add_argument("--type", choices=["geo", "industry", "service", "title_skill", "title-skills"], help="Search input type")
     inputs.add_argument("--query", help="Search text for input ID lookup")

{autotouch_cli-0.2.103 → autotouch_cli-0.2.104}/autotouch_cli/data/CLI_REFERENCE.md

@@ -1,6 +1,6 @@
 # Autotouch CLI Reference
 
-Generated from the installed parser for `autotouch-cli` `0.2.103`.
+Generated from the installed parser for `autotouch-cli` `0.2.104`.
 Manifest schema version: `2`.
 
 ## Output Modes
@@ -2492,10 +2492,10 @@ Build durable LinkedIn-sourced company and lead lists
 - Auth: `varies_by_subcommand`
 - Stability: `stable`
 - Destructive: `no`
-- Subcommands: `companies, leads, status, results, inputs, pricing`
+- Subcommands: `companies, leads, status, results, sync-to-table, inputs, pricing`
 - Example:
   - `autotouch list-build [-h]
-                            {companies,leads,status,results,inputs,pricing} ...`
+                            {companies,leads,status,results,sync-to-table,inputs,pricing} ...`
 
 #### `autotouch list-build companies`
 
@@ -2724,6 +2724,57 @@ Get list-build job status
   - `--json-pointer` (kind=string): Extract a JSON pointer from the final result (for example: /id)
   - `--verbose` (kind=boolean; when omitted=False; when present=True): Print request metadata to stderr
 
+#### `autotouch list-build sync-to-table`
+
+Sync list-build results into a Smart Table
+
+- Auth: `developer_key_or_user_session`
+- Stability: `stable`
+- Destructive: `no`
+- Required flags: `--job-id`
+- Output modes: `json, ndjson, human`
+- Example:
+  - `autotouch list-build sync-to-table [-h] --job-id JOB_ID
+                                          [--type {items,companies,leads,all}]
+                                          [--table-id TABLE_ID]
+                                          [--table-name TABLE_NAME]
+                                          [--table-mode {create,append}]
+                                          [--identity-key IDENTITY_KEY]
+                                          [--dedupe-mode {allow,skip,upsert}]
+                                          [--merge-mode {fill_empty,overwrite_mapped}]
+                                          [--allow-partial] [--wait]
+                                          [--poll-interval POLL_INTERVAL]
+                                          [--wait-timeout WAIT_TIMEOUT]
+                                          [--base-url BASE_URL]
+                                          [--token TOKEN] [--use-x-api-key]
+                                          [--timeout TIMEOUT]
+                                          [--output {json,ndjson,human}]
+                                          [--compact] [--select SELECT |
+                                          --json-pointer JSON_POINTER]
+                                          [--verbose]`
+- Options:
+  - `--job-id` (required; kind=string)
+  - `--type` (kind=string; choices=items,companies,leads,all): Result type to sync; defaults to the job kind
+  - `--table-id` (kind=string): Existing Smart Table id for append/upsert
+  - `--table-name` (kind=string): New Smart Table name when creating a table
+  - `--table-mode` (kind=string; choices=create,append): Create a new table or append/upsert into --table-id
+  - `--identity-key` (kind=string; default=auto): Dedupe identity key: auto, linkedin_url, linkedin_company_id, linkedin_company_url, or domain
+  - `--dedupe-mode` (kind=string; choices=allow,skip,upsert; default=upsert): How to handle matching rows
+  - `--merge-mode` (kind=string; choices=fill_empty,overwrite_mapped; default=fill_empty): How upserts merge values
+  - `--allow-partial` (kind=boolean; when omitted=False; when present=True): Allow syncing before the list-build job is completed
+  - `--wait` (kind=boolean; when omitted=False; when present=True): Poll until sync completes
+  - `--poll-interval` (kind=integer; default=5): Polling interval seconds for --wait
+  - `--wait-timeout` (kind=integer; default=0): Max seconds to wait (0 = no timeout)
+  - `--base-url` (kind=string; default=https://app.autotouch.ai): API base URL (default: https://app.autotouch.ai)
+  - `--token` (kind=string; sensitive): Developer API key / JWT token
+  - `--use-x-api-key` (kind=boolean; when omitted=False; when present=True): Send token via X-API-Key header
+  - `--timeout` (kind=integer; default=30): HTTP timeout in seconds
+  - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
+  - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON
+  - `--select` (kind=string): Extract a dotted field path from the final result (for example: id or items.0.id)
+  - `--json-pointer` (kind=string): Extract a JSON pointer from the final result (for example: /id)
+  - `--verbose` (kind=boolean; when omitted=False; when present=True): Print request metadata to stderr
+
 ### `onboarding`
 
 #### `autotouch onboarding`
@@ -6057,7 +6108,7 @@ Update a webhook subscription
 
 Goal-level workflow plans and scaffolds
 
-Use workflows for full user goals. Recipes are leaf templates; workflow plans describe the ordered path across sourcing, research tables, enrichment, Leads, Sequences, and outreach destinations.
+Use workflows for full user goals. Autotouch workflows follow Source Records -> Land In Smart Table -> Research And Operate -> Engage. Recipes are leaf templates; workflow plans describe the ordered path across list building, imports/webhooks, Smart Table research, Leads, Sequences, CRM, and outreach destinations.
 
 - Auth: `varies_by_subcommand`
 - Stability: `stable`
@@ -6070,7 +6121,7 @@ Use workflows for full user goals. Recipes are leaf templates; workflow plans de
 
 #### `autotouch workflows list`
 
-List common workflow blueprints
+List common workflow blueprints grouped by lifecycle stage
 
 - Auth: `none`
 - Stability: `stable`
@@ -6092,7 +6143,7 @@ List common workflow blueprints
 
 Emit one goal-level workflow plan
 
-Plan the workflow before creating files or running side effects. Use this to choose a source, research, enrichment, and destination path for goals such as bulk outreach, account research, or signal outreach.
+Plan the workflow before creating files or running side effects. Use this to choose how records are sourced, landed in Smart Table, researched/operated on, and sent to the right engagement destination.
 
 - Auth: `none`
 - Stability: `stable`
@@ -6101,13 +6152,13 @@ Plan the workflow before creating files or running side effects. Use this to cho
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch workflows plan [-h]
-                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
+                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,agent-to-leads,account-research,signal-outreach,website-visitors,list-build-to-table}
                                 [--out-file OUT_FILE]
                                 [--output {json,ndjson,human}] [--compact]
                                 [--select SELECT |
                                 --json-pointer JSON_POINTER]`
 - Options:
-  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,agent-to-leads,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
   - `--out-file` (kind=file; input=file): Save raw workflow payload to file
   - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
   - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON
@@ -6125,13 +6176,13 @@ Alias for `workflows plan`
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch workflows recipe [-h]
-                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
+                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,agent-to-leads,account-research,signal-outreach,website-visitors,list-build-to-table}
                                   [--out-file OUT_FILE]
                                   [--output {json,ndjson,human}] [--compact]
                                   [--select SELECT |
                                   --json-pointer JSON_POINTER]`
 - Options:
-  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,agent-to-leads,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
   - `--out-file` (kind=file; input=file): Save raw workflow payload to file
   - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
   - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON
@@ -6149,13 +6200,13 @@ Emit ordered workflow files and commands for a blueprint
 - Output modes: `json, ndjson, human`
 - Example:
   - `autotouch workflows scaffold [-h]
-                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}
+                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,agent-to-leads,account-research,signal-outreach,website-visitors,list-build-to-table}
                                     [--out-dir OUT_DIR]
                                     [--output {json,ndjson,human}] [--compact]
                                     [--select SELECT |
                                     --json-pointer JSON_POINTER]`
 - Options:
-  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,agent-to-sequence,agent-to-leads,account-research,signal-outreach,website-visitors,list-build-to-table): Workflow blueprint type
   - `--out-dir` (kind=string): Directory to save scaffold payload files
   - `--output` (kind=string; choices=json,ndjson,human; default=json): Output mode
   - `--compact` (kind=boolean; when omitted=False; when present=True): Print compact JSON