HumationHuman + Automation
Back to Catalog

INST - the n8n installer: deploy workflows with automatic credential mapping

WyethWyeth
108 views
2/3/2026
Text ProcessingRegular ExpressionsURL ExtractionData CleaningEmail Extraction
Official Page

INST: The n8n Workflow Installer

This workflow provides everything you need to package and deploy multiple workflows from a single workflow you distribute.

That's right, now you can package up dozens of workflows and send your client(s) a single workflow to run, that will create them all and auto-assign all the credentials.

This workflow installs 3 files when you run it, demonstrating the functionality. Just make your own mods to the system, repackage it, and you are ready to go!

Requirements

  • An n8n instance with API access enabled and an access key
  • Optional: GitHub and OpenAI access keys

What This Workflow Does

  • Installs 3 additional workflows, demonstrating the functionality
  • One of the workflows is a packager, that you configure for your own needs
  • Two example workflows demonstrate functionality, and can be deleted

Step-by-Step Setup

  1. Run the Workflow
    This will get the example and tool workflows on your instance.

  2. Package Your Content
    Configure the packager, then run it to produce a base64-compressed version of your files.

  3. Customize the Installer
    Make your own copy of the installer, and set the base64 payload.

  4. Deploy the Installer
    Export your installer script. Now, anyone you send it to will get all your packaged workflows when they execute it.

How to Use This Workflow

This workflow is meant to be reused and adapted. You can:

  • Integrate it into a deployment pipeline
  • Turn it into a subworkflow for dynamic installs
  • Extend it to include triggers, permission settings, or test runs

If you frequently deploy or share n8n assets, this installer gives you a repeatable way to do it with confidence.

n8n Installer: Deploy Workflows with Automatic Credential Mapping

This n8n workflow simplifies the process of deploying other n8n workflows by automatically fetching workflow definitions from a GitHub repository, extracting credentials, and then deploying them to your n8n instance. It's designed to streamline the management and distribution of n8n workflows, especially for those who maintain a collection of workflows in a version control system.

What it does

  1. Triggers Manually: The workflow is initiated by a manual trigger, allowing you to control when deployments occur.
  2. Fetches Workflow Definitions from GitHub: It connects to a specified GitHub repository to retrieve a list of workflow JSON files.
  3. Iterates Through Workflows: For each workflow JSON found, it processes the file.
  4. Extracts Credentials: It identifies and extracts credential information from each workflow definition.
  5. Checks for Existing Credentials: It queries your n8n instance to see if the required credentials already exist.
  6. Conditionally Creates or Updates Credentials:
    • If a credential does not exist, it creates it using placeholder values.
    • If a credential already exists, it skips creation.
  7. Deploys Workflows: It then deploys the workflow to your n8n instance.
  8. Handles Errors: If any step encounters an issue (e.g., a workflow cannot be deployed), it stops the process and reports an error.

Prerequisites/Requirements

  • n8n Instance: An active n8n instance where you intend to deploy workflows.
  • GitHub Account: A GitHub account with access to the repository containing your n8n workflow JSON files.
    • GitHub Credential: An n8n credential configured for GitHub (e.g., Personal Access Token) with read access to your repositories.
  • n8n API Key: An n8n API key credential configured in your n8n instance, with permissions to create/update credentials and workflows.
  • Workflow JSON Files: Your n8n workflow definitions saved as .json files in a GitHub repository.

Setup/Usage

  1. Import the Workflow: Import this workflow JSON into your n8n instance.
  2. Configure Credentials:
    • GitHub Credential: Ensure your GitHub credential is set up in n8n.
    • n8n API Key Credential: Configure an n8n API Key credential. You will need to provide your n8n instance URL and the API key. This credential will be used by the "n8n" nodes to interact with your instance's API.
  3. Configure GitHub Node (Node 16 - "GitHub"):
    • Specify the Repository (e.g., your-username/your-repo).
    • Specify the Branch (e.g., main).
    • Set the File Path to the directory where your workflow JSON files are located (e.g., workflows/).
    • Ensure the Operation is set to Get All Files.
  4. Configure HTTP Request Nodes (Nodes 19, 565, 826):
    • The "HTTP Request" nodes (Node 19, 565) and "n8n" node (Node 826) are pre-configured to use the n8n API credential. Ensure this credential is correctly set up.
  5. Execute the Workflow: Click "Execute Workflow" to run the deployment process. The workflow will fetch, process, and deploy your workflows.

