Self-Host n8n in 20 Minutes - Easiest & Cheapest Setup

Key Concepts

Self-hosting NADN, Cloud vs. Computer Hosting, Hostinger, Alast, Railway, Upgrading NADN, Google Cloud Credentials Integration, Community Nodes, HTTP Request, Automation, AI Automation Agency.

Self-Hosting NADN: The Ultimate Guide

Introduction

The video provides a comprehensive guide to self-hosting NADN (n8n), covering implementation, upgrades, community nodes, and Google Cloud credential integration. The primary motivation for self-hosting is to overcome the limitations of the cloud-hosted version, which restricts workflow executions and active workflows.

Cloud vs. Computer Hosting

Two primary methods for self-hosting NADN are discussed:

• Cloud Hosting: Recommended for non-technical users due to its reliability and uptime (99.99%). Cloud hosting ensures continuous operation regardless of internet connectivity or local server issues. Costs range from $0.05 to $20 per month.
• Computer Hosting: Suitable for technical users and is technically "free," but unreliable due to potential downtime caused by internet outages or computer failures. This method is not recommended for mission-critical applications.

Setting Up NADN with Hostinger

Hostinger is the preferred platform for self-hosting NADN due to its cost-effectiveness and ease of use.

Steps:

1. Search "Hostinger NADN" on Google and click the first link.
2. Choose the lowest-tier plan initially, with the option to upgrade later.
3. Select the server location closest to your physical location to minimize latency.
4. Choose NADN as the operating system and the basic version (not Q mode).
5. Set a root password.
6. Complete the payment process.
7. Access the NADN instance through the Hostinger control panel and log in.

Setting Up NADN with Alast

Alast is another option for self-hosting NADN.

Steps:

1. Sign up for a free Alast account.
2. Create a new service and select NADN from the dropdown menu.
3. Choose a server location closest to your physical location.
4. Select the smallest plan initially.
5. Enter your email and choose level one support.
6. Create the service.
7. Access the NADN instance through the Alast control panel using the provided username and password.

Setting Up NADN with Railway

Railway is presented as a less preferred option due to its instability.

Steps:

1. Deploy a new project and search for NADN.
2. Choose the "with workers" option.
3. Follow the prompts to deploy NADN.

Upgrading Self-Hosted NADN

• Alast: Automatic updates are enabled by default.
• Hostinger: Requires manual updates using a command-line interface.

Steps for Hostinger:

1. Search "Hostinger update NADN" on Google and click the first link.
2. Copy the provided code for updating NADN.
3. Access the browser terminal in Hostinger.
4. Paste the code and execute it to update the NADN instance.

Integrating Google Cloud Credentials

Integrating Google Cloud credentials involves a multi-step process within the Google Cloud Console.

Steps:

1. Visit Google Cloud Console: Sign up if necessary (may require credit card verification).
2. Create a New Project: Name the project (e.g., "test demo video").
3. Enable APIs: Enable the Google Drive API, Gmail API, Google Sheets API, Google Docs API, and Google Calendar API.
4. Configure OAuth Consent Screen:
   • Choose "External" as the user type.
   • Add an app name (e.g., "test integrations").
   • Add your email as a test user.
   • Publish the app.
5. Configure Audience: Add your Google email as a test user.
6. Create OAuth Client:
   • Select "Web application" as the application type.
   • Leave the "Authorized JavaScript origins" field blank.
   • Add the "Authorized redirect URI" from your NADN account.
   • Copy the Client ID and Client Secret.
7. Add Credentials to NADN:
   • Paste the Client ID and Client Secret into the corresponding fields in NADN.
   • Add the authorization URL (https://accounts.google.com/o/oauth2/auth) and access token URL (https://oauth2.googleapis.com/token).
   • Sign in with your Google account and grant the necessary permissions.

Community Nodes

Community nodes expand NADN's functionality by allowing users to install third-party integrations.

Steps:

1. Browse available nodes on n8n.io/integrations.
2. Copy the npm package name of the desired node.
3. In NADN settings, paste the package name (without "npm i") and install the node.
4. The new node will be available in the workflow canvas.

HTTP Request

For nodes not available in the community, users can integrate them using HTTP requests, which requires technical expertise.

Conclusion

Self-hosting NADN provides greater control, cost-effectiveness, and access to unlimited operations and workflows compared to the cloud-hosted version. The video provides a detailed guide to setting up and managing a self-hosted NADN instance, including integrating Google Cloud credentials and utilizing community nodes. The main limitation of the self-hosted version is the lack of team collaboration features.