Updates blog — Monday, May 18, 2026

HubSpot Updates: May 15 to 18, 2026

Eight updates landed across Friday through Monday in HubSpot's product updates feed, and they cluster around a clear theme: post-sale tooling and external data access keep getting more capable. Two payment updates close longstanding gaps (one removes a payment processor requirement, the other opens up a public API for payment links), Onboarding Plans graduates to live for Service Hub, Stage Calculated Properties land on custom objects, and a Snowflake direct sync arrives for the data warehouse crowd. Smaller updates round out the window with workflow, UI, and admin improvements.

If you watched the show today, you already heard the conversation around three of these. If you did not: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Create Payment Records Without Payment Processing

You can now manually record external payments directly within HubSpot without enrolling in HubSpot Payments or Stripe. The update also supports importing external payments in bulk. Available across all hubs and tiers, this is in public beta.

Why it matters: Until this update, the payment object's full capabilities were gated behind enrolling in a payment processor. That gate kept a lot of teams out of the data they actually needed. Marketing event registrations paid via Square or PayPal, course purchases that ran through a separate platform, B2B invoices paid via wire: all of this lived outside the CRM. Now those records can exist as first-class payment objects, associated to contacts, deals, and the rest of the platform. The broader pattern here is that HubSpot is not trying to replace your accounting system. It is making sure the unified customer view actually includes whether someone paid you, regardless of how they paid.

For more details: Create payment records without payment processing public beta.

Onboarding Plans

Customer success teams can now plan, execute, and track onboarding and success projects in HubSpot with structured tasks, milestones, and reporting. A new Onboarding pipeline is created by default for new Service Hub customers, alongside a new Service Onboarding project type and five out-of-the-box reports covering project count by stage, time spent in each stage, plan versus actual timeline, status distribution, and engagement distribution. This is live for Service Hub Professional and Enterprise.

Why it matters: Onboarding Plans is the operational backbone of the post-sale story HubSpot has been building for months. Customer Success Rooms gives the customer a place to see their work. Onboarding Plans gives the CS team the project structure to manage it. The Service Onboarding project type is the connective tissue, because tasks on a project with that type automatically surface in the customer's room. For teams running onboarding through Asana, spreadsheets, or anything else built outside the CRM, this is the version that scales because the work lives next to the customer record.

For more details: Onboarding Plans live.

Stage Calculated Properties Available for Custom Objects

Custom objects now have stage calculated properties that automatically track how records move through pipeline stages. Six new properties are available: date entered stage, date exited stage, latest time in stage, cumulative time in stage, time in current stage, and date entered current stage. This is live across the Enterprise tiers (Content, Marketing, Data, Sales, Smart CRM, and Service).

Why it matters: These properties have existed for years on deals, tickets, and projects. The newness is that they are now available on custom objects, which closes a real reporting and automation gap for anyone running pipeline workflows on objects outside the standard CRM model. Stage analytics on custom objects open up bottleneck identification, time-based automation, and pipeline health reporting that has been a manual lift up to now. The most underappreciated benefit: anyone who has ever exported properties from a twenty-pipeline custom object setup has been getting twenty separate time-in-stage versions, with no way to consolidate. The new calculated properties fix that at the source.

For more details: Stage calculated properties available for custom objects live.

Objects Now Recommended for Data Sync Spreadsheet Apps

HubSpot now analyzes the table and column names from Airtable, Smartsheet, Kintone, Monday.com, or Notion and automatically recommends which HubSpot object to sync the data into. This is in public beta across all HubSpot products and tiers, with super admin or partner admin permissions required to configure.

Why it matters: The fix here is small (auto-mapping a spreadsheet sync to the right object), but it fits a pattern that has been showing up across several recent releases. HubSpot is putting an intelligent layer between users and their external data, so the human is not the one guessing where everything goes. Combined with the agentic automation workspace coming next, the direction of travel is clear: wherever you are in HubSpot, the platform notices what you are trying to do with external data and offers a smarter next step. That is a real shift from "you figure it out" to "we have a recommendation."

For more details: Objects recommended for data sync spreadsheet apps public beta.

Workflow Action to Change Contact Participant State for a Marketing Event

