Most teams that come to me with a HubSpot problem have the same thing in common: they have workflows. They just don’t have the right ones.

There are teams out there with 80 workflows running and a pipeline that still makes no sense. And there are teams with five workflows that have cut manual work in half and actually trust their data. The difference isn’t volume. It’s whether the automation is solving a real problem in your sales process or just adding noise.

After building over 250 workflows across companies at different stages, a few keep showing up as genuinely foundational. Not flashy. Not complex. Just reliably useful from day one.

Here are the five I’d set up before anything else.

1. Past Close Date Alert

This is the one most teams don’t have, and it causes more pipeline reporting headaches than almost anything else.

Every deal in HubSpot has a close date. In theory, your team updates it as the deal progresses and timelines shift. In practice, deals slip, conversations get delayed, and close dates stop reflecting reality. Before long your pipeline report is showing $200k closing this month when half of it is actually stalled.

The fix is simple: a workflow that detects when a deal’s close date has passed and the deal is still open, then sends an internal notification to the deal owner, and optionally their manager, flagging it for review.

The trigger is straightforward: close date is in the past, deal stage is not Closed Won or Closed Lost. Set it to check daily. When it fires, send the rep a task or email reminding them to update the close date or move the deal.

This workflow does two things. First, it keeps your forecast clean without requiring a manager to manually audit every open deal every week. Second, it creates a natural accountability loop — reps know the system will flag stale close dates, so they’re more likely to keep them current in the first place.

It sounds almost too simple. It consistently makes a significant difference.

2. Meeting Booked Confirmation and Introduction

When a prospect books a meeting with one of your reps, they’ve done something meaningful. They’ve given you time on their calendar. Most teams acknowledge this with a generic calendar confirmation and nothing else.

This workflow does more. When a meeting is booked, it automatically sends a short, warm email and an SMS from the rep to the prospect. Not a confirmation of the meeting time, which the calendar invite already handles. Something that actually prepares them for the conversation.

A good version of this email includes who they’ll be speaking with, what to expect on the call, and maybe a question or two to get them thinking in advance. It sets expectations, makes the rep feel human before the call starts, and reduces no-shows because the prospect feels like they’re talking to a real person rather than booking a slot in a machine.

The trigger is a meeting being created and associated with a contact record. The actions are a short delay — a few minutes to make sure the booking is confirmed — then the email sends from the rep’s connected inbox. If you have the rep’s mobile number stored and SMS is configured, a brief text reinforces it.

Teams that run this workflow consistently see better show rates and better-prepared prospects. The call itself is more productive because the prospect has already started thinking about what you asked them.

3. No-Show Re-Engagement

No-shows happen. A prospect misses a call, life gets in the way, and if nobody follows up immediately they’re likely to fall off completely. Most reps intend to follow up. Many don’t, or they do it inconsistently.

This workflow removes the inconsistency. When a meeting outcome is marked as No-Show, the contact is automatically enrolled in a short re-engagement sequence — usually two or three emails spaced a few days apart, each with a simple one-click link to rebook.

The tone matters here. The first email should be understanding and low-pressure: things happen, here’s a link to find a time that works better. The second, a few days later, can be slightly more direct. The third, if you include one, is a gentle close — if the timing isn’t right, no problem, here’s how to reach us when it is.

This workflow works because it catches the contact at the exact moment they’re most likely to rebook — right after the missed meeting, when the original interest is still fresh — rather than days later when a rep finally gets around to following up manually.

One important detail: make sure the sequence stops automatically if the contact books a new meeting or replies to any of the emails. HubSpot handles this natively when the workflow is set up correctly, but it’s worth double-checking before you turn it on.

4. Deal Stagnation Alert

Every pipeline has deals that stop moving. Sometimes there’s a legitimate reason — the prospect is evaluating internally, budget approval is pending, a key stakeholder is on holiday. Sometimes the deal is just stuck and nobody has noticed.

A deal stagnation workflow surfaces those deals before they become lost opportunities. The trigger is a deal remaining in the same pipeline stage for longer than a defined number of days — typically seven to fourteen, depending on your average sales cycle — with no recent activity logged.

When it fires, it creates a task for the deal owner to review and take action, and optionally sends a notification to their manager. The goal isn’t to create a culture of surveillance. It’s to make sure that when a deal goes quiet, someone knows about it quickly enough to do something useful.

The threshold you set matters. If your average deal moves stages every five days, flagging at fourteen gives reps enough room while still catching genuine stalls. If your sales cycle is longer, adjust accordingly. You can also layer in a condition that only fires if no activity — calls, emails, meetings, notes — has been logged in that period, which reduces false positives for deals that are active but slow-moving by design.

This workflow, combined with the past close date alert, gives you two layers of pipeline hygiene that catch most of the problems that make forecasting unreliable.

5. Closed Won to CS Handoff

The moment a deal closes is also the moment a lot of important context is at risk of getting lost. What did sales promise? What were the main pain points the customer mentioned? What does success look like from their perspective? If none of that gets handed off to the customer success or onboarding team, the customer’s first experience after signing is often a generic kick-off call with someone who knows nothing about why they bought.

This workflow closes that gap. When a deal is moved to Closed Won, it automatically creates a task for the assigned CS or onboarding rep, sends them an internal notification with key deal properties pulled in — company name, deal amount, the rep who closed it, any relevant notes — and optionally fires an introductory email from the CS rep to the customer welcoming them and setting expectations for the onboarding process.

The handoff email doesn’t need to be elaborate. Something that acknowledges the customer by name, references what they’re looking to achieve, and tells them exactly what happens next is enough. The bar is just: make the customer feel like someone was expecting them, not like they fell into a queue.

If your onboarding has specific steps that vary by deal type, you can add conditional branches — different task sequences for different product lines, company sizes, or whatever properties matter in your process. But even a simple version of this workflow is significantly better than no workflow at all.

A Note on Keeping Workflows Simple

The most common workflow mistake isn’t building too few — it’s building ones that are too complex to debug when something goes wrong. Each of the five above does one thing clearly. The trigger is obvious, the action is obvious, and when a rep asks “why did this fire?” you can explain it in a sentence.

As your HubSpot setup matures, you’ll find plenty of opportunities to add more sophisticated automation. But these five give you the foundation: a clean pipeline, consistent follow-up, no deals slipping through the cracks, and a handoff process that doesn’t make new customers feel forgotten.

If you want to understand how workflows fit into the broader picture of how your HubSpot instance should be structured, the HubSpot setup guide covers the full sequence from pipeline design through automation. And if your CRM data is inconsistent enough that you’re not sure automation would actually help, the post on why sales teams don’t update the CRM is worth reading first — because workflows built on bad data tend to automate the wrong things.

If you want help building any of these — or figuring out which ones to prioritize for your specific sales motion — let’s talk.