Home / Insights / Operations and security
Can you work out how many times a month your automations will run before you sign?
Yes, you can. With the actual volumes for the past month, 7 steps will give you your monthly consumption. What you cannot do with every vendor is check afterwards whether that figure was right: of the 4 vendors, only monday.com lets you reconcile it once you have signed.
There is a second point. Even when the estimate holds, you can be blocked somewhere else. HubSpot caps how many automations you build, Asana caps the rules in 1 project, and Shopify caps how much it processes in 1 second. Alongside the run-count estimate, you need to check these 3 ceilings.
(The monthly run limits themselves are covered in a separate article, Will your automation run count be enough?)
These 7 steps give you the estimate
| Step | What to do | Where it goes wrong |
|---|---|---|
| 1 | Write out the work you want to automate, 1 item on 1 line | At the granularity of "when a quote is approved, notify the billing team" |
| 2 | Add "how many times this happens in 1 day" to each line | Actual volume for the past 1 month ÷ 30. Do not guess |
| 3 | Add "how many actions 1 run consumes" to each line | For a notification it is the number of recipients; for creating an item it is "1 for the creation + the number of columns you set" |
| 4 | For each line calculate volume × actions × 30, then total it | This is your expected monthly consumption |
| 5 | Total the lines that reach outside services (Slack, Gmail and so on) separately | monday.com counts the automation quota and the integration quota separately. Mixing them leads to the wrong verdict |
| 6 | Multiply the total by 1.5 | Not a vendor recommendation, but the safety margin this article applies |
| 7 | If it goes above 70% of the limit, estimate against the plan 1 level up | As above. This is the headroom that absorbs peak periods and misfires caused by misconfiguration |
Steps 6 and 7 are not vendor specifications. They are this article's rule of thumb for absorbing peak periods, re-runs and misfires caused by misconfiguration.
Take an example. An automation that creates a deal (1 item creation + 3 columns = 4 actions) fires 20 times in 1 day, and a notification to 6 subscribers fires 20 times in 1 day: 20×4×30 = 2,400 and 20×6×30 = 3,600, for a total of 6,000. Multiply by 1.5 and you have 9,000 actions per month. On monday.com, Standard (250) is out of the question, and this uses 36% of Pro (25,000). If this company picks Standard, it stops on the opening day.
In terms of what actually leaves the company at signing, Standard with 5 seats on annual billing is $12×5×12 = $720 a year, and Pro with 5 seats on annual billing is $19×5×12 = $1,140 a year. The gap is $420 a year. For a company expecting 9,000 actions, there is no sense in hesitating over a plan for that $420.
Can you check after signing whether the estimate was right?
| How consumption is visible | Buying more | What this means for you | |
|---|---|---|---|
| monday.com | The "Usage" tab in Autopilot Hub, or "Usage Stats" in the admin area. A progress bar, projected consumption to the end of the period, a breakdown by the boards, creators and automations that consume the most, and CSV export | We could not find the price of additional actions stated on the vendor's own pages (the guidance points to upgrading to a higher plan) | The only vendor of the 4 where you can reconcile the estimate against measured usage |
| HubSpot | API call logs for each private app | The "API Limit Increase" add-on adds 1,000,000 calls in 1 day, up to 2 per account. We could not find the price stated | What you see is the API, not "how many times an automation ran" |
| Asana | AI Studio credits by creator and by workflow in the admin console | Buy a usage pack or pay as you go. The overage cap can be set to $0. We could not find the unit price stated | Ordinary rules are unlimited, so there is no meter to count in the first place |
| Shopify | Individual run history kept for 14 days | We could not find this stated on the vendor's own pages | History, not aggregation |
Checked on each vendor's own help pages, August 2026. Sources are listed at the end of this article.
There is 1 thing to read here. monday.com is the only one where you will notice that your estimate was wrong. On the other 3, the run count will not stop you, but you cannot see your consumption either. For Asana, we could not find on the vendor's own pages how many credits 1 run consumes. Assume that consumption for automation involving AI cannot be estimated before you sign.
Where do the ceilings other than run count sit?
HubSpot's ceiling is the number of workflows. Marketing, Sales and Service Hub allow 300 on Professional and 1,000 on Enterprise; Data Hub allows 400 and 1,100; and with multiple subscriptions the vendor states that the limit is determined by the subscription with the highest limit. If you split workflows finely by department or by product, this is where you are blocked, not on run count.
Asana's runs are unlimited, but the rules in 1 project are fixed at 50. Because the cap is per project, you can raise the total by splitting projects. Asana's "unlimited" stops working only when you concentrate automations in 1 large project.
On Shopify, what blocks you first is not the number of workflows (1,000) but the rate per 1 second. The company limits its API in a unit it calls "points": Basic and Grow have 100 points per second, Advanced 200, Plus 1,000. Ordinary order processing will not hit this, but a design that bulk-updates inventory overnight will run short. The dividing line is not the monthly total but how much arrives at once. Flow's "send HTTP request" action is also limited to Grow and above, so if external integration runs through Flow, Basic is not an option.
monday.com has now added a ceiling on the number of workflows as well. From August 10, 2026, active workflows that can be published with the AI workflow builder are limited to 3 on Standard, 20 on Pro and 250 on Enterprise.
Who each of these does not suit
monday.com does not suit a company that wants to start running without making an estimate. The flip side of its strong visibility is a design that stops you unless you count. Once you reach the limit, adding and editing automations is blocked, and 72 hours after that runs stop.
Asana does not suit a company whose finance function wants a monthly figure for automation consumption. Because ordinary rules are unlimited there is no consumption meter, and the only thing you can track is AI Studio credits.
HubSpot Professional does not suit an operation that splits workflows finely by department or by product. You are blocked by that count of 300.
Shopify Basic does not suit a store that wants automated integration with outside services. "Send HTTP request" is limited to Grow and above, so the feature itself is unavailable.
If you are unsure
HubSpot and Shopify are not substitutes for monday.com and Asana; check them as the ceilings that apply when you run them alongside. Amounts are in US dollars, excluding tax; counts are per 1 billing period (month). Source: each vendor's own help pages (checked August 2026).
Stop after steps 1 to 4 and show that figure to the sales team. Ask "we expect 9,000 actions a month — is this plan enough?" and the answer will cover the ceilings other than run count as well: workflow counts, rates and credits. Sign without an estimate, assuming it will probably be enough, and you will be counting only after everything has stopped.
Sources (checked August 2026)
- monday.com: Automations and integrations pricing (Standard 250 automations / 250 integrations, Pro 25,000 each, Enterprise 250,000 each, separate quotas, upgrade to a higher plan when you go over) / Automation and Integration actions (definition of 1 action, column mapping, editing blocked at 100%, grace period of 72 hours) / Tracking Account automation, integration, and workflow usage (Usage tab, progress bar, projected consumption, breakdown, CSV) / The AI workflow builder (active workflow limits from August 10, 2026) / Pricing page ($12 / $19)
- Asana: Rules (50 rules in 1 project, 20 actions in 1 rule) / AI Studio admin (usage shown in the admin console) / Asana AI requests and usage allocation (usage packs, pay-as-you-go, overage cap of $0)
- HubSpot: Workflows FAQ (Professional 300 / Enterprise 1,000, Data Hub 400 / 1,100, the highest limit applies with multiple subscriptions) / API usage details (+1,000,000 calls with the add-on, up to 2, logs for private apps)
- Shopify: Shopify Flow (sending an HTTP request requires Grow or above) / Flow usage limits (1,000 workflows) / Monitoring workflow runs (14 days of history) / API rate limits (Standard 100 / Advanced 200 / Plus 1,000 points per second)
All amounts are in US dollars, excluding tax, and counts are per 1 billing period (month). For monday.com's price for additional actions, the price of HubSpot's API Limit Increase add-on, the unit price of Asana's AI usage packs and the credits consumed by 1 run, and whether extra run quota can be bought at Shopify, we could not find any of these stated on the vendors' own pages. The 1.5 multiplier in step 6 and the 70% in step 7 are not vendor recommendations but the rule of thumb this article applies. Terms change, so please check each vendor's own pages before you sign.
More in Operations and security
All of operations and security →What do you hand over when a client asks how you manage information
SOC 3, the URL of the DPA and the storage-location display are the first 3 items of a client security questionnaire, and all 3 are free; the other 4 are listed in the piece.
Read → Operations and security 05What does SSO actually cost?
The cheapest published route is $90 per seat per month, but a mandatory $1,500 onboarding fee brings the first year to $2,580 for a single seat.
Read → Operations and security 06What happens to your data when you cancel
Only Shopify and HubSpot state how long data survives cancellation, which makes the export a job for while the contract is still live.
Read →