autotouch-cli 0.2.97__tar.gz → 0.2.100__tar.gz

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.97
+Version: 0.2.100
 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
@@ -153,6 +153,7 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 - 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`
+- Create table webhook ingest tokens: `autotouch webhooks rotate`, `autotouch webhooks configure-ingest`, `autotouch webhooks ingest`
 
 ## Sequence Automation Choices
 
@@ -197,7 +198,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`, `account-research`, `signal-outreach`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, and Autotouch Sequences 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`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, 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
 
@@ -211,6 +212,35 @@ Use `autotouch integrations list` before wiring data movement. It returns connec
 
 Use the direction in the user's wording. "Pull from HubSpot" means `from_crm`. "Push to HubSpot" means `to_crm`. "Add these leads to this Autotouch sequence" means `to_leads` first when lead IDs do not exist, then `to_sequence`.
 
+## Table Webhook Ingest
+
+Use table webhooks when an external source should push records directly into a Smart Table.
+
+```bash
+WEBHOOK_TOKEN=$(autotouch webhooks rotate --table-id "$TABLE_ID" --output json --select token)
+
+autotouch webhooks configure-ingest \
+  --table-id "$TABLE_ID" \
+  --match-rule-id linkedin_url \
+  --match-strategy linkedin_url \
+  --duplicate-mode upsert
+
+autotouch webhooks ingest \
+  --table-id "$TABLE_ID" \
+  --webhook-token "$WEBHOOK_TOKEN" \
+  --records-json '{"records":[{"first_name":"Jane","last_name":"Doe","linkedin_url":"https://www.linkedin.com/in/jane-doe"}]}'
+```
+
+For external providers, prefer the `X-Autotouch-Token: <WEBHOOK_TOKEN>` header. If the provider cannot send custom headers and only accepts one webhook URL, use the compatibility URL:
+
+```text
+https://app.autotouch.ai/api/webhooks/tables/<TABLE_ID>/ingest?token=<WEBHOOK_TOKEN>
+```
+
+Use query-token URLs only for no-header providers because URLs may appear in provider logs or history. Rotate the table token if it is exposed.
+
+Webhook ingest stores the raw provider object in the `Webhook Payload` JSON column. For website visitor and external intent provider workflows, use `autotouch workflows plan --type website-visitors` first. The recommended shape is usually two starter tables: one for company-level events and one for person-level events. After a sample payload lands, use `autotouch columns projections` to split provider-specific JSON into stable columns such as `company_domain`, `linkedin_url`, `email`, `page_url`, `event_type`, and `last_seen_at`, then continue with enrichment, email finding, and the chosen destination.
+
 CRM round trip:
 
 ```bash
@@ -238,10 +268,11 @@ 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.97` 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`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, and goal-level workflow plans
+- `autotouch --version` should be `0.2.100` 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`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow 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 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_cli-0.2.97 → autotouch_cli-0.2.100}/README.md

@@ -128,6 +128,7 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 - 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`
+- Create table webhook ingest tokens: `autotouch webhooks rotate`, `autotouch webhooks configure-ingest`, `autotouch webhooks ingest`
 
 ## Sequence Automation Choices
 
@@ -172,7 +173,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`, `account-research`, `signal-outreach`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, and Autotouch Sequences 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`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, 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
 
@@ -186,6 +187,35 @@ Use `autotouch integrations list` before wiring data movement. It returns connec
 
 Use the direction in the user's wording. "Pull from HubSpot" means `from_crm`. "Push to HubSpot" means `to_crm`. "Add these leads to this Autotouch sequence" means `to_leads` first when lead IDs do not exist, then `to_sequence`.
 
