Confused about Products, Payments, Contacts, and Deals
SOLVE
I'm setting up what I thought would be a simple set of automations.
The client has an intake form for scheduling consultations. They have 2 types of consultations. I set a property for "which product" on the form that has a radio select for each call type.
It would be ideal to have the payment form on this form, but that isn't an option. So I went for conditional thank you messages or the ability to add ctas in the thank you message and that isn't an option. So now I need a thank you page to offer the different payment links so that the contact can click another button before actually paying. Which is bad flow but it's what we have to work with, I guess.
I have workflow set up to send the appropriate pay link to the contact based on their option, plus they will have the thank you landing page with the options.
But now I'm trying to simply move the deal they are associated with to the correct stage based on the product they choose. And this isn't possible?
Am I wrong? There is not way to perform workflow logic based on if a contact makes a purchase, buys a product, or interacts with products or payments? I can't just move a deal? everything I found says that, even though the client just signed up for $100/mo sales seats, and $850/mo marking pro hub, we now have to use zapier and/or a bunch of third party tools?
I can't add the product as a line item, what's the point of line items. I can't move a deal if a payment is made, that doesn't makes sense. I can't trigger a workflow based on if a contact uses a payment link. why? none of these products are connected in any useable automation way as far as I can tell. And it doesn't make any sense.
I'm just going to assume that I don't know what I'm doing and am missing something here, because otherwise what are we even doing here? The cost for HubSpot went from $100/mo/seat for the sales package to ugrading to $850/mo just to send some emails that look better than sequence emails, and now we need to buy some more upgrades just to have a connected flow from purchase to pipeline? or I'm missing the place on workflows where when a contact makes a payment I can move the associated deal one stage over? I really hope it's the latter because why does HubSpot even have a payment hub if not?
I might as well move them to stripe, a 3rd party form provide that integrates with stripe, an email provider that sends nice looking emails without the $850/mo price tag, and I can literally build 90% of HubSpot's pipeline functionality in Notion.so so it wouldn't take much effort to just move them away from HubSpot completely if they can't do the simple things that need to be done here.
Please tell me I'm wrong and that there is a clear and obvious way to simply move a deal based on payment activity that I am overlooking. I don't even care about not being able to dynamically add line items to a deal or any of the other common sense stuff that isn't possible without extra extensions or outside tools. I just need to move the deal object when the contact converts by paying for the product that is the point of the deal and the deal pipeline to begin with.
Confused about Products, Payments, Contacts, and Deals
SOLVE
hey @SamCBarth_LAIRE thank you. The confusion is in how everything is unlocked and available to stage under different hub trials, or the features show with a lock on them. But not payment related triggers, actions, or anything. I've worked with payments a few times before but they were already turned on. I'm trying to prove to a client that HubSpot can do what they are wanting to do and I'm currently having to say "trust me" while hoping I'm not wrong. We'll find out in a few days, either way. would be nice if the triggers and actions were at least visible or documented.
Confused about Products, Payments, Contacts, and Deals
SOLVE
There's not even a way to set tasks or anything regarding payments, as far as I can tell. So we can't even set a manual task to move the deal object. Someone just has to watch payments and wait for a new one then click through to the payment, click through to the contact, click through to the deal, then update the deal stage. ?. There is no way this is accurate.
Confused about Products, Payments, Contacts, and Deals
SOLVE
I finally got smart and asked AI if it's possible that the payment triggers and actions aren't showing in the workflow editor because we are in the approval process for the Payments feature. Claude says this is the case, that when Payments are approved and set up that this will cause the triggers and actions around payments to appear in workflows. I don't know if this is accurate, I can't find anything about this anywhere, but it really doesn't make sense that payments can't interact with workflows and the features being hidden without payments approval makes the most sense. I guess we will see in a few days.
Confused about Products, Payments, Contacts, and Deals
SOLVE
second opinion from chatgpt. I'm just going to trust this and wait the 2-3 business days before scrambling to finish this set up.
all of the subscription gated actions and triggers, aside from payments (and probably a few other objects) appear to be available in the workflow editor. If the subscription doesn't allow for a feature, there's a lock icon on the feature. click a locked feature takes you to an "upgrade" page with the appropriate HubSpot product required for that feature.
But payments (and probably other features) triggers and actions are completely hidden as if they don't exist and there's no signal or info on why. They just appear when you get approved for payments (hopefully)?
The client is on a 14 day trial for two different hubs. A trial is a good time to make sure a software is going to fit all of the required use cases. The approval process and delay is understandable. Complete obfuscation of the capabilities of this feature durring a trial critical to the decision making process is a little nuts. If this is even the case. I'm going based off of two different AI's opinions while doing my best to find any documentation that proves or explains what's possible with payments in workflows.