Important Notes:

  • Credential Placeholders: When new credentials are created, they will have placeholder values. You MUST manually update these credentials in your n8n instance with the correct sensitive information after the workflow runs.
  • Error Handling: The workflow includes a "Stop and Error" node (Node 528) to halt execution if a critical error occurs during deployment.
  • Idempotency: The workflow checks for existing credentials to avoid creating duplicates, making it somewhat idempotent for credential creation. However, it will always attempt to deploy the latest version of the workflow if it finds a new or updated JSON.

Related Templates

Send severe weather alerts from Visual Crossing to Telegram

How it works This workflow automates the process of fetching weather forecasts for your home location, including severe weather alerts, and sends timely notifications. It uses the Visual Crossing API for detailed weather data and integrates with Telegram (or other messaging services) for messaging and alerts. Step-by-step In summary, the workflow runs every hour, grabs the current day's weather conditions for [your city/location of interest], and returns only those items that truly contain one or more weather alerts. 📅 Step 1: Hourly Trigger The workflow begins with the Hourly Trigger node, which is a scheduleTrigger. This node acts as the clock that initiates the entire process at regular hourly intervals. 🌤️ Step 2: Fetch Weather Data Immediately after the trigger, the workflow moves to the Meteo node, an httpRequest. This node makes an external API call to fetch weather data for your specified location. API Used: Visual Crossing Web Services Authentication: Uses your API key (key=[API KEY]) Response format: JSON 🌪🌀 Step 3: Check for Severe Weather The JSON weather data output is analyzed, and if severe weather conditions or alerts are detected, the workflow sends the alert via your preferred communication channel(s). Optional You can replace the Telegram node with email, WhatsApp, SMS notifications, or add multiple notification nodes to receive severe weather alerts across all desired channels.

Razvan BaraBy Razvan Bara
32

Multi-channel workflow error alerts with Telegram, Gmail & messaging apps

The Error Notification workflow is designed to instantly notify you whenever any other n8n workflow encounters an error, using popular communication channels like Telegram and Gmail—with optional support for Discord, Slack, and WhatsApp. 💡 Why Use Error Notification workflow? Immediate Awareness: Get instant alerts when workflows fail, preventing unnoticed errors and downtime. Multi-Channel Flexibility: Notify your team via Telegram, Gmail, and optionally Slack, Discord, or WhatsApp. Detailed Context: Receive rich error information including the error message, node name, time, and execution link for quicker fixes. Easy Integration: Built with native n8n nodes and customizable code, simple to adopt without complex setup. Open Source & Free: Use and adapt this workflow at no cost, making professional error monitoring accessible. ⚡ Who Is This For? n8n Workflow Developers: Quickly spot and respond to automation issues in development or production. Operations Teams: Maintain uptime and swiftly troubleshoot errors across multiple workflows. Small to Medium Businesses: Gain professional error alerting without expensive monitoring tools. Automation Enthusiasts: Enhance your automation reliability with real-time failure notifications. ❓ What Problem Does It Solve? This workflow embedd error detection and notification directly within your n8n instance. It automates the process of catching errors as they occur, compiling meaningful context, and delivering it instantly via your preferred messaging platforms. This drastically reduces your response time to issues and streamlines error management, improving your automation reliability and operational confidence. 🔧 What This Workflow Does ⏱ Trigger: Listens for any error generated in your n8n workflows using the n8n Error Trigger node. 📎 Step 2: Executes a Code node that formats a detailed error message capturing workflow name, error node, description, timestamp, and an execution URL. 🔍 Step 3: Sends the formatted error notification to multiple communication channels: Telegram and Gmail by default, plus optionally Discord, Slack, and WhatsApp (disabled by default). 💌 Step 4: Delivers rich, parsed HTML-formatted messages to ensure error readability and immediate actionability. 🔐 Setup Instructions Import the provided .json file into your n8n instance (Cloud or self-hosted). Set up credentials: Gmail OAuth credentials for sending emails via Gmail node Telegram API credentials for Telegram notifications (Optional) Discord Webhook URL credential for Discord notifications (Optional) Slack Webhook credential for Slack notifications (Optional) WhatsApp connection credentials (if enabled) Customize the Code node if needed to adjust the error message format or target chat IDs. Update the chat IDs and recipient details in each notification node according to your channels. Test the workflow by manually triggering an error in another workflow to verify proper notifications. 🧩 Pre-Requirements Active n8n instance (cloud or self-hosted) with version supporting Error Trigger node Telegram bot credentials and chat ID (Optional) Gmail, Discord, Slack, or WhatsApp accounts and webhook credentials if you want to use those channels 🛠️ Customize It Further Enable and configure additional notification nodes like Slack or WhatsApp to fit your team's communication style. Customize the error message template in the Code node to include extra metadata or format it differently (e.g., markdown). Integrate with incident management tools via webhook nodes or create tickets automatically on error. 🧠 Nodes Used Error Trigger Code Telegram Gmail Discord (disabled) Slack (disabled) WhatsApp (disabled) Sticky Note (for description) 📞 Support Made by: khaisa Studio Tag: notification,error,monitoring,workflow,automation,alerts Category: Monitoring & Alerts Need a custom? Need a custom? contact me on LinkedIn or Web

