What This Update Actually Is
When someone pastes a HubSpot link into Slack, Slack "unfurls" it: a small preview card appears below the link showing record details. Until now, that card showed a fixed set of properties HubSpot decided for you.
This update changes two things. First, admins can now configure which properties appear in those preview cards at the account level. Second, team members can edit supported property values directly inside the Slack preview. Those edits save back to HubSpot automatically, and all existing HubSpot permissions and property rules still apply.
It's a public beta as of the April 29, 2026 announcement, with a scheduled release date of May 27, 2026. Every account is already enrolled.
Why HubSpot Shipped This
Here's the pattern we see constantly across portals: a sales rep drops a deal link in a Slack channel, the unfurl card pops up, and half the properties shown are irrelevant to the conversation. Deal stage? Useful. Associated company revenue calculated from a custom rollup property only RevOps understands? Not useful in that channel.
The friction compounds when the data is wrong. Someone spots a bad value, opens HubSpot in a new tab, finds the record, edits it, comes back to Slack, and the conversation has moved on. That's a real context-switching tax that costs humans time and focus every single day.
HubSpot recognized that Slack is where many go-to-market teams already coordinate. Making the HubSpot data inside Slack both relevant and editable removes the tab-switching loop and keeps the conversation productive.
How to Use It Step by Step
- Confirm your Slack integration is active. Go to Settings, then Integrations, then Connected Apps in your HubSpot portal. The Slack app should show as connected.
- Find the link preview configuration. Inside the Slack integration settings, look for a section labeled something like "Link Preview Properties" or "Unfurl Settings." This is the new account-level control panel.
- Choose your properties per object type. Select which properties appear when a contact, company, deal, or ticket link gets shared. Pick properties that are genuinely useful in a quick-glance conversation, not an audit.
- Save your configuration. Changes apply account-wide immediately. Every team member in Slack will see the updated preview cards the next time a HubSpot link is shared.
- Test inline editing. Share a deal or contact link in a Slack channel. Click an editable field in the preview card. Make a change. Confirm it saves back to the record in HubSpot. If a field doesn't appear editable, check whether that property type is currently supported for inline editing.
- Verify permissions. Remind your team that inline edits respect HubSpot property permissions. A human without edit access to a property in HubSpot won't be able to edit it from Slack either.
What It Touches in Your HubSpot Strategy
This update is primarily a CRM data quality and workflow efficiency story, even though it lives inside a Slack integration. Here's where the ripple effects land.
Properties and data hygiene: the properties you choose to surface in Slack previews are a forcing function. You have to decide which fields are actually meaningful to a fast-moving conversation. That decision is a mini audit of your property architecture. If you can't name five properties that matter in a deal discussion, your property setup might need a look.
Key Takeaway
The properties you pick for Slack previews reveal which fields your team actually trusts. If you're not sure what to show, start with the five properties a rep would check before a follow-up call.
Permissions and access control: inline editing from Slack is only as clean as your HubSpot permissions structure. If your team has broad edit access in HubSpot today, that same access now reaches into Slack. Worth reviewing before you roll this out widely.
Sales workflows: deal-stage updates, owner reassignments, or next-step fields can now happen inside a Slack thread where the decision was actually made. That's fewer records left stale because the update "never made it back to HubSpot."
Service and support workflows: service teams sharing ticket links in Slack can now see priority, status, and owner in the preview and update them inline. This pairs well with the structured approach to customer success work we covered in our piece on
Service and support workflows: service teams sharing ticket links in Slack can now see priority, status, and owner in the preview and update them inline. This pairs well with the structured approach to customer success work we covered in our piece on HubSpot Onboarding Plans. When your team coordinates onboarding tasks in Slack, having editable ticket properties in the preview removes a meaningful layer of friction.
Data integrity: the fact that all edits respect HubSpot's existing property rules is the right design. Required fields stay required. Calculated properties stay read-only. That consistency matters, especially in portals where data hygiene is already a work in progress.
Key Takeaway
Inline editing from Slack is only as reliable as your HubSpot permissions setup. Before rolling this out to your full team, audit which humans have edit rights on the properties you plan to surface.
This update also complements recent CRM-side improvements to data quality. If you're already using tools like the Duplicate Similarity Score to keep records clean, customized Slack previews are one more layer of defense. When your team sees accurate, relevant data in the preview, they're less likely to create duplicate records or overwrite good data.
Who Should Care Most
This update has the most immediate value for:
- RevOps and HubSpot admins who want to control what data is visible and editable in collaborative channels without building new automations or workarounds.
- Sales teams that already coordinate deal reviews, hand-offs, or pipeline calls inside Slack and need the record data to be accurate and actionable without switching tabs.
- Customer success and service teams sharing ticket or contact links in support channels where quick triage matters.
- Growing companies on any HubSpot tier: because this is available to all hubs and all tiers, even teams on free or starter plans get access immediately.
The companies that benefit least are those where Slack and HubSpot are used by separate groups with no real overlap. If your sales team doesn't use Slack, this isn't urgent. But if Slack is your company's operating environment, this is a meaningful quality-of-life upgrade.
George's Take
“The best HubSpot updates are the ones that meet humans where they already are. Your team isn't going to leave Slack to update a deal stage if it takes four clicks in HubSpot. But if the right field is right there in the preview card? They'll update it. That's the version of CRM adoption that actually sticks.”
I've watched portal after portal struggle with stale deal data, and the root cause almost always comes back to friction. Humans don't skip updates because they don't care. They skip updates because the update requires leaving the context where the conversation just happened. This change doesn't just reduce friction. It removes the excuse. And when you pair it with a clean property architecture and a solid permissions structure, you're building a CRM that actually reflects reality. That's worth a few minutes of admin setup.
If your portal's property structure isn't ready to support this kind of inline editing, it's worth reviewing the most common setup mistakes that make these decisions harder. Our guide on the biggest HubSpot onboarding mistakes covers the property and permissions missteps we see most often, and how to fix them before they compound.
Want help deciding which properties to surface, auditing your permissions before this rolls out, or just making sure your HubSpot and Slack setup is dialed in? Book a strategy call with the Sidekick team and we'll walk through your portal together.
Frequently Asked Questions
How do I configure which properties show in HubSpot Slack link previews?
Go to your HubSpot portal settings, open the Slack integration, and look for the link preview or unfurl settings section. From there, you can choose which properties display for each object type, such as contacts, companies, deals, and tickets. These settings apply account-wide immediately after you save them.
Can anyone on my team edit HubSpot records directly from a Slack preview?
Only team members who already have edit permissions for a given property in HubSpot can edit it from a Slack preview. The inline editing feature respects all existing HubSpot permission settings and property rules. If a human can't edit a field in HubSpot, they can't edit it from Slack either.
Which HubSpot plans include customizable Slack link previews?
This feature is available to all hubs and all tiers, including free and starter accounts. It's part of a public beta that began rolling out May 27, 2026, and all accounts are automatically enrolled.
Which property types support inline editing from a Slack link preview?
HubSpot's release notes indicate that inline editing is available for supported property types. Not every property type is editable from the preview card. Calculated properties, for example, remain read-only. Testing a few key fields after setup is the fastest way to confirm which ones your team can edit directly in Slack.
Does customizing Slack link previews affect how records look inside HubSpot?
No. The preview configuration only controls what appears in the Slack unfurl card. Your record layouts, views, and property display settings inside HubSpot are not changed by this setting. It's a Slack-specific display configuration at the account level.
What's the difference between this update and the previous static Slack unfurls?
Before this update, HubSpot link previews in Slack showed a fixed set of properties chosen by HubSpot, and no editing was possible from Slack. Now, admins can select which properties appear, and team members with the right permissions can edit supported property values directly in the preview card without leaving the Slack conversation.
