What are the best use cases for the new Services object in HubSpot?

[mohamedhamad]

I'm trying to take advantage of the new Services Object that's been recently released, and I'm not sure how to go about it. I love the idea of a service created can be associated to a contact, a company and a deal. But if i have a standard service that i would like to provide a customer, and potentially have a pipeline or automations behind it, there are no way (unless I'm missing something) to choose from a library of set services. 
Let's say i have 3 services, and i want to have an onboarding process for each one. And i sell one, let's say Blog Post Writing. I'd want to associate the service to the client i sold it to, the contact I'm communicating with, and the deal it was sold from. From there i can use the pipelines to trigger certain communications and keep track. 

but that scenario isn't straight forward, because there is no connection with the product library I'm using to sell Blog Post Writing in my deals/quotes line items.

Maybe I'm reading this all wrong, but I'm having a hard to wrapping my head around how to and when to best use it. 

Any ideas, or inspirations?

[Moderator Note: this post was reviewed for relevancy and optimized for clarity on October 21, 2025. Thank you for your contributions to the HubSpot Community!]

[MAlex3 · Accepted solution]

While there isn't a direct connection between Services Objects and the product library used in deals/quotes, here's a practical solution:

1. Create custom properties in the Services Object to define your standard services (like Blog Post Writing)
2. Use workflows to automatically create service records when deals close
3. Set up automations to associate the service with the relevant contact, company, and deal

For example, when a Blog Post Writing deal closes:

• A workflow creates a new service record
• It automatically associates with the contact, company, and deal
• This triggers your onboarding process

You can track this using service-specific pipelines and custom properties to maintain the connection with your product library.

[DanielZarick · Accepted solution]

Great question—you're generally thinking about it the right way.

You're correct: HubSpot's new Service object currently doesn't directly connect to the Product Library, so you can't select pre-built services directly from your deal line items.

However, there's a simple way to achieve a similar result by combining the Services object with Arrows onboarding templates and properties from Deals:

Here's a quick checklist you can follow:

• Create a single pipeline in the Services object to manage the delivery of all standardized services.

• Set up a dropdown property on the Deal record to specify the type of service sold (e.g., Blog Post Writing, SEO Audit).

• Automatically sync this property from the Deal record to the Service record upon creation to clearly identify and track the type of service (either copy it with a workflow or make a synced property on the Service record).

• Use Arrows templates to create standardized onboarding plans based on the selected service type, connecting these directly to your Service records.

• Leverage HubSpot workflows to automatically create a Service record and attach the correct Arrows onboarding template when a Deal is marked as Closed-Won.

• Automate communication and task management through HubSpot workflows based on Service object status updates and onboarding plan completion from Arrows.

This gives you clear visibility and automates the tasks.

Here's a quick rundown video showing exactly how you can set up the Services object integrated with Arrows: 👉 Watch our video guide on using HubSpot’s Services object with Arrows integration

HubSpot Marketplace: https://ecosystem.hubspot.com/marketplace/listing/digital-sales-rooms-by-arrows

[Moderator Note: added marketplace link]

[RMirsky]

This just doesn't make sense to me! Where does monthly billing and subscriptions live if we want sales to CLOSE DEALS but we need the billing to live SOMEWHERE?  Why not on the service?

[SealaB]

Hi @RMirsky -
 

I completely understand your frustration - I’m tagging in @DanielZarick  and @MAlex3  to see if they have found specific workarounds that they prefer, but also wanted to share a perspective on how the architecture is generally designed to handle this distinction.
 

Typically, Deals (along with Line Items and the Subscriptions/Invoices objects in Commerce Hub) remain the home for Billing, Revenue, and Closing. The Service object is specifically designed to track the Delivery, execution, or "fulfillment" of that work.
 

While it feels like they should be one and the same, separating them allows for distinct workflows.

This ensures your Service team has visibility into what was sold (and the billing context) without them having to manage the actual billing records, keeping the "Money" data clean for Sales and the "Work" data clean for Services. I'll check back in here to see if the experts have any other thoughts on this.

[DanielZarick · Accepted solution]

Great question—you're generally thinking about it the right way.

You're correct: HubSpot's new Service object currently doesn't directly connect to the Product Library, so you can't select pre-built services directly from your deal line items.

However, there's a simple way to achieve a similar result by combining the Services object with Arrows onboarding templates and properties from Deals:

Here's a quick checklist you can follow:

• Create a single pipeline in the Services object to manage the delivery of all standardized services.

• Set up a dropdown property on the Deal record to specify the type of service sold (e.g., Blog Post Writing, SEO Audit).

• Automatically sync this property from the Deal record to the Service record upon creation to clearly identify and track the type of service (either copy it with a workflow or make a synced property on the Service record).

• Use Arrows templates to create standardized onboarding plans based on the selected service type, connecting these directly to your Service records.

• Leverage HubSpot workflows to automatically create a Service record and attach the correct Arrows onboarding template when a Deal is marked as Closed-Won.

• Automate communication and task management through HubSpot workflows based on Service object status updates and onboarding plan completion from Arrows.

This gives you clear visibility and automates the tasks.

Here's a quick rundown video showing exactly how you can set up the Services object integrated with Arrows: 👉 Watch our video guide on using HubSpot’s Services object with Arrows integration

HubSpot Marketplace: https://ecosystem.hubspot.com/marketplace/listing/digital-sales-rooms-by-arrows

[Moderator Note: added marketplace link]

[jayraj_berde]

Is there a way to share a service record with external customer ? Say for onboarding

[shareilnariman · Accepted solution]

I'm not sure you can share the entire record, but we built Arrows to be the customer-facing extension of the service record in HubSpot (HubSpot themselves now use Arrows onboarding plans to manage that process as well).

Blog: Why HubSpot’s new service object is the best way to manage customer onboarding

If that is interesting, you can book a demo with our team to learn more about how Arrows might help you with that onboarding process! 

[noahriley]

How does this workflow maintain the connection to the product library?

[MAlex3 · Accepted solution]

While there isn't a direct connection between Services Objects and the product library used in deals/quotes, here's a practical solution:

1. Create custom properties in the Services Object to define your standard services (like Blog Post Writing)
2. Use workflows to automatically create service records when deals close
3. Set up automations to associate the service with the relevant contact, company, and deal

For example, when a Blog Post Writing deal closes:

• A workflow creates a new service record
• It automatically associates with the contact, company, and deal
• This triggers your onboarding process

You can track this using service-specific pipelines and custom properties to maintain the connection with your product library.