Khairul MuhtadinBy Khairul Muhtadin
3028

Automate invoice processing from Gmail with Azure GPT-4.1 and human verification

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This n8n workflow automates invoice management by integrating Gmail, PDF analysis, and Azure OpenAI GPT-4.1, with an optional human verification step for accuracy and control. It's ideal for businesses or individuals who regularly receive invoice emails and want to streamline their accounts payable process with minimal manual effort. The system continuously monitors Gmail for new messages from specified senders. When it detects an email with a PDF attachment and relevant subject line (e.g., "Invoice"), it automatically extracts text from the PDF, analyzes it using Azure OpenAI, and determines if it is a valid invoice. If the AI is uncertain, the workflow sends a manual approval request to a human reviewer. Valid invoices are saved to local storage with a timestamped filename, and a confirmation email is sent upon successful processing. 🎯 Who This Is For Small to medium businesses Freelancers or consultants who receive invoices via email IT or automation teams looking to streamline document workflows Anyone using n8n with access to Gmail and Azure OpenAI ✅ Features Gmail Monitoring – Automatically checks for new emails from trusted senders AI-Powered Invoice Detection – Uses Azure GPT-4.1 to intelligently verify PDF contents PDF Text Extraction – Extracts readable text for analysis Human-in-the-Loop Verification – Requests approval when AI confidence is low Secure File Storage – Saves invoices locally with structured filenames Email Notifications – Sends confirmations or manual review alerts ⚙️ Setup Instructions Prerequisites An active n8n instance (self-hosted or cloud) A Gmail account with OAuth2 credentials An Azure OpenAI account with access to the GPT-4.1 model A local directory for saving invoices (e.g., C:/Test/Invoices/) Gmail OAuth2 Setup In n8n, create Gmail OAuth2 credentials. Configure it with Gmail API access (read emails and attachments). Update the Gmail Trigger node to filter by sender email (e.g., sender@gmail.com). Azure OpenAI Setup Create Azure OpenAI API credentials in n8n. Ensure your endpoint is correctly set and GPT-4.1 access is enabled. Link the credentials in the AI Analysis node. Customize Workflow Settings Sender Email – Update in Gmail Trigger Notification Email – Update in Send Notification node Save Directory – Change in Save Invoice node Testing the Workflow Send a test email from the configured sender with a PDF invoice. Wait for the workflow to trigger and check for: File saved in the directory Confirmation email received Manual review request (if needed) 🔄 Workflow Steps Gmail Trigger → Check for PDF Invoice → Extract PDF Text → Analyze with GPT-4.1 → ↳ If Invoice: Save & Notify ↳ If Uncertain: Request Human Review ↳ If Not Invoice: Send Invalid Alert

Sachin ShresthaBy Sachin Shrestha
647