# hubspot Published articles for hubspot. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Reimagining advertising with AI DevFeed: [Reimagining advertising with AI]() Original publisher: [Read original article]() Published: 2026-09-16T13:00:00Z Content type: release Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [ChatGPT](), [hubspot](), [Shopify]() Tags: [advertising](), [agents](), [ai](), [chatgpt](), [hubspot](), [integrations](), [openai](), [plugin](), [product](), [shopify](), [sponsored]() ### AI overview OpenAI introduces AI-powered advertising features in ChatGPT, including Sponsored Agents that let users converse with select business-sponsored agents after viewing an ad. It also adds prompt-based campaign tools and AI creative tools, plus integrations with HubSpot and Shopify. ### Source excerpt Explore new AI-powered advertising experiences from OpenAI, including Sponsored Agents, tools for marketers, and integrations with HubSpot and Shopify. ## Three ways to let an AI agent call third-party APIs on behalf of a user DevFeed: [Three ways to let an AI agent call third-party APIs on behalf of a user]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-27T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [AI Agent](), [OAuth](), [Security]() Tags: [agent](), [ai-agent](), [apis](), [hubspot](), [linear](), [oauth](), [patterns](), [proxy](), [security](), [slack](), [third-party](), [tokens]() ### AI overview This article explains three patterns for letting an AI agent access third-party APIs on a user's behalf: storing OAuth credentials yourself, fetching tokens at runtime, or using a proxy that keeps tokens out of the agent-controlled runtime. It compares their operational and security implications and recommends choosing based on where the code runs and the system's requirements. ### Source excerpt Store the token yourself, fetch it at runtime, or never hold it at all. Where the credential ends up in each pattern, what each one costs, and how to pick without guessing. ## Incident Report: July 22, 2026 DevFeed: [Incident Report: July 22, 2026]() Original publisher: [Read original article]() Author: Karina Devadoss Published: 2026-08-14T17:06:07Z Content type: news Language: en Sources: [HubSpot]() Topics: [incident](), [configuration](), [bug](), [health checks](), [client]() Tags: [2026](), [bug](), [change](), [configuration](), [customers](), [engineering](), [errors](), [europe](), [health-checks](), [hubspot](), [incident](), [memory](), [network](), [performance](), [report](), [services]() ### AI overview HubSpot reports that a configuration change triggered a latent defect in a core CRM service, causing European customers to experience CRM access disruptions for approximately 55 minutes on July 22, 2026. No data was lost, and non-European regions operated without interruption. ### Source excerpt Customers in Europe faced CRM access issues on July 22 due to a configuration change. Learn about the incident, its impact, and our commitment to improved reliability. ## The 9 best tools for your early-stage startup tech stack in 2026 DevFeed: [The 9 best tools for your early-stage startup tech stack in 2026]() Original publisher: [Read original article]() Author: Alan McGlinchey Published: 2026-08-04T08:00:51Z Content type: article Language: en Sources: [The Intercom Blog]() Topics: [Software](), [Artificial Intelligence](), [migration](), [Claude](), [systems](), [Claude Code]() Tags: [ai](), [ai-tools](), [aws](), [best-practices](), [claude-code](), [code](), [customer-engagement](), [fin](), [growth](), [how-to](), [hubspot](), [integrations](), [migration](), [partner](), [pricing](), [startup](), [startup-advice](), [startups](), [stripe](), [tech](), [tech-stack](), [technology-stack](), [tools]() ### AI overview A guide to choosing a foundational technology stack for early-stage startups, emphasizing scalable, AI-powered tools, manageable costs, integrations, and problem-focused selection. ### Source excerpt Learn how to create a foundational tech stack for your high growth and early-stage startup - starting with these top tools. ## Sales workflows with ChatGPT Work DevFeed: [Sales workflows with ChatGPT Work]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [codex](), [Slack]() Tags: [app](), [chatgpt](), [codex](), [crm](), [customer](), [deals](), [hubspot](), [openai-academy](), [sales](), [salesforce](), [slack](), [strategy](), [tools](), [work](), [workflows]() ### AI overview A practical overview of how sales teams use ChatGPT Work to turn CRM data, customer conversations, internal discussions, and deal signals into account briefs, meeting preparation, forecast reviews, account plans, follow-ups, and deal-risk analysis. ### Source excerpt Learn practical ChatGPT Work workflows for pipeline briefs, meeting prep, account plans, forecast reviews, and deal diagnosis. ## Fin extends Service Agent support to HubSpot and Freshworks DevFeed: [Fin extends Service Agent support to HubSpot and Freshworks]() Original publisher: [Read original article]() Author: Paul Adams Published: 2026-06-09T16:45:42Z Content type: release Language: en Sources: [The Intercom Blog]() Topics: [hubspot](), [Support]() Tags: [agent](), [apis](), [cli](), [customer-experience](), [docs](), [fin](), [fin-for-freshdesk](), [fin-for-hubspot](), [helpdesk](), [hubspot](), [integrations](), [mcps](), [news-updates](), [platform]() ### AI overview Intercom announces that Fin can operate as a Service Agent on top of HubSpot and Freshworks, allowing customers to integrate it without migrating from their existing helpdesk. The article also describes Fin's open-platform approach, including APIs, MCPs, CLI access, and public documentation. ### Source excerpt Fin can be used as a Service Agent on top of HubSpot and Freshworks, meaning you can use the world's best Agent without migrating off your helpdesk. ## Turning support tickets into organization-wide intelligence DevFeed: [Turning support tickets into organization-wide intelligence]() Original publisher: [Read original article]() Author: Idit Matas Published: 2026-05-04T10:35:03Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Support](), [Artificial Intelligence](), [data](), [hubspot](), [Slack](), [bug]() Tags: [agents](), [ai](), [bug](), [hubspot](), [jira](), [slack](), [support](), [workflows]() ### AI overview The article explains how Port built an internal Support AI Hub on its Agentic Engineering Platform to analyze support-ticket information. It describes agents for ticket summaries, engineer handovers, escalations, health checks, and monthly trend analysis using data from systems including HubSpot, Zendesk, Jira, and Slack. ### Source excerpt Learn how to turn support tickets into organization-wide intelligence to uncover trends, improve workflows, and drive decisions. ## HubSpot's 37-Minute Lesson in Why HTTP 200 Can Lie DevFeed: [HubSpot's 37-Minute Lesson in Why HTTP 200 Can Lie]() Original publisher: [Read original article]() Author: Byte-Sized Design Published: 2026-04-22T16:34:15Z Content type: article Language: en Sources: [Byte-Sized Design]() Topics: [hubspot](), [HTTP](), [Availability](), [Monitoring]() Tags: [availability](), [http](), [hubspot](), [monitoring](), [permission]() ### AI overview The article examines a HubSpot access incident in which a permission check passed while users were locked out, showing that an HTTP 200 response and conventional availability monitoring may not reflect whether users can actually access a service. ### Source excerpt The permission check that passed, the users who were locked out, and what monitoring for "availability" actually misses ## HubSpot Incident Report: February 25, 2026 DevFeed: [HubSpot Incident Report: February 25, 2026]() Original publisher: [Read original article]() Author: Shilpa Varma Published: 2026-03-20T17:48:30Z Content type: article Language: en Sources: [HubSpot]() Topics: [incident](), [ui](), [Access Control](), [Authorization](), [configuration]() Tags: [access-control](), [analysis](), [configuration](), [deployment](), [engineering](), [errors](), [health-checks](), [http](), [hubspot](), [incident](), [issue](), [monitoring](), [report](), [user-interface]() ### AI overview HubSpot reports a February 25, 2026 service disruption that blocked access to certain contact, company, order, and project-based workflows in the user interface. Backend workflow automations continued to run normally, and no customer data was lost. The incident resulted from permission scopes being deployed without corresponding production role assignments. ### Source excerpt On February 25, 2026, HubSpot experienced a service disruption affecting user access to specific types of workflows within our user interface. All backend workflow automations continued to execute normally without interruption - no automations were delayed, missed, or lost. We have completed a thorough analysis of this incident and are implementing targeted safeguards to prevent this class of failure from recurring. ## ClickHouse Fivetran Destination moves to Beta DevFeed: [ClickHouse Fivetran Destination moves to Beta]() Original publisher: [Read original article]() Author: Luke Gannon Published: 2026-02-25T00:00:00Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [data](), [Software as a service](), [audit trail](), [Cloud](), [No-code]() Tags: [2025](), [analysis](), [analytics](), [api](), [apis](), [applications](), [architecture](), [audit-trail](), [business](), [clickhouse](), [cloud](), [code](), [data](), [data-engineering](), [go](), [hubspot](), [integration](), [kafka](), [no-code](), [object-storage]() ### AI overview The Fivetran destination for ClickHouse Cloud has entered beta with History Mode, which adds Slowly Changing Dimension Type 2 support. Instead of overwriting changed records, it preserves each version for audit trails, point-in-time analysis, and trend reporting. The release also supports compute-compute separation for isolating ingestion workloads. ### Source excerpt The Fivetran destination for ClickHouse Cloud is now in beta! ## Cloud Coding Agents at HubSpot DevFeed: [Cloud Coding Agents at HubSpot]() Original publisher: [Read original article]() Author: Stephan Lensky Published: 2026-01-23T15:59:04Z Content type: article Language: en Sources: [HubSpot]() Topics: [hubspot](), [AI-assisted coding](), [Claude Code](), [Self-hosted](), [GitHub](), [pull-requests](), [developer tooling](), [Code review]() Tags: [ai](), [claude-code](), [code-review](), [coding-agents](), [developer-tooling](), [engineering](), [github](), [hubspot](), [self-hosting]() ### AI overview This article explains how HubSpot built and deployed a self-hosted platform for cloud coding agents, integrating them with internal developer tooling, infrastructure, and GitHub. It describes their use of autonomous agents for planning, implementation, and code review, including more than 7,000 merged AI-generated pull requests and over 50,000 human-authored pull requests reviewed by agents. ### Source excerpt This post is the second in a series about empowering product, UX, and engineering teams with AI, especially in the context of writing code. Read the first post about scaling AI adoption here! ## HubSpot Incident Report for October 20, 2025 DevFeed: [HubSpot Incident Report for October 20, 2025]() Original publisher: [Read original article]() Author: Kartik Vishwanath Published: 2025-11-11T17:09:36Z Content type: news Language: en Sources: [HubSpot]() Topics: [incident](), [Amazon Web Services](), [Cloud](), [Resilience](), [Amazon Simple Queue Service (SQS)](), [Amazon EC2](), [AWS IAM](), [DynamoDB]() Tags: [amazon](), [amazon-sqs](), [analysis](), [aws](), [cloud](), [data](), [database](), [distributed](), [dynamodb](), [ec2](), [engineering](), [failover](), [hubspot](), [iam](), [improvements](), [incident](), [message-queue](), [outage](), [recovery](), [report](), [resilience]() ### AI overview HubSpot reports that a severe AWS outage in the us-east-1 region on October 20, 2025 disrupted multiple product features and affected third-party vendors. The incident caused failures involving DynamoDB, IAM, SQS, and EC2, and degraded HubSpot's TQ2 background task processing. HubSpot says it completed an analysis and is implementing resilience improvements. ### Source excerpt On October 20, 2025, HubSpot experienced a significant service disruption affecting multiple product features due to a severe AWS outage in the us-east-1 region. While our infrastructure remained intact, the widespread nature of the cloud provider failure impacted both our services and critical third-party vendors we rely on. We've completed a thorough analysis of this incident and are implementing comprehensive improvements to strengthen our resilience against future cloud provider disruptions.