{
  "source": "DABYTE analysis, dabyte.ai",
  "note": "Full text of each piece is written by us and licensed CC BY 4.0. Linked sources remain with their publishers. The measurement each piece rests on comes from our own monthly panel.",
  "license": "CC-BY-4.0",
  "count": 5,
  "articles": [
    {
      "slug": "breaking-change-pipeline-and-pipeline-stage-delete-endpoints-will-vali",
      "title": "HubSpot Adds Reference Validation to Pipeline Delete Endpoints in 2026-09 API",
      "url": "https://dabyte.ai/articles/breaking-change-pipeline-and-pipeline-stage-delete-endpoints-will-vali/",
      "published_at": "2026-07-31",
      "summary": "HubSpot announced on 2026-07-21 that pipeline and pipeline stage delete endpoints will validate references by default starting with the 2026-09 API version, and on 2026-07-23 updated the notice to add the Deal-object query parameter validateDealStageUsagesBeforeDelete. The change was carried by a single source, HubSpot's own developer channel, while HubSpot held a visibility score of 25.0 and rank 2 in the SaaS & AI Tools AI Visibility Index measured on 2026-07-28.",
      "key_facts": [
        "HubSpot published the pipeline and pipeline stage delete validation notice on 2026-07-21 and amended it on 2026-07-23.",
        "Reference validation becomes the default on these endpoints starting with the 2026-09 API version.",
        "The 2026-07-23 amendment added the Deal-object query parameter validateDealStageUsagesBeforeDelete.",
        "Corroboration for the event is 1 outlet: HubSpot's own developer channel, recorded as rel_hubspot.",
        "HubSpot scored 25.0 visibility at rank 2 in the SaaS & AI Tools AI Visibility Index measured 2026-07-28, with a delta of 4.1.",
        "HubSpot's per-engine scores were 25.0 on OpenAI and 25.0 on Perplexity, with commercial intent of 82."
      ],
      "brands": [
        "HubSpot"
      ],
      "corroboration": 1,
      "sources": [
        "https://developers.hubspot.com/changelog/pipeline-stage-validation-true"
      ],
      "ttl_hours": 336,
      "measurement": [
        {
          "rank": 2,
          "brand": "HubSpot",
          "delta": 4.1,
          "quadrant": "Niche (visibility gap)",
          "per_engine": {
            "openai": 25.0,
            "perplexity": 25.0
          },
          "visibility_score": 25.0,
          "commercial_intent": 82
        }
      ]
    },
    {
      "slug": "app-listing-and-app-certification-requirement-updates-for-may-2026",
      "title": "HubSpot Updates Marketplace App Listing and Certification Requirements",
      "url": "https://dabyte.ai/articles/app-listing-and-app-certification-requirement-updates-for-may-2026/",
      "published_at": "2026-07-31",
      "summary": "HubSpot published updated requirements for listed and certified apps in the HubSpot Marketplace on 2026-05-07, tying them to current platform standards and deprecations, with the announcement carried by a single source — HubSpot itself. In DABYTE's SaaS & AI Tools AI Visibility Index measured on 2026-07-28, HubSpot holds a visibility score of 25.0 and rank 2, with identical 25.0 shares on OpenAI and Perplexity, a delta of +4.1, and commercial intent of 82.",
      "key_facts": [
        "HubSpot updated listing and certification requirements for HubSpot Marketplace apps, reported 2026-05-07.",
        "Corroboration for the change is 1 outlet: HubSpot's own developer communications.",
        "HubSpot scores 25.0 visibility and rank 2 in DABYTE's SaaS & AI Tools AI Visibility Index as of 2026-07-28.",
        "Per-engine visibility is identical at 25.0 on OpenAI and 25.0 on Perplexity.",
        "HubSpot's commercial intent reading is 82, with a quadrant assignment of Niche (visibility gap).",
        "The measured visibility delta for HubSpot is +4.1; the event's decision-relevant window is 336 hours."
      ],
      "brands": [
        "HubSpot"
      ],
      "corroboration": 1,
      "sources": [
        "https://developers.hubspot.com/changelog/app-listing-and-app-certification-requirement-updates-for-may-2026"
      ],
      "ttl_hours": 336,
      "measurement": [
        {
          "rank": 2,
          "brand": "HubSpot",
          "delta": 4.1,
          "quadrant": "Niche (visibility gap)",
          "per_engine": {
            "openai": 25.0,
            "perplexity": 25.0
          },
          "visibility_score": 25.0,
          "commercial_intent": 82
        }
      ]
    },
    {
      "slug": "bamboohr-testing-creating-connections-fail-with-status-code-403",
      "title": "Zapier Resolved a BambooHR 403 Connection Failure",
      "url": "https://dabyte.ai/articles/bamboohr-testing-creating-connections-fail-with-status-code-403/",
      "published_at": "2026-07-31",
      "summary": "Zapier resolved an incident in which new BambooHR connections and reconnection attempts failed with HTTP 403 and an unclear authentication error, reported 2026-07-22 by one outlet, Zapier's own status channel. In DABYTE's SaaS & AI Tools AI Visibility Index measured 2026-07-28, Zapier ranks 5th with a 20.8% visibility score, split 8.3% on OpenAI and 33.3% on Perplexity, a 25-point per-engine gap, with commercial intent at 72.",
      "key_facts": [
        "Zapier marked the BambooHR connection issue resolved in a notice reported 2026-07-22.",
        "The failure returned HTTP status code 403 on new BambooHR connections and reconnection attempts.",
        "Corroboration count is 1: only Zapier's own incident channel reported the event.",
        "Zapier ranks 5th with a 20.8 visibility score in the SaaS & AI Tools AI Visibility Index, measured 2026-07-28.",
        "Per-engine share splits 8.3 on OpenAI and 33.3 on Perplexity, a 25-point gap.",
        "Commercial intent on Zapier's measured queries is 72; DABYTE places the brand in the Niche (visibility gap) quadrant."
      ],
      "brands": [
        "Zapier"
      ],
      "corroboration": 1,
      "sources": [
        "https://status.zapier.com//incidents/01KY2E7CQ16M9Z0E54HAB3C9K0"
      ],
      "ttl_hours": 336,
      "measurement": [
        {
          "rank": 5,
          "brand": "Zapier",
          "delta": 8.3,
          "quadrant": "Niche (visibility gap)",
          "per_engine": {
            "openai": 8.3,
            "perplexity": 33.3
          },
          "visibility_score": 20.8,
          "commercial_intent": 72
        }
      ]
    },
    {
      "slug": "scheduled-triggers-v2-now-run-scheduled-rules-on-the-tasks-already-in",
      "title": "Asana Extends Scheduled Triggers to Existing Tasks in V2",
      "url": "https://dabyte.ai/articles/scheduled-triggers-v2-now-run-scheduled-rules-on-the-tasks-already-in/",
      "published_at": "2026-07-31",
      "summary": "Asana announced Scheduled Triggers V2 on 2026-05-18, extending scheduled automation rules so they can act on tasks already present in a project rather than only newly created ones, following Scheduled Triggers V1 released in January. Asana holds rank 12 in the SaaS & AI Tools AI Visibility Index measured 2026-07-28, named in 8.3% of AI answers on both OpenAI and Perplexity, with commercial intent of 69 and a delta of 0.0.",
      "key_facts": [
        "Asana announced Scheduled Triggers V2 on 2026-05-18, allowing scheduled rules to act on tasks already present in a project.",
        "Asana's Scheduled Triggers V1 shipped in January, and the ability to act on existing tasks was the most cited follow-up request.",
        "Asana ranks 12 in the SaaS & AI Tools AI Visibility Index measured on 2026-07-28, with a visibility score of 8.3.",
        "Asana's per-engine answer share is 8.3 on OpenAI and 8.3 on Perplexity, with a delta of 0.0.",
        "Commercial intent for Asana-related queries is 69, placing the brand in the Niche (visibility gap) quadrant.",
        "Corroboration for the Scheduled Triggers V2 announcement is one outlet, Asana's own community channel; DABYTE assigns the event a 336-hour decision-relevance window."
      ],
      "brands": [
        "Asana"
      ],
      "corroboration": 1,
      "sources": [
        "https://forum.asana.com/t/scheduled-triggers-v2-now-run-scheduled-rules-on-the-tasks-already-in-your-project/1141375"
      ],
      "ttl_hours": 336,
      "measurement": [
        {
          "rank": 12,
          "brand": "Asana",
          "delta": 0.0,
          "quadrant": "Niche (visibility gap)",
          "per_engine": {
            "openai": 8.3,
            "perplexity": 8.3
          },
          "visibility_score": 8.3,
          "commercial_intent": 69
        }
      ]
    },
    {
      "slug": "retool-cloud-oauth2-resource-authentication-flow-failing-for-custom-do",
      "title": "Retool OAuth2 Custom Domain Failure: What the Data Shows",
      "url": "https://dabyte.ai/articles/retool-cloud-oauth2-resource-authentication-flow-failing-for-custom-do/",
      "published_at": "2026-07-31",
      "summary": "Retool reported an OAuth2 resource authentication failure affecting custom domains on Retool Cloud, identifying the issue at 17:05 UTC on 25 March 2026 and marking it resolved at 20:36 UTC, a gap of 3 hours 31 minutes. The event was carried by 1 source, Retool's own status channel, while DABYTE measures Retool at a 4.2% visibility score and rank 17 in the SaaS & AI Tools AI Visibility Index, with 8.3% share on OpenAI and 0.0% on Perplexity.",
      "key_facts": [
        "Retool identified the OAuth2 custom domain authentication issue at 17:05 UTC on 25 March 2026 and marked it resolved at 20:36 UTC, an interval of 3 hours 31 minutes.",
        "Corroboration for the event is 1: the only source is Retool's own incident channel (inc_retool).",
        "Retool scores 4.2 visibility at rank 17 in the SaaS & AI Tools AI Visibility Index, measured 28 July 2026.",
        "Retool's per-engine share is 8.3 on OpenAI and 0.0 on Perplexity.",
        "Commercial intent on queries naming Retool is 62; the brand sits in the Low performance quadrant with a delta of 0.0.",
        "DABYTE assigns the event a decision-relevance window of 336 hours."
      ],
      "brands": [
        "Retool"
      ],
      "corroboration": 1,
      "sources": [
        "https://status.retool.com/incidents/61f71m1m8thn"
      ],
      "ttl_hours": 336,
      "measurement": [
        {
          "rank": 17,
          "brand": "Retool",
          "delta": 0.0,
          "quadrant": "Low performance",
          "per_engine": {
            "openai": 8.3,
            "perplexity": 0.0
          },
          "visibility_score": 4.2,
          "commercial_intent": 62
        }
      ]
    }
  ]
}