I’m trying to create a flow that starts with a webhook node.
I put this webhook in an automation inside activecampaing, so when the contact goes through it, it comes to the N8N and from the N8N I take it to the airtable.
However, on the N8N side, everything is configured correctly, post method, saved and active flow, production url.
But in active when the contact goes through the webhook node it jumps and reports failure.
But I can’t identify what this failure is, because using a webhook tester, everything works.
I’m using n8n as a self host, on a Digital Ocean machine and the installation was done using Docker. The latest version of N8N that is installed.
Sadly no idea what system you are using and why it would “skip” the n8n Webhook. Did you try to call the Webhook manually with curl, Postman or similar?
If you do it, is it reachable? Does it return a response code 200 and says that it started the workflow?
Is there any way of seeing in the tool you are using what is happening in that step (maybe you can see the response there).
Sorry, if the n8n webhook works via curl/Postman I sadly have no idea why it would not work with Active Campaign. In this case, you probably really have to wait for a response from their support to give you additional information on what exactly is going on.
Neither I or anybody else I am aware of added any configuration which should do that. So doubt that. Anyway some services out there sometimes make some questionable design decisions which are not conform with the standards and then something like that could theoretically happen. Anyway do not think that is the case here.
Same with Digital Ocean, could theoretically be possible but also honestly unlikely.
Generally sounds very strange and can currently not explain what is going on there. Very sad that Active Campaign does by default not offer any more information what is going on except that it failed.
I got the following feedback from ActiveCampaign support, something related to the size of the request.
I even saw about the N8N_PAYLOAD_SIZE_MAX function, but it doesn’t solve the problem.
And the error occurs also in the desktop version of n8n, which I don’t know how to increase the limit.
