ESC
↑↓ navigate↵ open

Home / Signal / #009

Signal #009 · 6 November 2026

We got ChurnZero's write access wrong. HubSpot's AI connectors get a read-only key to sensitive data.

Signal is a weekly note on what actually changed in the commercial software stack (pricing models, agent interfaces, ownership) tagged to the layer of the Agentic Commercial Model it belongs to. A link to the document behind every claim, and no filler to hit a quota: this issue is two items, because two is what the documentation actually supports.

Checked against the 3 November 2026 Agent Access Registry baseline: the rows carrying a claimed-undocumented, third-party-only or unclear-write-access status, plus a general sweep for MCP and agent-interface news across all 43 tracked vendors and adjacent competitors, re-verified against that dated row. Two rows re-date below, to 6 November 2026; one changes grade.

In this issue

  1. ChurnZero's REST API already writes to Accounts and Contacts. Our own note called it read only.
  2. HubSpot's AI connectors get a read-only key to Sensitive Data. The write surface doesn't move.
01Layer 7 · Customer Success & Adoption

ChurnZero's REST API already writes to Accounts and Contacts. Our own note called it read only.

ChurnZero's HTTP API, documented at support.churnzero.com and authenticated with an account level appKey, exposes setAttribute, incrementAttribute and trackEvent endpoints that create and update Account and Contact records. ChurnZero's own integration guide states plainly: “we only allow updates to Accounts and Contacts using our API and Javascript.” Our Aug 21, 2026 registry note described this same API as read only, with writes handled by a separate ingestion API whose agent-scoped use was undocumented. That was a misread: the write capability it was describing is this API, not a separate one, and it has been documented the whole time. No roles, scopes, or permission tiers are documented beyond the appKey itself, and the API's response format (every call returns HTTP 200 with a 1x1 tracking pixel) gives no indication of whether a write actually succeeded.

Why it matters: this is a correction to our own research rather than a vendor announcement, and it moves ChurnZero's Agent write access grade from Unclear to Documented — the registry's aggregate write-access count rises to 34 of 43. It does not touch ChurnZero's MCP status: Agentic Essentials and ChurnZero Connect (MCP) remain verifiable only through an Aug 2026 press release, with zero technical documentation behind the AI-specific interface. The broader lesson travels past ChurnZero: a vendor's plain old REST API, built with no AI framing at all, often already clears the “documented write access” bar this registry checks for, while the newer, flashier MCP server sitting next to it gets none of its own documentation. Grading the boring API honestly matters as much as catching the undocumented new one.

Source: ChurnZero: Integrate ChurnZero using HTTP API · ChurnZero: Agentic Essentials press release

02Layer 9 · CRM & Pipeline

HubSpot's AI connectors get a read-only key to Sensitive Data. The write surface doesn't move.

HubSpot's Oct 30, 2026 “October 2026 Rollup” changelog entry opens a new, opt-in permission: Super Admins can now let supported AI connectors read Sensitive Data properties and engagements that were previously blocked outright. ChatGPT, Claude and Copilot get both Sensitive Data properties and engagements; Gemini and HubSpot's own Remote MCP server get engagements only. The page states directly that “access is read-only,” and turning it on requires disconnecting and reauthenticating each connector under Settings > Integrations > Connected Apps, with new permissions taking up to two hours to propagate.

Why it matters: HubSpot was already Official, Documented and Documented across all three registry columns, and nothing here changes that grade — this is new read access, not a new write verb, so the row re-dates without a status move. What it does show is a vendor treating Sensitive Data as a separate, higher-bar permission tier from ordinary CRM write access, gated connector by connector rather than granted the moment an app connects. That is a more conservative default than most of the write-access rows already Documented in this registry, and it is worth watching whether other vendors sitting on sensitive fields (payroll, health, compensation) adopt the same split before they ever get near write access at all.

Source: HubSpot developer changelog: October 2026 Rollup

Registry moves

Two rows re-date this week, to 6 November 2026, one with a grade change. ChurnZero's Agent write access grade moves from Unclear to Documented after we corrected our own Aug 21 note, which had described its HTTP API as read only; its MCP status is unchanged (still claimed, undocumented). HubSpot's row is re-dated without a grade change, noting the Oct 30, 2026 Sensitive Data read permission for AI connectors.

The registry's aggregate figures move with it: 27 of 43 vendors still publish an official MCP server, and 34 of 43 (up from 33) now document agent write access. The single zero-interface category, Sales Compensation & Incentive Management, is unchanged.

Signal lands weekly. The registry updates with it.

Layer tagged, evidence linked. If something here is wrong or out of date, tell us and we will re check and re date the row.

Open the registry →