NodeMation By Nskha
🔥 LIMITED TIME ONLY! 🔥 🏆 Claim Your FREE Lifetime n8n LICENSE! 🏆 🔧 Don't forget to UPDATE TO THE LATEST VERSION. ➡️ Follow these steps: - Go to Billing & Plans - CLICK ON THE NEW POPUP - ENTER YOUR EMAIL TO GET YOUR LICENSE KEY RIGHT AWAY! 🎉 Congratulations!…
If you haven't received them yet, here are the 3 paid features now available for free when you active your key:
1️⃣ . Restore your old version of workflows (24h auto delete).
2️⃣ . Debug the current executed workflows from history (🔥 this is the most useful feature!).
3️⃣ . Add tags and rates to the executed workflow data.
To be honest, these features should always be free since they are core functionalities. It's great to see the n8n team finally offering them at no cost! I had previously requested this for verified creators, and now they're making it available to everyone. Don't miss out on this opportunity!🚀
To be honest, these features should always be free since they are core functionalities. It's great to see the n8n team finally offering them at no cost! I had previously requested this for verified creators, and now they're making it available to everyone. Don't miss out on this opportunity!
Please open Telegram to view this post
VIEW IN TELEGRAM
Important Notice Regarding Coolify and n8n Integration
When using Coolify with n8n, always ensure you're using HTTPS links. This is crucial because the FQDN (Fully Qualified Domain Name) will be shared with n8n. If it's not HTTPS, your app will run on HTTP even if you have SSL enabled. This can lead to several issues:
- 🚫 Webhooks may experience excessive redirects, causing them not to work or be slow.
- 🚫 Node triggers like Telegram might stop working without any apparent reason.
- 🚫 Your n8n instance may become inaccessible.
All these problems stem from not using an HTTPS domain on Coolify's FQDN and not enabling Cloudflare's SSL mode to "Full/Strict". Do not turn off the Cloudflare proxy (this is strongly not recommended).
To resolve these issues:
1. Use an HTTPS domain on Coolify's FQDN.
2. Enable Cloudflare SSL mode to "Full/Strict".
A client shared that they used their domain with WordPress hosting, which strictly requires the SSL mode to be set to "Flexible". To handle this with Cloudflare, navigate to the Page Rules in your account settings. Then, enable the SSL mode only for the subdomain running your n8n instance (e.g.,
When using Coolify with n8n, always ensure you're using HTTPS links. This is crucial because the FQDN (Fully Qualified Domain Name) will be shared with n8n. If it's not HTTPS, your app will run on HTTP even if you have SSL enabled. This can lead to several issues:
- 🚫 Webhooks may experience excessive redirects, causing them not to work or be slow.
- 🚫 Node triggers like Telegram might stop working without any apparent reason.
- 🚫 Your n8n instance may become inaccessible.
All these problems stem from not using an HTTPS domain on Coolify's FQDN and not enabling Cloudflare's SSL mode to "Full/Strict". Do not turn off the Cloudflare proxy (this is strongly not recommended).
To resolve these issues:
1. Use an HTTPS domain on Coolify's FQDN.
2. Enable Cloudflare SSL mode to "Full/Strict".
A client shared that they used their domain with WordPress hosting, which strictly requires the SSL mode to be set to "Flexible". To handle this with Cloudflare, navigate to the Page Rules in your account settings. Then, enable the SSL mode only for the subdomain running your n8n instance (e.g.,
n8n.domain.tld) and set it to force SSL mode to "Full/Strict". That's all, and it should work without any problems.👍1🔥1
🌟 Vote for This Feature!
Hey everyone! Please take a moment to vote for this feature: Socks5 Support in HTTP Request Node.
Socks5 proxies help you bypass website security by using DNS + Proxy, unlike standard HTTP proxies that rely on static DNS. This makes them more versatile!
💡 If you're looking for affordable Socks5 proxies, I recommend Webshare as a great option: Webshare Proxies. They offer ISP Residential proxies for just $8/year! Personally, I buy one per client and share it with them for browser use. This way, it appears to services that they are real users! ✅
Hey everyone! Please take a moment to vote for this feature: Socks5 Support in HTTP Request Node.
Socks5 proxies help you bypass website security by using DNS + Proxy, unlike standard HTTP proxies that rely on static DNS. This makes them more versatile!
💡 If you're looking for affordable Socks5 proxies, I recommend Webshare as a great option: Webshare Proxies. They offer ISP Residential proxies for just $8/year! Personally, I buy one per client and share it with them for browser use. This way, it appears to services that they are real users! ✅
n8n Community
Socks5 support in http request node
One year ago this was discussed: Socks5 support in http request node? I am using the desktop version nowadays. How can I make the HTTP request go via a socks5 proxy in the desktop setup? When doing things in bash is as easy as this: I first just get…
🫡2
To convert any internal website API into a long-lasting API, I follow this process:
1. Automate the user login 🔐
2. Establish a KV (Key-Value) database to securely store tokens 🗄
3. Implement n8n's internal API, converting it similarly, to manage service API keys using the credentials same as official way 🔄
By doing this, any website can function on n8n as an official API. These workflows run in the background, frequently updating tokens according to their expiration times. ⚙️
1. Automate the user login 🔐
2. Establish a KV (Key-Value) database to securely store tokens 🗄
3. Implement n8n's internal API, converting it similarly, to manage service API keys using the credentials same as official way 🔄
By doing this, any website can function on n8n as an official API. These workflows run in the background, frequently updating tokens according to their expiration times. ⚙️
Hey everyone! 👋
I've got a preference for Mega.io over other cloud services, but recently I needed to automate some personal tasks using cloud storage. For business purposes, I always go with S3. However, I found that Dropbox might be a cost-effective solution for small business use.
The challenge with Dropbox and n8n is that it doesn't support the refresh token method needed for accessing specific internal features like file or folder sharing. To tackle this, I created an internal workflow that converts Dropbox's internal API to the official API using n8n micro-services method.
Since implementing this, the workflow has been running smoothly with just a ~5-second delay.🚀
I've got a preference for Mega.io over other cloud services, but recently I needed to automate some personal tasks using cloud storage. For business purposes, I always go with S3. However, I found that Dropbox might be a cost-effective solution for small business use.
The challenge with Dropbox and n8n is that it doesn't support the refresh token method needed for accessing specific internal features like file or folder sharing. To tackle this, I created an internal workflow that converts Dropbox's internal API to the official API using n8n micro-services method.
Since implementing this, the workflow has been running smoothly with just a ~5-second delay.
Please open Telegram to view this post
VIEW IN TELEGRAM
I wanted to share some progress with you. Today, I started using Puppeteer, which involves automation through headless browsers.
After some research, I discovered the easiest way to set it up is by using Coolify with a project called "Browserless." This setup allows me to connect it with n8n and restrict API calls to the n8n server exclusively using Cloudflare.
The main reason for this is to bypass the Cloudflare challenge page. I was having difficulty with n8n while trying to inject JavaScript code required by a service like 2Captcha to overcome Cloudflare's bot protection. To tackle this, I opted for an RPA method, and using a headless browser proved to be the best solution.🚀
i just want to let you know if you used it with coolify then do not use the internal debugger use the cloud one faster: https://chrome.browserless.io/debugger/💊
Thanks for your attention!😊
After some research, I discovered the easiest way to set it up is by using Coolify with a project called "Browserless." This setup allows me to connect it with n8n and restrict API calls to the n8n server exclusively using Cloudflare.
The main reason for this is to bypass the Cloudflare challenge page. I was having difficulty with n8n while trying to inject JavaScript code required by a service like 2Captcha to overcome Cloudflare's bot protection. To tackle this, I opted for an RPA method, and using a headless browser proved to be the best solution.
i just want to let you know if you used it with coolify then do not use the internal debugger use the cloud one faster: https://chrome.browserless.io/debugger/
Thanks for your attention!
Please open Telegram to view this post
VIEW IN TELEGRAM
NodeMation By Nskha
Channel photo updated
Please open Telegram to view this post
VIEW IN TELEGRAM
👍1
YouTube
Automate Your Designs: Robolly + n8n Tutorial
🎨 Master Design Automation: Robolly + n8n Complete Tutorial Guide!
Get instant image & video automation with Robolly inside n8n—no coding required!
Learn to install, configure, and generate visuals using custom templates.
Expand your workflow and skyrocket…
Get instant image & video automation with Robolly inside n8n—no coding required!
Learn to install, configure, and generate visuals using custom templates.
Expand your workflow and skyrocket…
Get instant image & video automation with Robolly inside n8n—no coding required!
Learn to install, configure, and generate visuals using custom templates.
Expand your workflow and skyrocket productivity—timestamps below! 🚀
🕐 TIMESTAMPS:
00:00 - Intro & Overview: Quick Setup Guide
00:50 - Step-by-Step Installation Process
02:00 - Automating Image Generation
05:00 - Creating Dynamic Videos
08:00 - Managing Historical Renders
10:00 - Pro Design Tips & Freepik Integration
14:00 - Community Resources & FAQ
#robolly #n8n #automation #nocode #designautomation #workflow #tutorial #productivityhacks #automation2024 #workflowautomation
Please open Telegram to view this post
VIEW IN TELEGRAM
❤1
It's been a long time since I abandoned this project, which was designed to generate fully functional n8n installation files. The goal was to provide no-code users with the best possible experience through a GUI configuration for setting up their own n8n instance.
I identified this as a serious problem after spending around two days in meetings with my client, configuring and setting up his instance step by step. The issue was that I had to teach him every single step along the way.
I thought to myself, "Why not create an entire project that automates each step for the client?" I started by writing a basic script for him, explaining every single line I added to his Docker file. He really appreciated it, and that encouraged me to take the idea further by converting it into a full-fledged website.
However, the challenge was figuring out how to ensure his credentials wouldn't be shared with my servers. This led me to realize that everything had to run locally on the client side. Every AI request, search, or any operation would need to occur locally. Although this is a significant challenge for someone new like me, it's an excellent way to build trust with users by ensuring their credentials remain secure.
Until now, it supports 86 credential values with n8n. Every single step suggested is based on my own tests, so I believe it is going to be the ultimate tool that truly cares about n8n installation—not just default values and a quick setup!
I identified this as a serious problem after spending around two days in meetings with my client, configuring and setting up his instance step by step. The issue was that I had to teach him every single step along the way.
I thought to myself, "Why not create an entire project that automates each step for the client?" I started by writing a basic script for him, explaining every single line I added to his Docker file. He really appreciated it, and that encouraged me to take the idea further by converting it into a full-fledged website.
However, the challenge was figuring out how to ensure his credentials wouldn't be shared with my servers. This led me to realize that everything had to run locally on the client side. Every AI request, search, or any operation would need to occur locally. Although this is a significant challenge for someone new like me, it's an excellent way to build trust with users by ensuring their credentials remain secure.
Until now, it supports 86 credential values with n8n. Every single step suggested is based on my own tests, so I believe it is going to be the ultimate tool that truly cares about n8n installation—not just default values and a quick setup!
🔥4💯2👍1
NodeMation By Nskha
It's been a long time since I abandoned this project, which was designed to generate fully functional n8n installation files. The goal was to provide no-code users with the best possible experience through a GUI configuration for setting up their own n8n instance.…
Vote here if you'd like to see this project go live this week or prefer any of the other ones we've already worked on:
https://www.facebook.com/groups/n8nuser/posts/1845502812877094/
https://www.facebook.com/groups/n8nuser/posts/1845502812877094/
Paid HTTP node alternative that can bypass almost all internet bot blocks at the lowest price on the market (Lowest price i mean LOWEST not fake at all it's cheap like free)... Would you use it?
We're currently developing this node. first, we thought clone the http node itself and improve it, but our partner decided to keep it simple, but it will be linked to the http node using the (Error Path), it's not our SaaS, but we've invited them to join n8n and we take care of the development. Since they're the most affordable option on the market and stable for our clients, we haven't made them widely known yet. However, if this post shows interest in these kinds of solutions, we promise to release it publicly with our affiliate link.
Cons:1️⃣ Privacy concerns: Third-party services (such as Captcha, proxies, and browsers providers) may have access to your data.2️⃣ It's a paid service, not free.🙁
Pros:1️⃣ Unlock restricted access for automation and scraping without limits. No need to set up multiple services or pay multiple providers—just plug in your key and go with our node it will became the easiest way to do it!2️⃣ Save significant money on tools like Captcha, proxies (IPs), Docker setups (VPS), Playwright, or spending time reading articles on how to accomplish these tasks. you will get unlimited solutions of these (Including IPs) of all countries of the world at one cost with significant free plan.
We're currently developing this node. first, we thought clone the http node itself and improve it, but our partner decided to keep it simple, but it will be linked to the http node using the (Error Path), it's not our SaaS, but we've invited them to join n8n and we take care of the development. Since they're the most affordable option on the market and stable for our clients, we haven't made them widely known yet. However, if this post shows interest in these kinds of solutions, we promise to release it publicly with our affiliate link.
Please open Telegram to view this post
VIEW IN TELEGRAM
NodeMation By Nskha
Paid HTTP node alternative that can bypass almost all internet bot blocks at the lowest price on the market (Lowest price i mean LOWEST not fake at all it's cheap like free)... Would you use it? Cons: 1️⃣ Privacy concerns: Third-party services (such as Captcha…
Like one GPT for setups, one for expressions, one for logs and error debugging and so on...
Please open Telegram to view this post
VIEW IN TELEGRAM
😁2
Please open Telegram to view this post
VIEW IN TELEGRAM
n8n Community
Update n8n CLI workflows command (import/export) to support folders
I tried to export organized workflows in folders using the official export method for workflows command n8n export:workflow --all --output=/tmp/workflows.json, but the folder settings did not appear on the second instance when import. Both instances have…
Yesterday i pushed small project, a tested vibe coded project... a shell to import and export your n8n data...
😁Hey rami, Why not use n8n workflows? I have dozens of workflows for backups... already shared some of them before. but the update and import within n8n instance cause errors sometimes and it made me look stupid on the client meeting day when the workflow didn't work on his instance... so we forced to do something outside the n8n... and this shell exactly requested by our partners some weeks ago so i decided to make it public with some fixes since it's requested by many people...
In near future when website ready you will have also a command builder to build your own command with one click.
Automations-Project/n8n-data-manager: https://github.com/Automations-Project/n8n-data-manager
Here's example command i use for quick export and tests
You can ask help of A.I to understand it better, and you can go to the repo and copy the shell content and paste to A.I to ask if it contain any danger code parts for your safety 😉 in future it will be shorter command.
- you can use it also inside n8n nodes
- you can make it auto backup/import which used to move from dev to prod
- you can import only workflows so you can get updates without affecting credentials
Read more: https://www.reddit.com/r/n8n/comments/1kcv2uj/from_oops_to_up_in_one_command_my_new_n8n/ & https://community.n8n.io/t/from-oops-to-up-in-one-command-my-new-n8n-backup-restore-shell/109695
😁Hey rami, Why not use n8n workflows? I have dozens of workflows for backups... already shared some of them before. but the update and import within n8n instance cause errors sometimes and it made me look stupid on the client meeting day when the workflow didn't work on his instance... so we forced to do something outside the n8n... and this shell exactly requested by our partners some weeks ago so i decided to make it public with some fixes since it's requested by many people...
In near future when website ready you will have also a command builder to build your own command with one click.
Automations-Project/n8n-data-manager: https://github.com/Automations-Project/n8n-data-manager
Here's example command i use for quick export and tests
clear && sudo rm -f /usr/local/bin/n8n-manager.sh && rm -rf ~/.config/n8n-manager && rm -rf /tmp/n8n-* && rm -rf n8n-shell-install.sh && curl -o n8n-shell-install.sh https://raw.githubusercontent.com/Automations-Project/n8n-data-manager/refs/heads/main/install.sh && chmod +x n8n-shell-install.sh && ./n8n-shell-install.sh && n8n-manager.sh --action 'backup' --container '$(docker ps --filter "name=n8n" --format "{{.Names}}" | head -n 1)' --token '<Replace Your Github Token Here>' --repo '<Replace Your Github username/repo here>' --branch 'main' --trace --verbose --dated
And same command can be used for import just replace the 'backup' with 'restore'
You can ask help of A.I to understand it better, and you can go to the repo and copy the shell content and paste to A.I to ask if it contain any danger code parts for your safety 😉 in future it will be shorter command.
- you can use it also inside n8n nodes
- you can make it auto backup/import which used to move from dev to prod
- you can import only workflows so you can get updates without affecting credentials
Read more: https://www.reddit.com/r/n8n/comments/1kcv2uj/from_oops_to_up_in_one_command_my_new_n8n/ & https://community.n8n.io/t/from-oops-to-up-in-one-command-my-new-n8n-backup-restore-shell/109695