autotouch-cli 0.2.52__tar.gz → 0.2.58__tar.gz

{autotouch_cli-0.2.52 → autotouch_cli-0.2.58}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.52
+Version: 0.2.58
 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
@@ -40,6 +40,8 @@ For a shipped human-readable reference generated from the installed parser, use
 pipx install autotouch-cli
 # or
 pip install autotouch-cli
+# upgrade
+pip install -U autotouch-cli
 ```
 
 ## First Run
@@ -135,6 +137,7 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 - Poll authoritative state: `autotouch jobs get`
 - Create/activate sequences: `autotouch sequences recipe`, `autotouch sequences create`, `autotouch sequences activate`
 - Query leads: `autotouch leads query`
+- Find a lead by email or phone: `autotouch leads query --search '<email-or-phone>' --limit 10`
 
 ## More
 
@@ -155,9 +158,15 @@ For `llm_enrichment` in `agent` mode, the recommended path is:
 
 Only send `user_schema` / `response_schema` when you intentionally want to override the generated schema and keep it aligned yourself. The installed recipe surface at `autotouch columns recipe --type llm_enrichment` follows this contract.
 
+Prompt variables in authored prompts support nested JSON access:
+- Use flat row variables like `{{company_name}}` for scalar columns.
+- Use dotted placeholders like `{{linkedin_lookup.linkedin_url}}` when the source column stores JSON or stringified JSON.
+- For arrays, use numeric indexes such as `{{contacts.0.email}}`.
+- This is different from config payload mappings, which use objects like `{ "column": "linkedin_lookup", "path": "linkedin_url" }`.
+
 ## Docs
 
-- Full CLI reference: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/research-table/reference/autotouch-cli.md
-- Agent playbook: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/research-table/guides/autotouch-cli-agent-playbook.md
-- Tables/API reference: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/research-table/reference/tables-api.md
-- Authentication/scopes: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/platform/authentication.md
+- Full CLI reference: https://github.com/nicolonic/autotouch_main/blob/main/docs/research-table/reference/autotouch-cli.md
+- Agent playbook: https://github.com/nicolonic/autotouch_main/blob/main/docs/research-table/guides/autotouch-cli-agent-playbook.md
+- Tables/API reference: https://github.com/nicolonic/autotouch_main/blob/main/docs/research-table/reference/tables-api.md
+- Authentication/scopes: https://github.com/nicolonic/autotouch_main/blob/main/docs/platform/authentication.md

{autotouch_cli-0.2.52 → autotouch_cli-0.2.58}/README.md

@@ -15,6 +15,8 @@ For a shipped human-readable reference generated from the installed parser, use
 pipx install autotouch-cli
 # or
 pip install autotouch-cli
+# upgrade
+pip install -U autotouch-cli
 ```
 
 ## First Run
@@ -110,6 +112,7 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 - Poll authoritative state: `autotouch jobs get`
 - Create/activate sequences: `autotouch sequences recipe`, `autotouch sequences create`, `autotouch sequences activate`
 - Query leads: `autotouch leads query`
+- Find a lead by email or phone: `autotouch leads query --search '<email-or-phone>' --limit 10`
 
 ## More
 
@@ -130,9 +133,15 @@ For `llm_enrichment` in `agent` mode, the recommended path is:
 
 Only send `user_schema` / `response_schema` when you intentionally want to override the generated schema and keep it aligned yourself. The installed recipe surface at `autotouch columns recipe --type llm_enrichment` follows this contract.
 
+Prompt variables in authored prompts support nested JSON access:
+- Use flat row variables like `{{company_name}}` for scalar columns.
+- Use dotted placeholders like `{{linkedin_lookup.linkedin_url}}` when the source column stores JSON or stringified JSON.
+- For arrays, use numeric indexes such as `{{contacts.0.email}}`.
+- This is different from config payload mappings, which use objects like `{ "column": "linkedin_lookup", "path": "linkedin_url" }`.
+
 ## Docs
 
-- Full CLI reference: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/research-table/reference/autotouch-cli.md
-- Agent playbook: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/research-table/guides/autotouch-cli-agent-playbook.md
-- Tables/API reference: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/research-table/reference/tables-api.md
-- Authentication/scopes: https://github.com/nicolonic/autotouch_main/blob/autotouch-cli-v0.2.52/docs/platform/authentication.md
+- Full CLI reference: https://github.com/nicolonic/autotouch_main/blob/main/docs/research-table/reference/autotouch-cli.md
+- Agent playbook: https://github.com/nicolonic/autotouch_main/blob/main/docs/research-table/guides/autotouch-cli-agent-playbook.md
+- Tables/API reference: https://github.com/nicolonic/autotouch_main/blob/main/docs/research-table/reference/tables-api.md
+- Authentication/scopes: https://github.com/nicolonic/autotouch_main/blob/main/docs/platform/authentication.md