+## Table Webhook Ingest
+
+Use table webhooks when an external source should push records directly into a Smart Table.
+
+```bash
+WEBHOOK_TOKEN=$(autotouch webhooks rotate --table-id "$TABLE_ID" --output json --select token)
+
+autotouch webhooks configure-ingest \
+  --table-id "$TABLE_ID" \
+  --match-rule-id linkedin_url \
+  --match-strategy linkedin_url \
+  --duplicate-mode upsert
+
+autotouch webhooks ingest \
+  --table-id "$TABLE_ID" \
+  --webhook-token "$WEBHOOK_TOKEN" \
+  --records-json '{"records":[{"first_name":"Jane","last_name":"Doe","linkedin_url":"https://www.linkedin.com/in/jane-doe"}]}'
+```
+
+For external providers, prefer the `X-Autotouch-Token: <WEBHOOK_TOKEN>` header. If the provider cannot send custom headers and only accepts one webhook URL, use the compatibility URL:
+
+```text
+https://app.autotouch.ai/api/webhooks/tables/<TABLE_ID>/ingest?token=<WEBHOOK_TOKEN>
+```
+
+Use query-token URLs only for no-header providers because URLs may appear in provider logs or history. Rotate the table token if it is exposed.
+
+Webhook ingest stores the raw provider object in the `Webhook Payload` JSON column. For website visitor and external intent provider workflows, use `autotouch workflows plan --type website-visitors` first. The recommended shape is usually two starter tables: one for company-level events and one for person-level events. After a sample payload lands, use `autotouch columns projections` to split provider-specific JSON into stable columns such as `company_domain`, `linkedin_url`, `email`, `page_url`, `event_type`, and `last_seen_at`, then continue with enrichment, email finding, and the chosen destination.
+
 CRM round trip:
 
 ```bash
@@ -213,10 +243,11 @@ 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.97` 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`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, and goal-level workflow plans
+- `autotouch --version` should be `0.2.100` 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`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow 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 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_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli/commands/webhooks.py

@@ -296,8 +296,8 @@ def cmd_webhooks_configure_ingest(args: argparse.Namespace, *, runtime: WebhookC
     merge_mode = str(getattr(args, "merge_mode", None) or "").strip()
     if match_rule_id:
         payload["match_rule_id"] = match_rule_id
-    if match_column:
-        payload["match_column"] = match_column
+    elif match_column:
+        payload["match_rule_id"] = match_column
     if match_strategy:
         payload["match_strategy"] = match_strategy
     if duplicate_mode:

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli/data/CLI_REFERENCE.md

@@ -1,6 +1,6 @@
 # Autotouch CLI Reference
 
-Generated from the installed parser for `autotouch-cli` `0.2.97`.
+Generated from the installed parser for `autotouch-cli` `0.2.100`.
 Manifest schema version: `2`.
 
 ## Output Modes
@@ -5506,8 +5506,8 @@ Persist ingest identity settings on a table's webhook config
                                            [--verbose]`
 - Options:
   - `--table-id` (required; kind=string)
-  - `--match-rule-id` (kind=string): Use a pre-configured table identity rule by ID
-  - `--match-column` (kind=string): Column key to match on (when no rule-id)
+  - `--match-rule-id` (kind=string): Identity rule id or column key to match on
+  - `--match-column` (kind=string): Column key to match on; alias for --match-rule-id when no rule id is set
   - `--match-strategy` (kind=string; choices=email,domain,linkedin_url,external_id,exact_text): Normalisation strategy for the match column
   - `--duplicate-mode` (kind=string; choices=allow,skip,upsert; default=upsert): Duplicate handling: allow / skip / upsert (default: upsert)
   - `--merge-mode` (kind=string; choices=fill_empty,overwrite_mapped; default=fill_empty): Cell merge strategy when upserting (default: fill_empty)
@@ -5650,7 +5650,7 @@ Ingest records using table webhook token
                                  --json-pointer JSON_POINTER] [--verbose]`
 - Options:
   - `--table-id` (required; kind=string)
-  - `--webhook-token` (kind=string; sensitive): x-autotouch-token (or AUTOTOUCH_WEBHOOK_TOKEN)
+  - `--webhook-token` (kind=string; sensitive): Table webhook token for CLI/header auth; no-header providers may use the ingest URL with ?token=<WEBHOOK_TOKEN>
   - `--records-json` (kind=json; input=json): Object, list, or {records:[...]} payload JSON
   - `--records-file` (kind=file; input=file): Path to JSON file containing records payload
   - `--base-url` (kind=string; default=https://app.autotouch.ai): API base URL (default: https://app.autotouch.ai)
@@ -6097,13 +6097,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,account-research,signal-outreach,list-build-to-table}
+                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,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,account-research,signal-outreach,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,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
@@ -6121,13 +6121,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,account-research,signal-outreach,list-build-to-table}
+                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,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,account-research,signal-outreach,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,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
@@ -6145,13 +6145,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,account-research,signal-outreach,list-build-to-table}
+                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,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,account-research,signal-outreach,list-build-to-table): Workflow blueprint type
+  - `--type` (required; kind=string; choices=bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,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

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli/data/cli-manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.2.97",
+  "version": "0.2.100",
   "manifest_schema_version": 2,
   "entry_points": {
     "autotouch": "autotouch_cli.cli:main",
@@ -9135,6 +9135,7 @@
             "research-to-sequence",
             "account-research",
             "signal-outreach",
+            "website-visitors",
             "list-build-to-table"
           ],
           "flags": [
@@ -9241,7 +9242,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch workflows plan [-h]\n                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,list-build-to-table}\n                                [--out-file OUT_FILE]\n                                [--output {json,ndjson,human}] [--compact]\n                                [--select SELECT |\n                                --json-pointer JSON_POINTER]"
+        "autotouch workflows plan [-h]\n                                --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                [--out-file OUT_FILE]\n                                [--output {json,ndjson,human}] [--compact]\n                                [--select SELECT |\n                                --json-pointer JSON_POINTER]"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -9275,6 +9276,7 @@
             "research-to-sequence",
             "account-research",
             "signal-outreach",
+            "website-visitors",
             "list-build-to-table"
           ],
           "flags": [
@@ -9381,7 +9383,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch workflows recipe [-h]\n                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,list-build-to-table}\n                                  [--out-file OUT_FILE]\n                                  [--output {json,ndjson,human}] [--compact]\n                                  [--select SELECT |\n                                  --json-pointer JSON_POINTER]"
+        "autotouch workflows recipe [-h]\n                                  --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                  [--out-file OUT_FILE]\n                                  [--output {json,ndjson,human}] [--compact]\n                                  [--select SELECT |\n                                  --json-pointer JSON_POINTER]"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -9415,6 +9417,7 @@
             "research-to-sequence",
             "account-research",
             "signal-outreach",
