| | Hello there. HubSpot's release notes, changelog and newsroom stayed quiet over the weekend, so today comes from the people running the platform. A retailer asks how to keep commerce webhooks flowing into workflows on Black Friday, sales leaders swap stage rules that keep forecasts honest, and admins hit the limits of webhook triggers and app ownership labels. In today’s newsletter, we’ll get into: - A retailer lost cart abandonment and order workflows last Black Friday when its store dropped webhook events, and replies suggest a queue in between.
- Sales leaders say a deal stage only counts when it carries a next step date and an assigned task, and some make those required to move a deal.
- Admins want to edit fields on a webhook workflow trigger after creation and to show a company name instead of a user on installed apps.
| |
|
| | 🛒 Will your store's webhooks keep up with HubSpot on Black Friday? An online retailer says last year its commerce platform dropped webhook events under Black Friday load, so cart abandonment sequences misfired and order confirmations lagged for hours while support chased buyers who had already sorted things out. Replies suggest a small queue between store and HubSpot that holds and retries events, and asking each platform how it buffers events at peak. 📉 A deal stage only counts when it forces a next step. A sales leader watched the forecast slip as reps left deals in proposal with no meeting and an empty next step date. Replies share fixes: require a next step date and an assigned task before a deal moves, use HubSpot's required properties on stage change, flag close dates pushed without a note, and name stages in the past tense, such as Demo delivered, so reviews stay unambiguous. | |
|
| | 🪝 Webhook workflow triggers are hard to change after setup. An admin using the When a webhook is received trigger says they cannot add fields or fully edit an event once it exists. They could not find documentation on adding fields without generating a new webhook URL, changing the match property later or authenticating incoming requests, and asked whether these are known limits. No answer yet, so plan the fields you need before you share the webhook address with another system. 🧩 Installed by a person who left? Admins want a company label. Many apps in the App Marketplace list show Installed by followed by an individual user's name. One admin asked whether that label can show the integration or the company account instead, so connections stay easy to find and maintain when people change roles or leave. The question is still open, and it is a good prompt to note who owns each integration today. | |
|
| | 🎓 Academy course stuck on a spinner? Try these checks first. Two learners say the Inbound Sales course will not open or its videos will not play, one with a 502 error in a private window. A community expert says the course loads fine on their end and suggests a supported browser (Opera is not on the list), the latest Chrome, extensions turned off, a cleared cache and a different device. | |
|
| | Three remote roles posted in the last two weeks, each linked to its own posting with the source named. Each posting is linked from the source named on its line, with the date it was posted. Check the details on the posting itself. | |
|
|
|