A new workflow action lets you automatically update a contact's participation state to Registered, Attended, or Cancelled for manually created marketing events in HubSpot. The previous version of this action only supported marking contacts as Registered, which meant tracking attendance or cancellations required manual updates or external workarounds. This is in public beta for Marketing, Data, Sales, and Service Hub Professional and Enterprise, as well as Smart CRM Professional and Enterprise.

Why it matters: The full event participation journey now lives inside the workflow tool: registration through attendance through cancellation. If you have been managing marketing events in a spreadsheet, this is the nudge worth taking seriously. The workflow side is built out, the reporting side connects, and the data ends up where the rest of your marketing automation already lives. Worth flagging that this is for manually created marketing events, which is the path most teams take when running webinars or in-person events directly through HubSpot.

For more details: Workflow action to change contact participant state for a marketing event public beta.

Sync Data from Snowflake (Including Multi-Object Sync)

You can now sync data from Snowflake directly into HubSpot with data preview, multi-object syncing with associations, and auto-mapping. The sync brings warehouse data into HubSpot workflows, lists, reports, and Breeze AI. This is in public beta for HubSpot Data Hub Enterprise and Smart CRM Enterprise.

Why it matters: The most valuable customer data in mature companies often lives in the warehouse, not the CRM. Usage metrics, billing data, health scores, enrichment fields, calculated lifetime value: that data has historically required either a custom integration or a one-way reverse ETL pipeline to make it usable in HubSpot. A direct Snowflake sync with multi-object support and association mapping changes the operational picture for Data Hub Enterprise customers. Warehouse data becomes available wherever HubSpot users are already working. For revenue operations teams running on a Snowflake-first data strategy, this is the kind of release that determines whether HubSpot stays in or moves to the center of the stack.

For more details: Sync data from Snowflake public beta.

Payment Links API

Developers and partners can now programmatically create, retrieve, and manage HubSpot payment links via a public API. Optional line items and editable quantities are not supported during the private beta. This is available across all hubs and tiers for accounts enrolled in the beta.

Why it matters: The clearest use case is businesses running B2C through a platform like Shopify that also need to support B2B. Special pricing agreements, custom configurations, account-specific discounts: those fall outside what a B2C front face is built for. HubSpot CRM data plus product configuration infrastructure plus a payment link API is a clean way to fill the gap without paying for a separate B2B add-on. The broader signal here matches the rest of this release window. Public API access to commerce data keeps expanding, and the days of "we can't get the data out of HubSpot" are functionally over.

For more details: Payment Links API private beta.

Updated Report Quick Edit and Filter Interface on Dashboards

The report quick edit and filter interface on dashboards has been updated for a cleaner, more consistent experience that matches the rest of the HubSpot UI. This is in public beta across all hubs and tiers.

Why it matters: Small UI updates compound. The quick edit and filter interface on dashboards is one of those surfaces users touch dozens of times a day, and inconsistency between this view and the rest of HubSpot has been a low-grade friction for a long time. Bringing it in line means fewer extra clicks, fewer "where did that filter go" moments, and a slightly faster path to the answer the user is looking for.

For more details: Updated report quick edit and filter interface on dashboards public beta.

Key Takeaways and Next Steps

Post-sale tooling keeps maturing: Onboarding Plans going live, Customer Success Rooms continuing to evolve, and payment records becoming accessible without a processor requirement all point at the same shift. HubSpot is investing in the part of the customer relationship that comes after the deal closes, and the tools are increasingly capable enough to run real CS operations from inside the platform.

External data is getting easier to bring in: Three updates in this window touch on data ingestion in different ways. Snowflake Direct Sync handles the warehouse story. Objects Recommended for Data Sync Spreadsheet Apps handles the spreadsheet story. The Payment Links API handles the developer story. Different audiences, same direction. If your team has been holding off on a CRM-centered data strategy because the pipes felt incomplete, this is a good moment to revisit.

Stage calculated properties on custom objects is overdue, and welcome: Anyone running pipeline workflows on custom objects has been doing the calculated-properties work manually for years. Closing this gap quietly opens up automation and reporting use cases that have lived on the "not worth the lift" list. Worth a review of your custom object pipelines to see what is now possible.