+            "website-visitors",
             "list-build-to-table"
           ],
           "flags": [
@@ -9520,7 +9523,7 @@
       },
       "availability": null,
       "examples": [
-        "autotouch workflows scaffold [-h]\n                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,list-build-to-table}\n                                    [--out-dir OUT_DIR]\n                                    [--output {json,ndjson,human}] [--compact]\n                                    [--select SELECT |\n                                    --json-pointer JSON_POINTER]"
+        "autotouch workflows scaffold [-h]\n                                    --type {bulk-outreach,company-table-to-people,table-to-outreach,research-to-sequence,account-research,signal-outreach,website-visitors,list-build-to-table}\n                                    [--out-dir OUT_DIR]\n                                    [--output {json,ndjson,human}] [--compact]\n                                    [--select SELECT |\n                                    --json-pointer JSON_POINTER]"
       ],
       "stability": "stable",
       "handler": "_fn"
@@ -30696,7 +30699,7 @@
         {
           "dest": "webhook_token",
           "required": false,
-          "help": "x-autotouch-token (or AUTOTOUCH_WEBHOOK_TOKEN)",
+          "help": "Table webhook token for CLI/header auth; no-header providers may use the ingest URL with ?token=<WEBHOOK_TOKEN>",
           "kind": "string",
           "action": "store",
           "sensitive": true,
@@ -30917,7 +30920,7 @@
         {
           "dest": "match_rule_id",
           "required": false,
-          "help": "Use a pre-configured table identity rule by ID",
+          "help": "Identity rule id or column key to match on",
           "kind": "string",
           "action": "store",
           "flags": [
@@ -30928,7 +30931,7 @@
         {
           "dest": "match_column",
           "required": false,
-          "help": "Column key to match on (when no rule-id)",
+          "help": "Column key to match on; alias for --match-rule-id when no rule id is set",
           "kind": "string",
           "action": "store",
           "flags": [
@@ -39804,4 +39807,4 @@
       "handler": "cmd_sop"
     }
   }
-}
+}

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli/parser_groups.py

@@ -183,7 +183,10 @@ def add_webhooks_subcommands(
 
     pwhi = wh_sub.add_parser("ingest", help="Ingest records using table webhook token")
     pwhi.add_argument("--table-id", required=True)
-    pwhi.add_argument("--webhook-token", help="x-autotouch-token (or AUTOTOUCH_WEBHOOK_TOKEN)")
+    pwhi.add_argument(
+        "--webhook-token",
+        help="Table webhook token for CLI/header auth; no-header providers may use the ingest URL with ?token=<WEBHOOK_TOKEN>",
+    )
     pwhi.add_argument("--records-json", help="Object, list, or {records:[...]} payload JSON")
     pwhi.add_argument("--records-file", help="Path to JSON file containing records payload")
     add_api_common_arguments(pwhi)
@@ -195,8 +198,8 @@ def add_webhooks_subcommands(
 
     pwhci = wh_sub.add_parser("configure-ingest", help="Persist ingest identity settings on a table's webhook config")
     pwhci.add_argument("--table-id", required=True)
-    pwhci.add_argument("--match-rule-id", default=None, help="Use a pre-configured table identity rule by ID")
-    pwhci.add_argument("--match-column", default=None, help="Column key to match on (when no rule-id)")
+    pwhci.add_argument("--match-rule-id", default=None, help="Identity rule id or column key to match on")
+    pwhci.add_argument("--match-column", default=None, help="Column key to match on; alias for --match-rule-id when no rule id is set")
     pwhci.add_argument(
         "--match-strategy",
         choices=_MATCH_STRATEGIES,

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli/templates.py

@@ -241,6 +241,28 @@ _CONTACT_ITEM_FIELDS: List[Tuple[str, str]] = [
     ("company_domain", "Company Domain"),
     ("linkedin_url", "LinkedIn URL"),
 ]
+_WEBSITE_VISITOR_COMPANY_PROJECTION_FIELDS: List[Tuple[str, str, str, str]] = [
+    ("company_domain", "Company Domain", "company.domain", "text"),
+    ("company_name", "Company Name", "company.name", "text"),
+    ("provider_company_id", "Provider Company ID", "company.id", "text"),
+    ("event_type", "Event Type", "event.type", "text"),
+    ("page_url", "Page URL", "event.url", "url"),
+    ("last_seen_at", "Last Seen At", "event.timestamp", "date"),
+]
+_WEBSITE_VISITOR_PERSON_PROJECTION_FIELDS: List[Tuple[str, str, str, str]] = [
+    ("first_name", "First Name", "person.first_name", "text"),
+    ("last_name", "Last Name", "person.last_name", "text"),
+    ("full_name", "Full Name", "person.name", "text"),
+    ("title", "Title", "person.title", "text"),
+    ("linkedin_url", "LinkedIn URL", "person.linkedin_url", "url"),
+    ("email", "Email", "person.email", "email"),
+    ("company_domain", "Company Domain", "company.domain", "text"),
+    ("company_name", "Company Name", "company.name", "text"),
+    ("provider_person_id", "Provider Person ID", "person.id", "text"),
+    ("event_type", "Event Type", "event.type", "text"),
+    ("page_url", "Page URL", "event.url", "url"),
+    ("last_seen_at", "Last Seen At", "event.timestamp", "date"),
+]
 
 
 def _build_column_recipe_catalog() -> Tuple[Dict[str, Dict[str, Any]], Dict[str, List[str]]]:
@@ -1032,6 +1054,12 @@ WEBHOOK_RECIPES: Dict[str, Dict[str, Any]] = {
 WEBHOOK_RECIPE_NOTES: Dict[str, List[str]] = {
     "ingest": [
         "Use this with webhooks ingest when writing rows through a table webhook token.",
+        "Recommended auth for external providers is the X-Autotouch-Token header.",
+        "For providers that cannot send custom headers, use the compatibility URL https://app.autotouch.ai/api/webhooks/tables/<TABLE_ID>/ingest?token=<WEBHOOK_TOKEN>.",
+        "Use query-token URLs only for no-header providers because URLs may appear in provider logs or history; rotate the table token if it is exposed.",
+        "Webhook ingest stores the raw provider object in the Webhook Payload JSON column. Use autotouch columns projections to split provider-specific JSON into stable columns for mapping/filtering.",
+        "Company-level and person-level external events usually belong in separate starter tables because they use different identity fields and downstream steps.",
+        "Configure ingest identity before going live when the provider sends a flat identity field, for example: autotouch webhooks configure-ingest --table-id <TABLE_ID> --match-rule-id linkedin_url --match-strategy linkedin_url --duplicate-mode upsert.",
     ],
     "subscription_create": [
         "retryPolicy is optional, but including it makes the request contract explicit for agents.",
@@ -1396,6 +1424,21 @@ def _projection_payload(*, source_column_id: str, fields: List[Tuple[str, str]])
     }
 
 
+def _visitor_projection_payload(*, source_column_id: str, fields: List[Tuple[str, str, str, str]]) -> Dict[str, Any]:
+    return {
+        "items": [
+            {
+                "key": field_key,
+                "label": field_label,
+                "sourceColumnId": source_column_id,
+                "path": json_path,
+                "dataType": data_type,
+            }
+            for field_key, field_label, json_path, data_type in fields
+        ]
+    }
+
+
 def _single_buyer_instructions(*, include_company_domain: bool) -> str:
     keys = ["first_name", "last_name", "title", "company_name", "company_website"]
     if include_company_domain:
@@ -1841,6 +1884,134 @@ def _workflow_scaffold_signal_outreach() -> Dict[str, Any]:
     }
 
 
+def _workflow_scaffold_website_visitors() -> Dict[str, Any]:
+    artifacts = [
+        _workflow_artifact(
+            step=1,
+            provider="json_projections",
+            filename="01-company-event-projections.json",
+            payload=_visitor_projection_payload(
+                source_column_id="<COMPANY_WEBHOOK_PAYLOAD_COLUMN_ID>",
+                fields=_WEBSITE_VISITOR_COMPANY_PROJECTION_FIELDS,
+            ),
+            table_scope="company_event_table",
+            kind="projection_payload",
+            notes=[
+                "Edit path values to match the provider payload. These defaults assume company.domain, company.name, and event.* paths.",
+                "Use after a sample webhook row has created/populated the Webhook Payload JSON column.",
+            ],
+        ),
+        _workflow_artifact(
+            step=2,
+            provider="json_projections",
+            filename="02-person-event-projections.json",
+            payload=_visitor_projection_payload(
+                source_column_id="<PERSON_WEBHOOK_PAYLOAD_COLUMN_ID>",
+                fields=_WEBSITE_VISITOR_PERSON_PROJECTION_FIELDS,
+            ),
+            table_scope="person_event_table",
+            kind="projection_payload",
+            notes=[
+                "Edit path values to match the provider payload. These defaults assume person.*, company.*, and event.* paths.",
+                "Person event tables usually dedupe on email, linkedin_url, or provider_person_id.",
+            ],
+        ),
+        _workflow_artifact(
+            step=3,
+            provider="llm",
+            recipe_type="llm_enrichment",
+            filename="03-company-event-find-people.json",
+            payload=_items_agent_payload(),
+            table_scope="company_event_table",
+            notes=[
+                "Use this for company-level visitor events that do not already include a person.",
+                "Adjust instructions/persona before creating the column.",
+            ],
+        ),
+        _workflow_artifact(
+            step=4,
+            provider="sync_to_table",
+            recipe_type="sync_to_table",
+            filename="04-sync-visitor-contacts-to-table.json",
+            payload=_items_sync_to_table_payload(),
+            table_scope="company_event_table",
+            notes=[
+                "Create a contacts/person table first, then set destinationTableId and listSourceColumnId.",
+            ],
+        ),
+        _workflow_artifact(
+            step=5,
+            provider="email_finder",
+            recipe_type="email_finder",
+            filename="05-email-finder.json",
+            payload=_recipe_payload("email_finder"),
+            table_scope="person_or_contacts_table",
+            notes=["Use on the person event table or the contacts table created from company events."],
+        ),
+        _workflow_artifact(
+            step=6,
+            provider="to_outreach",
+            recipe_type="to_outreach",
+            filename="06-push-to-outreach.json",
+            payload=_recipe_payload("to_outreach"),
+            table_scope="person_or_contacts_table",
+            notes=["Optional destination. Set outreachProvider, campaignId, emailColumnKey, and variableMappings."],
+        ),
+        _workflow_artifact(
+            step=7,
+            provider="to_leads",
+            recipe_type="to_leads",
+            filename="07-sync-to-leads.json",
+            payload=_items_sync_to_leads_payload(),
+            table_scope="person_or_contacts_table",
+            notes=["Optional destination step before Autotouch Sequence enrollment."],
+        ),
+        _workflow_artifact(
+            step=8,
+            provider="to_sequence",
+            recipe_type="to_sequence",
+            filename="08-add-to-sequence.json",
+            payload=_to_sequence_payload(source_lead_column="sync_to_leads"),
+            table_scope="person_or_contacts_table",
+            notes=[
+                "Optional destination. Set sequenceId and assignedToUserId before creating the column.",
+                "Use manual AI-draft review by default for researched website visitor or external intent campaigns.",
+            ],
+        ),
+    ]
+    return {
+        "artifacts": artifacts,
+        "commands": [
+            "autotouch tables create --name 'Website Visitor Companies' --output json",
+            "autotouch tables create --name 'Website Visitor People' --output json",
+            "autotouch webhooks rotate --table-id <COMPANY_EVENTS_TABLE_ID> --output json",
+            "autotouch webhooks rotate --table-id <PERSON_EVENTS_TABLE_ID> --output json",
+            "autotouch webhooks recipe --type ingest --output json",
+            "autotouch webhooks configure-ingest --table-id <COMPANY_EVENTS_TABLE_ID> --match-rule-id company_domain --match-strategy domain --duplicate-mode upsert --merge-mode fill_empty",
+            "autotouch webhooks configure-ingest --table-id <PERSON_EVENTS_TABLE_ID> --match-rule-id email --match-strategy email --duplicate-mode upsert --merge-mode fill_empty",
+            "autotouch columns projections --table-id <COMPANY_EVENTS_TABLE_ID> --after-column-id <COMPANY_WEBHOOK_PAYLOAD_COLUMN_ID> --data-file 01-company-event-projections.json",
+            "autotouch columns projections --table-id <PERSON_EVENTS_TABLE_ID> --after-column-id <PERSON_WEBHOOK_PAYLOAD_COLUMN_ID> --data-file 02-person-event-projections.json",
+            "autotouch columns create --table-id <COMPANY_EVENTS_TABLE_ID> --data-file 03-company-event-find-people.json",
+            "autotouch columns run-next --table-id <COMPANY_EVENTS_TABLE_ID> --column-id <CONTACT_ITEMS_COLUMN_ID> --count 25 --show-estimate --wait --output json",
+            "autotouch tables create --name '<VISITOR_CONTACTS_TABLE_NAME>' --output json",
+            "autotouch columns create --table-id <COMPANY_EVENTS_TABLE_ID> --data-file 04-sync-visitor-contacts-to-table.json",
+            "autotouch columns run --table-id <COMPANY_EVENTS_TABLE_ID> --column-id <SYNC_CONTACTS_TO_TABLE_COLUMN_ID> --wait --output json",
+            "autotouch columns create --table-id <PERSON_OR_CONTACTS_TABLE_ID> --data-file 05-email-finder.json",
+            "autotouch columns run-next --table-id <PERSON_OR_CONTACTS_TABLE_ID> --column-id <EMAIL_FINDER_COLUMN_ID> --count 25 --show-estimate --wait --output json",
+            "autotouch integrations list --select destinations --output json",
+            "autotouch workflows scaffold --type table-to-outreach --out-dir outreach-handoff",
+            "autotouch workflows scaffold --type research-to-sequence --out-dir sequence-handoff",
+        ],
+        "notes": [
+            "Keep company-level and person-level webhook events in separate starter tables unless the provider has one clean event shape.",
+            "Webhook ingest stores the raw provider object in Webhook Payload. Use columns projections to split that JSON into stable columns before downstream mapping/filtering.",
+            "For ingest-time upsert, the identity field must be present as a mapped flat field on the incoming row. If the provider sends only nested JSON, split a sample first and configure the provider or payload mapping to send a flat identity field such as company_domain, email, or linkedin_url.",
+            "Header auth is preferred. Use the query-token URL only for providers that cannot send custom headers.",
+            "This scaffold stops at common handoff points; use the destination-specific scaffolds for provider upload or Autotouch Sequence enrollment.",
+        ],
+    }
+
+
 def _workflow_scaffold_list_build_to_table() -> Dict[str, Any]:
     return {
         "artifacts": [],
@@ -2091,6 +2262,7 @@ def _workflow_scaffold_bundle(workflow_type: str) -> Dict[str, Any]:
         "research-to-sequence": _workflow_scaffold_research_to_sequence,
         "account-research": _workflow_scaffold_account_research,
         "signal-outreach": _workflow_scaffold_signal_outreach,
+        "website-visitors": _workflow_scaffold_website_visitors,
         "list-build-to-table": _workflow_scaffold_list_build_to_table,
         "lead_finder_to_sequence": _workflow_scaffold_lead_finder_to_sequence,
         "llm_items_to_contacts_then_sequence": _workflow_scaffold_items_to_contacts_then_sequence,
@@ -2425,7 +2597,7 @@ def emit_webhooks_recipe(args: argparse.Namespace, runtime: TemplateRuntime) ->
         payload_getter=_webhook_recipe_payload,
         notes_lookup=WEBHOOK_RECIPE_NOTES,
         usage_lookup={
-            "ingest": "autotouch webhooks ingest --table-id <TABLE_ID> --records-file <payload.json>",
+            "ingest": "autotouch webhooks ingest --table-id <TABLE_ID> --webhook-token <WEBHOOK_TOKEN> --records-file <payload.json>",
             "subscription_create": "autotouch webhooks subscriptions create --data-file <payload.json>",
             "subscription_update": "autotouch webhooks subscriptions update --subscription-id <SUB_ID> --data-file <payload.json>",
             "subscription_test": "autotouch webhooks subscriptions test --subscription-id <SUB_ID> --data-file <payload.json>",

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli/workflows/registry.py

@@ -138,6 +138,57 @@ _GOAL_WORKFLOW_BLUEPRINTS: Dict[str, Dict[str, Any]] = {
             {"provider": "to_outreach", "purpose": "optionally push qualified table rows to Instantly or Smartlead"},
         ],
     },
+    "website-visitors": {
+        "goal": "Ingest website visitor or external intent provider webhooks, split payload JSON into usable columns, then enrich and route company/person intent to outreach destinations.",
+        "use_case": "website_visitor_external_intent_webhook",
+        "supported_starting_points": ["website_visitor_provider", "external_intent_provider_webhook", "company_event", "person_event"],
+        "recommended_when": [
+            "an external provider sends website visitor, account intent, or person intent events by webhook",
+            "the workflow should start from raw provider payloads and turn them into Smart Table columns before automation",
+            "company-level events and person-level events may arrive as different event types or payload shapes",
+        ],
+        "default_safety": {
+            "separate_event_grain_tables": True,
+            "header_auth_preferred": True,
+            "query_token_only_for_no_header_providers": True,
+            "sample_first": True,
+            "dedupe_before_downstream_runs": True,
+        },
+        "event_grain": {
+            "company_events": {
+                "starter_table": "Website Visitor Companies",
+                "identity_preference": ["company_domain", "provider_company_id"],
+                "dedupe": "match company_domain with domain strategy when available; otherwise match provider_company_id with external_id strategy",
+                "next_steps": ["split webhook_payload JSON", "enrich company", "find people", "find email", "route destination"],
+            },
+            "person_events": {
+                "starter_table": "Website Visitor People",
+                "identity_preference": ["email", "linkedin_url", "provider_person_id"],
+                "dedupe": "match email when available; otherwise linkedin_url; otherwise provider_person_id with external_id strategy",
+                "next_steps": ["split webhook_payload JSON", "find or verify email if missing", "route destination"],
+            },
+        },
+        "docs": {
+            "webhook_ingest": "autotouch webhooks recipe --type ingest",
+            "json_split": "autotouch columns projections --help",
+            "json_split_concept": "docs/research-table/concepts/projection-columns.md",
+            "destinations": "autotouch integrations list --select destinations",
+        },
+        "steps": [
+            {"provider": "webhooks", "purpose": "create a table webhook token and ingest raw provider payloads"},
+            {"provider": "webhooks.configure-ingest", "purpose": "persist identity/upsert behavior separately for company and person event tables"},
+            {"provider": "columns.projections", "purpose": "split webhook_payload JSON into stable columns such as company_domain, linkedin_url, email, page_url, event_type, and last_seen_at"},
+            {"provider": "llm_enrichment", "purpose": "for company events, enrich the account or find likely people when the event has no person"},
+            {"provider": "email_finder", "purpose": "find or verify email addresses before outreach destinations"},
+            {"provider": "to_outreach|to_leads|to_sequence|to_crm", "purpose": "route qualified rows to the user's chosen destination"},
+        ],
+        "inspect_commands": [
+            "autotouch webhooks get --table-id <TABLE_ID> --output json",
+            "autotouch rows list --table-id <TABLE_ID> --page-size 5 --output json",
+            "autotouch cells get --table-id <TABLE_ID> --row-id <ROW_ID> --column-id <COLUMN_ID> --output json",
+            "autotouch jobs get --job-id <JOB_ID> --output json",
+        ],
+    },
     "list-build-to-table": {
         "goal": "Build a company or lead list and land the results in a Smart Table for enrichment.",
         "use_case": "new_list_acquisition",

{autotouch_cli-0.2.97 → autotouch_cli-0.2.100}/autotouch_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.97
+Version: 0.2.100
 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
@@ -153,6 +153,7 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 - 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`
+- Create table webhook ingest tokens: `autotouch webhooks rotate`, `autotouch webhooks configure-ingest`, `autotouch webhooks ingest`
 
 ## Sequence Automation Choices
 
@@ -197,7 +198,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`, `account-research`, `signal-outreach`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, and Autotouch Sequences 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`, `account-research`, `signal-outreach`, `website-visitors`, and `list-build-to-table`. These keep CRM, outreach providers, Autotouch Leads, Autotouch Sequences, 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
 
@@ -211,6 +212,35 @@ Use `autotouch integrations list` before wiring data movement. It returns connec
 
 Use the direction in the user's wording. "Pull from HubSpot" means `from_crm`. "Push to HubSpot" means `to_crm`. "Add these leads to this Autotouch sequence" means `to_leads` first when lead IDs do not exist, then `to_sequence`.
 
+## Table Webhook Ingest
+
+Use table webhooks when an external source should push records directly into a Smart Table.
+
+```bash
+WEBHOOK_TOKEN=$(autotouch webhooks rotate --table-id "$TABLE_ID" --output json --select token)
+
+autotouch webhooks configure-ingest \
+  --table-id "$TABLE_ID" \
+  --match-rule-id linkedin_url \
+  --match-strategy linkedin_url \
+  --duplicate-mode upsert
+
+autotouch webhooks ingest \
+  --table-id "$TABLE_ID" \
+  --webhook-token "$WEBHOOK_TOKEN" \
+  --records-json '{"records":[{"first_name":"Jane","last_name":"Doe","linkedin_url":"https://www.linkedin.com/in/jane-doe"}]}'
+```
+
+For external providers, prefer the `X-Autotouch-Token: <WEBHOOK_TOKEN>` header. If the provider cannot send custom headers and only accepts one webhook URL, use the compatibility URL:
+
+```text
+https://app.autotouch.ai/api/webhooks/tables/<TABLE_ID>/ingest?token=<WEBHOOK_TOKEN>
+```
+
+Use query-token URLs only for no-header providers because URLs may appear in provider logs or history. Rotate the table token if it is exposed.
+
+Webhook ingest stores the raw provider object in the `Webhook Payload` JSON column. For website visitor and external intent provider workflows, use `autotouch workflows plan --type website-visitors` first. The recommended shape is usually two starter tables: one for company-level events and one for person-level events. After a sample payload lands, use `autotouch columns projections` to split provider-specific JSON into stable columns such as `company_domain`, `linkedin_url`, `email`, `page_url`, `event_type`, and `last_seen_at`, then continue with enrichment, email finding, and the chosen destination.
+
 CRM round trip:
 
 ```bash
@@ -238,10 +268,11 @@ 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.97` 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`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, and goal-level workflow plans
+- `autotouch --version` should be `0.2.100` 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`, paced HTTP Request column contracts, branch-aware LinkedIn sequence recipes, real agent soft-delete with associated-table handling, research-table sequence handoff assignee config, backend-owned directional source/destination helpers, goal-level workflow plans, and website visitor/external intent webhook workflow 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 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_cli-0.2.97 → autotouch_cli-0.2.100}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "autotouch-cli"
-version = "0.2.97"
+version = "0.2.100"
 description = "Autotouch Smart Table CLI"
 readme = "README.md"
 requires-python = ">=3.9"