I have one workflow, only one. I cannot publish my workflow to test because it says I have reached the Max of 16 Test Webhooks. I have no clue how to resolve this and publish so that I can test.
My automation is simple, when a Stripe payment comes in, it triggers the duplication of 3 wordpress pages and then triggers an email to the subscriber and to myself. Not complicated. But I need to run a test purchase in Stripe to make sure it is working. But I can’t publish to run the test. Please help.
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
this usually happens because old test webhooks are still registered.Even if you only have one workflow now, n8n keeps test webhooks from previous tests. try disabling the workflow, refresh the editor and remove any unused test webhooks, then enable it again. If that doesnt help,restarting n8n usually clears the leftover test webhooks
@Seth_Freeman It sounds like the issue is due to Stripe’s 16 live webhook endpoint limit .You should go to your stripe dashboard under Developers → Webhooks and remove any old or unused endpoints, even the disabled ones to free up slots for your test.
Building on what robbie mentioned about leftover test webhooks and what Anshul pointed out about cleaning unused Stripe endpoints, the immediate blocker here is on the n8n side.
If the error appears when you try to start the test in n8n, it means the internal pool of temporary test webhooks is full. The most practical way to clear those stale registrations is to deactivate the workflow and fully restart the n8n instance, then open the editor and start the test again so a fresh single test webhook is registered.
Cleaning old webhook endpoints in Stripe is still good practice and can prevent other limits later, but the action that actually unblocks testing right now is restarting n8n to reset its internal test webhook counter.
I looked into this and found the root cause. The error isn’t coming from n8n itself, it’s coming from your Stripe account.
When you publish or test a Stripe Trigger in n8n, it automatically tries to create a new webhook endpoint in Stripe. Stripe has a hard limit of 16 webhook endpoints per account, and even disabled endpoints count toward that limit. If you already have 16 registered, Stripe rejects any new one and n8n shows the “Reached max of 16 webhooks” message.
Because of that, restarting n8n or deactivating workflows won’t help, since the limit is enforced on the Stripe side. To fix it, open your Stripe Dashboard, go to Developers → Webhooks, and delete old or unused endpoints (including disabled ones) until you have fewer than 16. After that, go back to n8n and publish/test again, and the Stripe Trigger should register successfully.