Hello, it seems that, in order to trigger a workflow via webhooks, one should always:
trigger the test url
enable the workflow
trigger the production url
Is there some flag for n8n environment, that allows us to skip 1. and by enabling the workflow, we can immediately start using it in production?
Hi @Boris_Idesman, I am afraid auto-enabling workflows including a webhook trigger is not a setting n8n has right now. So I’ll convert your question into a feature request, allowing you and other users to vote for it.
Is there any other approach, that you can recommend? Unfortunately, if we change a n8n machine, the workflows have to be reenabled one by one, so that the prod webhooks work.
@MutedJam For some reason, I can’t call the n8n API - it asks me for authorisation, but I am using an API key: {“code”:401,“message”:“Authorization is required!”}
Do you know what might be the reason?