Back to Catalog

Transfer workflows with credentials & sub-workflow management between n8n instances

Arthur BraghettoArthur Braghetto
342 views
2/3/2026
Official Page

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

Export Workflows Between n8n Instances

Copy workflows between n8n instances β€” with optional credential export and automatic sub-workflow adjustments.

🧠 How it Works

This workflow copies a selected workflow from a SOURCE n8n server to a TARGET server and guides you through safe checks:

  • Name conflict check: If a workflow with the same name exists on the target the export is stopped.
  • Sub-workflows: Detects calls to sub-workflows.
    • If all sub-workflows exist on the target (same names), references are auto-updated and the export continues.
    • If any are missing, the form shows what’s missing and lets you cancel or proceed anyway.
  • Credentials: Detects nodes using credentials and lets you export those credentials along with the workflow.
    • The workflow can only apply credential corrections for the credentials that you choose to export with it.
    • At the end, the form lists which credentials were successfully exported.

πŸ’‘ For in-depth behavior and edge cases, see the Notes inside the workflow (Setup, How It Works, and Credential Issues).

πŸš€ How to Use

  1. Run this workflow on your SOURCE server.
  2. Follow the step-by-step form: pick the workflow to export, choose whether to include credentials, and review sub-workflow checks. Done.

βš™οΈ Setup

  • Create an n8n API key on both servers (SOURCE and TARGET).
  • On the SOURCE server, create two n8n API credentials in n8n: one for SOURCE and one for TARGET (using the respective base URL and key).
  • Configure the nodes in this workflow with these two credentials.
  • Detailed step-by-step instructions are available in the workflow notes.

βœ… Once configured, you’ll be ready to migrate workflows between servers in just a few clicks.

n8n Workflow and Credential Transfer Tool

This n8n workflow provides a robust solution for managing and transferring n8n workflows and their associated credentials between different n8n instances. It's designed to simplify the process of backing up, migrating, or replicating workflows, especially in environments where direct database access or manual configuration is cumbersome.

What it does

This workflow automates the following steps:

  1. Triggers Workflow Execution: The workflow is initiated by an n8n Form Trigger, allowing for manual input to control the transfer process.
  2. Executes CLI Commands: It leverages the Execute Command node to interact with the n8n CLI.
    • It first attempts to export all workflows and credentials using n8n export:workflow --all and n8n export:credentials --all.
    • It then attempts to import workflows and credentials using n8n import:workflow and n8n import:credentials.
  3. Conditional Logic for Export/Import: An If node checks for a specific condition (likely an input from the form trigger) to determine whether to proceed with the export or import operations.
  4. File Operations:
    • Read/Write Files from Disk: This node is used to save the exported workflow and credential data to disk and to read the files for import.
    • Extract from File: This node processes the content of the exported files, likely to prepare them for import or further manipulation.
  5. Data Transformation:
    • Edit Fields (Set): This node is used to manipulate data, potentially setting file paths, names, or other parameters for the export/import commands.
    • Split Out: This node helps in processing multiple workflows or credentials if they are exported as a collection.
    • Code: A custom code node is included, which could be used for advanced data manipulation, formatting, or error handling during the transfer process.
  6. No Operation: A No Operation node is present, likely as a placeholder or for debugging purposes, indicating a path where no action is taken.

Prerequisites/Requirements

  • n8n Instance(s): You need at least two n8n instances (source and target) if you intend to transfer between them.
  • n8n CLI Access: The n8n instance running this workflow must have access to the n8n CLI (Command Line Interface) and the necessary permissions to execute n8n export and n8n import commands. This typically means the n8n server user needs appropriate shell access.
  • File System Access: The n8n instance needs read/write access to a local file system where exported workflows and credentials can be temporarily stored and read from.
  • n8n Form Trigger: The workflow is initiated via an n8n form, so an active n8n instance with the form trigger enabled is required.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Execute Command Node:
    • Ensure the Execute Command nodes are configured with the correct n8n CLI commands for your environment. The current commands are n8n export:workflow --all and n8n export:credentials --all for export, and n8n import:workflow and n8n import:credentials for import. You may need to specify paths or other options depending on your setup.
    • Verify that the user running the n8n process has the necessary permissions to execute these CLI commands and to read/write files to the specified disk locations.
  3. Configure Read/Write Files from Disk: Adjust the file paths in the Read/Write Files from Disk nodes to match your desired temporary storage locations for the exported JSON files.
  4. Configure If Node: Review the condition in the If node (id: 20) to ensure it correctly branches the workflow for export or import based on your input. You will likely need to link this to an input field from the On form submission node.
  5. Configure n8n Form Trigger: Customize the form fields in the On form submission node (id: 1225) to provide the necessary input for controlling the workflow (e.g., a dropdown to select "export" or "import", or fields for specific workflow IDs if not exporting/importing all).
  6. Activate the Workflow: Once configured, activate the workflow. You can then trigger it via the generated n8n form to perform workflow and credential transfers.

This workflow provides a powerful foundation for managing your n8n assets programmatically, offering flexibility and control over your deployment strategy.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required β€” one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- βš™οΈ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (β€œRepair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (β€œRepair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row β€” enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚑ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- πŸ› οΈ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31