Hey Oskar. Thanks for video. I have a question. Before start to fully work in n8n i would like to know about backups, do you find solution for yourself how automaticaly do backups of all your workflows? i'm using command docker exec -u node -it root-n8n-1 n8n export:workflow --all --output=backups/latest/ But each time i have error message that it si impossible to create execute mkdir and create folder for export Folder must be created inside container or in my VPS machine
Hello, I think the easiest way would be to make a simple API call to your n8n instance to retrieve all workflows. You can do it by selecting „n8n” from nodes library, choosing resource „Workflow” and operation „Get many” (or „Get” if you want to retrieve the specific workflow). As an output you should get your workflows in JSON format, so you can further process them (for example export to GitHub). Link to the endpoint in n8n docs in case you need it: docs.n8n.io/api/api-reference/#tag/Workflow/paths/~1workflows/get I personally haven’t made my auto-backup workflow yet, since all important ones I always export manually. But this method should work to automate the process. Let me know whether it is something that you were looking for. Cheers!
Hi Oskar, What should I do if I have a workflow that takes around 8 minutes to complete? When I initiate the API GET request in a new browser tab, it times out after about 2 minutes. However, the workflow continues to run and eventually completes in n8n, as I can see in the execution list. I'm expecting to receive a JSON response from the final "Respond to Webhook" node, but the request in the browser times out after 2 minutes, which prevents this from happening. How do you handle situations like this?
Hello, thank you for your comment. I suspect it’s the matter of default timeout value for your browser (as the workflow executes correctly, the only reason for this could be ~2 min timeout in browser). You can try to make request form other browser or even from terminal to verify this issue. I’m not sure what is the goal of your automation, but you can also consider rebuilding it to make it asynchronous (instead of standard synchronous request-response). For long-execution workflows it’s usually more convenient way to run communication.
Hello, thank you for your comment. In "Respond to Webhook" node switch value of "Respond With" field to "Text", and in field below ("Response Body") paste your HTML code. It should return HTML page after triggering the webhook.
Appreciate the short to the point video covering most common use cases!
Nice tips... Now I'm search for a way to access data from previous workflow. Do you have any example ?
Hey Oskar. Thanks for video. I have a question. Before start to fully work in n8n i would like to know about backups, do you find solution for yourself how automaticaly do backups of all your workflows? i'm using command
docker exec -u node -it root-n8n-1 n8n export:workflow --all --output=backups/latest/
But each time i have error message that it si impossible to create execute mkdir and create folder for export
Folder must be created inside container or in my VPS machine
Hello, I think the easiest way would be to make a simple API call to your n8n instance to retrieve all workflows. You can do it by selecting „n8n” from nodes library, choosing resource „Workflow” and operation „Get many” (or „Get” if you want to retrieve the specific workflow). As an output you should get your workflows in JSON format, so you can further process them (for example export to GitHub).
Link to the endpoint in n8n docs in case you need it: docs.n8n.io/api/api-reference/#tag/Workflow/paths/~1workflows/get
I personally haven’t made my auto-backup workflow yet, since all important ones I always export manually. But this method should work to automate the process. Let me know whether it is something that you were looking for. Cheers!
Hi Oskar,
What should I do if I have a workflow that takes around 8 minutes to complete? When I initiate the API GET request in a new browser tab, it times out after about 2 minutes. However, the workflow continues to run and eventually completes in n8n, as I can see in the execution list. I'm expecting to receive a JSON response from the final "Respond to Webhook" node, but the request in the browser times out after 2 minutes, which prevents this from happening. How do you handle situations like this?
Hello, thank you for your comment.
I suspect it’s the matter of default timeout value for your browser (as the workflow executes correctly, the only reason for this could be ~2 min timeout in browser). You can try to make request form other browser or even from terminal to verify this issue.
I’m not sure what is the goal of your automation, but you can also consider rebuilding it to make it asynchronous (instead of standard synchronous request-response). For long-execution workflows it’s usually more convenient way to run communication.
hello, how you configure you webhook response to send back html and not json ?
Hello, thank you for your comment. In "Respond to Webhook" node switch value of "Respond With" field to "Text", and in field below ("Response Body") paste your HTML code. It should return HTML page after triggering the webhook.
Thanks it works ! @@workfloows
Fucking legend, loved the beginning. Hit me up, we could perhaps do some work together 😄
Thanks a lot! Sure, if you have some cool ideas, feel free to drop me an email (workfloows@gmail.com) and I’ll do my best to respond asap 😃 Cheers!
@@workfloows you bet I do! I’ll mail you rn
Братан, спасибо тебе, очень помог