You’ve got five email workflows running. Each one is perfectly reasonable on its own — a welcome series, a re-engagement campaign, a deal-stage nurture, a webinar follow-up, and a monthly newsletter. But there’s no single place that says “this contact should never receive more than X emails per day.”

HubSpot Enterprise has a frequency cap feature for this. Marketing Hub Pro does not. And the commonly suggested workaround — filtering on the “Last marketing email send date” property — only works per-workflow. It can’t enforce a combined limit across all your campaigns.

This is the gap Shared Throttle fills.

The Per-Workflow Problem

If you’re already using Daeda Essentials, you might know the Throttle V2 action. It’s great for rate-limiting a single workflow — you set how many records to release and how often, and it queues everything up.

But Throttle V2 creates a separate queue for each workflow action. If you have five workflows each throttled to 50 emails per hour, your actual combined send rate could hit 250 per hour. Each workflow is respecting its own limit while collectively blowing past the overall ceiling you actually care about.

What you need is one shared limit that all your email workflows feed into.

One Queue, Many Workflows

Shared Throttle works differently. Instead of configuring throttle settings inside each workflow, you create a named queue once in the Daeda Essentials settings page. That queue defines the combined rate — say, 50 emails every 15 minutes.

Then in each email workflow, you add the Shared Throttle action and select your queue from a dropdown. That’s it. Every workflow that references the same queue shares the same rate limit. If your welcome series sends 30 this interval, your re-engagement campaign can only send 20 before the cap kicks in.

Setting It Up

Step 1: Create the Queue

Open Daeda Essentials in your HubSpot portal, go to Settings, and click the Shared Throttle tab. Hit Create Shared Queue.

Fill in:

• Display Name — something descriptive like “Email Hourly Cap”
• Batch Size — how many emails per interval (e.g. 50)
• Every / Unit — the interval (e.g. 15 Minutes)
• Execution Days — leave blank for every day, or select Monday–Friday for business days only

Save it. The queue key is auto-generated from the name.

Step 2: Add to Your Workflows

In each email workflow, add a Shared Throttle action before the email send step. Select your queue from the dropdown.

Optionally set Execution Priority if you want certain contacts (higher-value leads, time-sensitive deals) to go first when the queue releases.

Repeat for every workflow that should share the limit. Done.

What This Gives You

• A hard cap across all campaigns — not per-workflow, across everything. 50 every 15 minutes means 50 total, no matter how many workflows are feeding in.
• No “Last email send date” gymnastics — you don’t need to build branch logic checking when the last email went out. The queue handles it.
• Business-day awareness — restrict sends to weekdays so your contacts aren’t getting emails on a Sunday morning.
• Priority control — high-value contacts go first when space opens up in the queue.
• One place to manage it — change the rate in Settings and every workflow that uses the queue picks up the change automatically.

Works on Any HubSpot Tier

Shared Throttle is available on all Daeda Essentials plans — Starter, Growth, and Enterprise. You don’t need HubSpot Enterprise or Marketing Hub Enterprise to get email frequency safeguards.

If the native frequency cap eventually comes to lower HubSpot tiers, great. Until then, this is a clean, reliable way to enforce it today.

Install Daeda Essentials — or learn more about how it works.