Hello n8n Support Team,
I’m reaching out to request an urgent response from your team.
We’ve already made a payment that exceeds the agreed amount and have sent multiple emails, but unfortunately, we haven’t received any reply so far.
We need your support to resolve this issue as soon as possible.
Thank you in advance for your attention, and I look forward to hearing from you soon.
Best regards,
I am personally not officially apart of the n8n team. But could provide some clarity.
n8n is currently exploding in popularity, and they are trying their best to keep up. They just got a large amount of funding and are looking for more people to join to assist in their growth.
May I ask, is this enterprise level payments or just basic cloud? What issue are you encountering exactly? I may be able to assist.
Hey, just stepping in to help while you wait for an official response from the n8n team.
I’m not part of their support staff, but I’ve been around in the tech space for a while — contributed to early open-source automation tools, helped shape integrations that later inspired how tools like Zapier and n8n handle webhook workflows today, and worked on early concepts of distributed queues before they became mainstream in platforms like Temporal and Prefect.
So yeah, I understand how frustrating it is to be on the paying side and not get timely support, especially when there’s money and commitments involved.
I’d recommend:
Tagging @moderators or the n8n support team here on the forum directly (sometimes posts slip through the cracks).
Also dropping a message via n8n.io/contact if you haven’t already — it routes straight to their billing/support queue.
If the issue is related to subscription management, account locking, or limits affecting workflows, and you can share what’s happening technically, I might be able to suggest a temporary workaround until support picks it up.
Hope it gets resolved soon — and shout if you need a hand with anything on the workflow side.
Dandy
PLEASE don’t do either of these things. They won’t help you ‘jump the queue’ and will only give us more work, making it harder to keep up with support.
Hey @Dandy — thank you so much for your message. It was the first constructive and empathetic response I’ve seen so far, and I truly appreciate it. Your willingness to help and the technical background you shared really mean a lot.
Just to give some context: we first reached out to n8n support on March 26th, and we’ve been waiting since then. Meanwhile, we’re facing an issue that has completely stopped our operations — and from our side, it seems like something simple and quick to fix.
@Bartv, the only thing your message brought was: “stop trying.”
That’s what you call support?
No attempt to understand what the issue is, no empathy for the fact that a business is down, no alternative path, no timeline, no prioritization suggestion — nothing.
If anything, this kind of answer only adds to the frustration.
I understand there’s a queue. But when a problem is critical and blocks operations entirely, I believe any support system should have either a maximum response time or a way to handle urgent cases differently. This is not about skipping ahead — it’s about avoiding damage that could be resolved in minutes with the right attention.
We’re still here, waiting, hoping to get some real help soon.
If you believe there is a simple fix, could you describe the issue in greater detail so others on the forums can help in the meantime? What issue is occurring? And what have you done to try solve?
Simply saying you reached out once and processes are down, is not helpful in guiding you to a solution. More description is needed.
The 26th was only a few days ago, less counting out the weekend… You made it seem like it was weeks ago.
Thanks for your reply, ThinkBot.
Let me provide more context so it’s clear why we’re pressing for a solution.
Our operations have been completely down for 4 business days, and we also tried to keep things running over the weekend, so it’s been 6 days in total. This isn’t just inconvenient — it’s highly damaging to our clients and our business.
Saying “it was only a few days ago” downplays the seriousness of the situation. For companies that rely on n8n to deliver services and keep automations running, even a few hours of downtime can mean missed opportunities, lost clients, and real financial impact.
The solution is simple, but only the n8n team has the access and ability to apply it. We’ve already sent all the necessary information via email.
If there’s anything else we need to provide or clarify to get this escalated and treated as a priority, please let us know. We’re fully available to collaborate — we just need someone from the team to actually act on this.
It’s professional to send follow up emails, but it may already be visible in their queue. It is still early Monday (at least in US).
I would ensure that you sent a request to the right emails as well.
I am currently not tied to the n8n team, so I cannot give an actionable answer about their internal systems. Nor have I been able to see your email with explanations.
If you could provide some of those details here, that could assist greatly, to help confirm or deny if this is even something that is needed for an internal team to handle.
Often times, a basic restart or updates of the instance can fix some odd issues. This can be done in your admin panel if you are on n8n cloud, but it is still quite unclear if you are on cloud, self hosted, or enterprise / white label additions of n8n.
Other times, the issue is a basic development misunderstanding of a node, the platform, or of core logic of a workflow.
Either of the above issues I am (and other forum volunteers are) happy to assist on, but if it truly is an internal matter, and you reached out to the correct email + sent follow ups, I would say you may just have to wait in queue.
They are very overwhelmed right now, and I believe don’t intend to make you feel unseen/ignored. They just got 55m euro funding, which I would guess, will help greatly in many areas including support tickets.
Thank you so much for your message and your willingness to help — I really appreciate it.
That said, I’d like to clarify once again that this is not an issue with a workflow or a node misunderstanding, but rather a problem with my n8n Cloud account itself. It’s something that only the official n8n team can solve, and that has already been clearly stated in the support request.
I also want to be very clear — in your last message, you minimized the impact this issue is having. Our operations have been completely down for several days, and this has caused serious harm to both our clients and our business. This is not a minor inconvenience — it’s a critical situation that requires immediate attention.
We’ve already sent all the necessary details by email, and while I understand the team may be overwhelmed, we are still waiting for a resolution.
Thanks again for your support — I just wanted to make sure this distinction was absolutely clear.
What is the Cloud account issue tho? I still am not clear. If you paid but the instance went down, you should be able to restart/start it within your admin panel.
If you missed a payment for long enough, the instance will be destroyed, and I don’t believe workflows are recoverable, if that’s also potentially what happened?
Really unclear tho.
I am also unsure what your business is and where your workflows fit in. If it is as critical as you say, even tho support won’t be able to help the same (nor is it as easy as Cloud), you could just self-host from now on (depending on your business use case). You will then have 100% full control of the instance and need no n8n involvement, if it goes down, you can easily restart it, and there will be no charges (unless you are reselling automations), only the charge of the server cost to host, and perhaps the charge of a dev to deploy/fix/maintain it.
ThinkBot,
We are currently in the process of migrating to a self-hosted solution, but in the meantime, we still need to rely on n8n Cloud.
I understand that the situation may not have been clear to you — and that’s on me, I didn’t explain all the details. However, this is an issue that only the official n8n team can solve, and unfortunately, there’s nothing we can do on our side.
Thanks again for trying to help.
So you have workflows that are down for clients as well?
This means you are on enterprise? This would mean you had the option for an SLA with priority support I think. Of course you would have had to pay for that then.
Thanks for your input, Bram.
Just to clarify — we’re using n8n Cloud, not the Enterprise plan.
The issue is with our Cloud account itself, which is currently preventing all workflows from running. Several clients are being directly affected because they rely on automations inside our n8n Cloud environment.
We’re in the process of migrating to a self-hosted solution to avoid this kind of situation in the future, but for now, we still depend on the Cloud infrastructure and support.
Appreciate you taking the time to comment.
To my understanding, self-hosted or cloud, if you are selling automations/access on your own account to clients, that is against the TOS and requires a Whitelabel or Enterprise plan. Unless you meant something else.
You’re right, but just to clarify: I don’t sell automations to my clients.
However, a big part of my work happens inside n8n, and it directly impacts my clients’ operations. That’s why I want to make sure everything is aligned with the TOS.
Will you help me get in touch with the n8n team to solve this issue?
Is there anyone from the n8n team who could actually help me?
Please?
I really appreciate the constructive response from @Dandy_Dow — thank you for that.
I received a reply via email from n8n support.
Still, I’m honestly tired of having to explain everything over and over again to people who haven’t offered any real assistance and only made the problem seem less important than it actually is.
It is difficult for those to help on the forums without many details.
I am glad someone got back, were they able to fix the issue?
Hey Gabriela — I’m really sorry you had to go through all of this while also handling client expectations and operations on your end.
I’m glad the support team finally got back to you, but I completely get your frustration. When everything stops and people around act like it’s “just a few days,” it really feels like no one is actually listening.
If at some point you feel like sharing what the issue ended up being (even without sensitive details), it could help others in the community be more prepared or avoid similar situations. But of course, only if that makes sense for you.
And honestly — I hope your self-hosted migration goes as smoothly as possible. If you run into any issues with setup, architecture, or anything technical, I’m around. You shouldn’t have to deal with this kind of mess alone.
We got this.
Just popping in here to note that this user has received a response from n8n Support.
We do appreciate that there are definitely time-sensitive issues that we would like to prioritize, and we are working to better address our users’ needs as n8n experiences this latest round of explosive growth.
Please bear with us, we understand your frustration and ask for your patience while we work to improve our Support offerings as n8n and its users needs continue to evolve and grow.