Just to be clear, in my message above I’m not complaining. I’m genuinely trying to understand what is the right way to make my projects because I don’t think the wording around executions is clear.
Is each sub-workflow within a workflow an individual execution? if one workflow is chaining other sub-workflows synchronously do they all count as individual executions or 1? I basically just want to know if we should structure our projects in a way where we don’t call other workflows from within a workflow (like small modules), unless we really need it, or if we should not worry about it because, “that’s all just 1 execution regardless”.
Sorry if this is clear to everybody else It’s not clear to me.
What you’ve done for the world has been life changing for businesses and many many people who don’t even realize the impact you’ve made. To simply take this feedback as some will like pricing changes and others won’t like it’s a binary issue of “pay per workflow” or “pay per use” is a huge error in judgement. You’ve created a false dichotomy. You don’t have a single type of user. You have some that lean heavy on workflows, some heavy on runs but with less workflows, some that are teams, etc etc. By your thinking, you will force your company down to the one type of customer that fits the singular model you’ve chosen. Your invented choice between A or B will force your user base down to A or B. This is how you will hand the others right over to your competitors. This is the moment you opened the window for them to finally catch you. It’s not how enterprise SaaS crosses over the scale line you’ve approached. It’s going backwards. You’ve always just missed having the right license for enterprise. Now you’re messing up the plan for the next tier down. You’re forcing the entire customer base downstream to try and capture the entry level market instead of simply adjusting the lowest tier and simply adjusting the highest tier. Your primary avatar isn’t the entry level and you won’t capture that. The market is driven by the power user. Your base exploded because of influencers making videos. That’s who you just alienated. Who will they start making videos for next? Those are the companies you just propped up. Brother, hire a CEO and let this baby take over like it should. The window is closing fast. You deserve to win. It’s time.
@jan What happens if we don’t upgrade to 1.106? We’d like to stay on the active workflow plan until we finish phasing out from n8n. Right now, we’re on the Startup plan and run about 500,000 executions per week. Even though the execution count is high, we’re a very small startup that believed n8n was the right tool and built everything around it. We receive a large volume of messages from the WhatsApp Business API and process each one in n8n, and each message may trigger around 10 or more workflows (not subworkflows). We see no way to merge these workflows without compromises, since we also integrate with Airtable, and some other integrations. Leaving n8n will be costly for us — but still less than the cost of the new plan.
Thank you for the excellent product and the recent update. Regrettably, despite being on the Starter plan in the cloud, we are still experiencing the error below. Could you please advise on how we can resolve this issue?
Thank you! You’re very welcome!! I’m planning to build a part 2 for Queue mode which I’m hoping to go into more details on some other parts such as custom worker management and even customizing workers, etc. Still in the works, so stay tuned to that video!!
I think the new changes are great overall, unlimited workflows is a big win for a lot of us.
Just remember:
On paid plans (cloud or self-hosted Business/Enterprise), workflows are unlimited but executions are capped by your plan.
On Community Edition (self-hosted), workflows and executions are both unlimited, as long as you’re within the Sustainable Use License. (I didn’t see any changes here)
Quick license reminder: there’s no limit on company size for Community Edition use — even large organisations can use it internally. The key restriction is that you can’t offer n8n as a hosted service to external users without a commercial license.
If you’re just testing, developing, or running internal automations, you can usually stay on Community Edition without issue.
And if you’re a bigger company looking to go onboard, it’s always worth asking n8n directly — I’m sure they’d be open to a fair discount, especially if you’re not yet in production maybe?
Community Edition = uncapped executions + unlimited workflows, but know the license terms so you’re on the right side of things.
Personally I choose n8n over make and other automation due to the unrestriced executions (alot of testing was eating my allowance on make (how annoying)), hopefully doesn’t effect business to much might help stablise the demand, is that a good thing maybe.
I started using n8n just a couple of days ago and I’m currently on the trial period. I was amazed by the possibilities this service provides. I had big plans to grow my business with your help.
As a test, I created a simple Telegram bot that helps me view orders from my online store, but in just 2 days of testing I already used up 200+ workflow executions. Now I realize that any serious development with n8n is probably impossible for me, because these execution limits will be exceeded instantly with even the most basic real usage and the creation of new workflows.
It’s very unfortunate that I won’t be able to use your great service. I don’t know if these limits have always been in place, and I honestly don’t understand how people can work with them at all. I cannot afford the Business or Enterprise plan, but neither the Starter nor the Pro plan seem suitable even for the simplest automation tasks because of these restrictions.
Much to my regret, it’s clear that I won’t be upgrading after the trial period ends.
Hello!
We currently have an active “Your n8n Startup Plan”, License Key, and pay $400.00 per month.
We notice the new plans, but since we have ~5M executions per month, the pricing is prohibitive for us, therefore we haven’t upgraded the version since, we are using 1.100.1.
However, checking our license:info (bellow), we’ve noticed that our license cert is expiring on Oct 03 in our production instance, however in our stating instance is validTo: Fri Sep 21 2035.
What happens in Oct 03? We are going to be forced downgraded? Are this legacy plan going to expire?
I’ve sent a e-mail to sales@ 2 days ago and no reply.
Exactly the conundrum we’re facing with this pricing! Most of our workflows are low execution volume, but we have two that effectively combine log data from various sources as part of a custom SIEM tool solution, and execute 10s of thousands of times per day. Yes, we could cut n8n out of the loop for this, but combining the data prior to it entering the tool itself is making the whole system far more efficient. I really can’t understand this execution limit for self hosted setups!
Hi YurkaTim!
First of all congrats on the implementation, i’ve been doing it for a couple of months and still havent had any volume like that! I really encourage you to check out this video from Jan (n8n’s CEO), the most important part is from minute 12 onwards, but it is all pretty good stuff! https://www.youtube.com/live/b5BBwpuYXws?si=XfGkLlOzBikwtA6E
Jan clearly stated that the community edition is, and will still be, free. So, if you’re just automating internal stuff you’re well within the Fair Usage Licencing of the free self hosted version. You should consider updating if n8n becomes a core part of your value proposition.
It’s not clear to me.