LIVEAI Bootcamps · May 2026 · 🇫🇷 CET
Resources · Integrations · n8n FREE · 2026n8n logo featuring a modern, abstract blue-green icon and the lowercase company name

n8n N8N INTEGRATION: AUTOMATE N8N WITH N8N

Looking to automate your n8n instance management directly from within n8n itself? The native n8n integration gives you access to 1 trigger and 14 actions to build powerful meta-automation workflows that manage your workflows, executions, credentials, and audits programmatically.

This self-referential integration is particularly powerful for n8n administrators and power users who want to automate instance maintenance, workflow deployment pipelines, or execution monitoring. Instead of manually managing your automations through the UI, you can create workflows that create, update, publish, and delete other workflows—essentially automating your automation platform.

In this guide, you'll discover how to connect n8n to itself, explore every available trigger and action in detail, and learn practical use cases to supercharge your workflow management.

Need help

Need help automating N8N with n8n?

Our team will get back to you in minutes.

Reply within 1 business hour
Why automate

Why automate N8N with n8n?

The n8n native integration unlocks 1 system trigger and 14 distinct actions spanning four resource types: Workflows, Executions, Credentials, and Audits. This means you can build comprehensive automation pipelines that monitor and manage every aspect of your n8n instance without leaving the platform.

The benefits are substantial. Time savings become significant when you automate repetitive tasks like deploying workflow updates across environments, cleaning up old executions, or generating audit reports. Improved responsiveness comes from triggers that fire instantly when workflows are published or updated, allowing you to implement CI/CD-style deployment pipelines. Zero oversight is achieved through automated monitoring—every execution, every workflow change can be tracked and acted upon automatically. Seamless integration means you can connect n8n management to your existing tools: notify Slack when workflows fail, sync workflow definitions to Git, or create tickets when audits flag issues.

Concrete use cases include: automatically backing up workflow definitions when they're updated, implementing approval workflows before publishing changes to production, bulk-managing credentials across multiple workflows, monitoring execution health and alerting on failures, and generating regular security audit reports.

Credentials

How to connect N8N to n8n?

  1. !
    1 step

    How to connect N8N to n8n?

    1. 01

      Add the node

      Connecting n8n to itself requires API credentials from your n8n instance. The integration uses API Key authentication to securely access your n8n's internal API.Basic configuration:Generate an API Key: Navigate to your n8n settings, find the API section, and generate a new API key with appropriate permissions for the operations you need.Create the credential in n8n: In your workflow, add an n8n node, click on "Credential to connect with", and select "Create New".Configure the connection: Enter your n8n instance URL (e.g., https://your-instance.n8n.cloud or your self-hosted URL) and paste your API key.Test the connection: Save the credential and test it by running a simple "Get Many Workflows" operation to verify everything works correctly.

    N8N credentials
    TIP
    💡 TIP: Create separate API keys with limited permissions for different workflow purposes. For example, use a read-only key for monitoring workflows and a full-access key only for workflows that need to modify other workflows. This follows the principle of least privilege and makes your automation more secure. Need help setting up complex n8n configurations? Our n8n training covers advanced credential management and security best practices.
Need help

Need help automating N8N with n8n?

Our team will get back to you in minutes.

Reply within 1 business hour
Triggers

N8N triggers available in n8n

  1. 01
    Trigger 01

    n8n Trigger

    The n8n Trigger is your gateway to event-driven automation within your n8n instance. This powerful trigger monitors system-level events and automatically fires your workflow whenever specified activities occur, enabling you to build reactive automation that responds instantly to changes in your n8n environment.

    Configuration Parameters: Events - This is a required multi-select field where you choose which n8n system events will activate the trigger. You can select multiple events from the available list, and the workflow will fire when any of them occur. Available events include "Published Workflow Updated", "Instance Started", "Workflow Published", and more.

    Typical Use Cases: Deployment notifications (trigger a workflow when any workflow is published to notify your team via Slack or email), backup on update (automatically save a workflow's JSON definition to a Git repository when a published workflow is updated), instance health monitoring (fire alerting workflows when your n8n instance starts), and audit logging (capture every workflow publication event and store details in a database).

    When to use it: This trigger is essential for n8n administrators who need visibility into instance activity, teams implementing CI/CD practices for workflow management, or anyone wanting to automate responses to system events without manual polling.

    n8n Trigger
Actions

N8N actions available in n8n

  1. 01
    Action 01

    N8n Workflow Update

    This action allows you to programmatically modify existing workflows in your n8n instance. It's invaluable for implementing bulk updates, automated maintenance, or deployment pipelines that need to push changes to workflows without manual intervention.

    Key Parameters: Credential to connect with (required dropdown for n8n account credentials), Resource (required, set to "Workflow"), Operation (required, set to "Update"), Workflow (required field to specify which workflow to update), and Workflow Object (optional text area accepting a JSON object representing the workflow definition or specific properties to modify).

    Use Cases: Bulk update node versions across multiple workflows, implement environment-specific configuration changes during deployment, and automatically fix or patch workflows based on audit findings.

    N8n Workflow Update
  2. 02
    Action 02

    N8n Workflow: Get Version

    This action retrieves a specific version of a workflow, enabling you to access historical states of your workflows. Perfect for version control, rollback scenarios, or auditing changes over time.

    Key Parameters: Credential to connect with (required dropdown for authentication), Resource (required, set to "Workflow"), Operation (required, set to "Get Version"), Workflow (required field to identify the target workflow), and Version ID (required text field where you enter the specific version number to retrieve).

    Use Cases: Build a workflow diff tool comparing versions, implement rollback functionality in deployment pipelines, and audit workflow changes by retrieving and comparing multiple versions.

    N8n Workflow: Get Version
  3. 03
    Action 03

    N8n Workflow: Get Many

    This action retrieves multiple workflows from your n8n instance in a single operation. It's essential for bulk operations, reporting, and building workflow management dashboards.

    Key Parameters: Credential to connect with (required dropdown), Resource (required, set to "Workflow"), Operation (required, set to "Get Many"), Return All (optional toggle that, when enabled, returns all workflows regardless of limits), and Filters (optional section to add conditions filtering workflows by properties like name, ID, or tags).

    Use Cases: Generate reports on all workflows in your instance, find workflows matching specific criteria for bulk updates, and build a custom workflow catalog or documentation system.

    N8n Workflow: Get Many
  4. 04
    Action 04

    Get Workflow

    This action retrieves complete information about a single specific workflow. Use it when you need detailed data about one workflow for processing, backup, or analysis.

    Key Parameters: Credential to connect with (required dropdown for authentication), Resource (required, set to "Workflow"), Operation (required, set to "Get"), and Workflow (required field to specify the workflow, either from a list or by entering its ID).

    Use Cases: Fetch workflow definitions for backup to external storage, retrieve workflow details for documentation generation, and load workflow configuration for comparison or validation.

    Get Workflow
  5. 05
    Action 05

    N8n Workflow Delete

    This action permanently removes a workflow from your n8n instance. Use with caution—it's powerful for cleanup operations but irreversible.

    Key Parameters: Credential to connect with (required dropdown for n8n account selection), Resource (required, set to "Workflow"), Operation (required, set to "Delete"), and Workflow (required field to specify which workflow to delete, selectable from a list or by ID).

    Use Cases: Automated cleanup of test or temporary workflows, remove deprecated workflows as part of maintenance routines, and implement workflow lifecycle management with automatic expiration.

    N8n Workflow Delete
  6. 06
    Action 06

    Unpublish Workflow

    This action deactivates a published workflow, stopping it from executing while preserving its definition. Useful for temporary disabling or controlled rollbacks.

    Key Parameters: Credential to connect with (required dropdown for authentication credentials), Resource (required, set to "Workflow"), Operation (required, set to "Unpublish"), and Workflow (required field to select the workflow to unpublish from a list or by ID).

    Use Cases: Emergency stop for problematic workflows without deleting them, implement scheduled maintenance windows by unpublishing workflows temporarily, and create approval workflows that unpublish until review is complete.

    Unpublish Workflow
  7. 07
    Action 07

    N8n Create Workflow

    This action creates a brand new workflow in your n8n instance from a JSON definition. Essential for deployment pipelines, template systems, or programmatic workflow generation.

    Key Parameters: Credential to connect with (required dropdown for n8n account credentials), Resource (required, set to "Workflow"), Operation (required, set to "Create"), and Workflow Object (required text area accepting a JSON object defining the complete workflow structure including name, nodes, connections, and settings).

    Use Cases: Deploy workflows from version control (Git) to n8n, generate workflows dynamically based on templates, and clone workflows across different n8n instances.

    N8n Create Workflow
  8. 08
    Action 08

    N8n Workflow Publish

    This action activates a workflow, making it live and ready to execute. The final step in any deployment pipeline.

    Key Parameters: Credential to connect with (required dropdown for authentication), Resource (required, set to "Workflow"), Operation (required, set to "Publish"), Workflow (required field to specify which workflow to publish, from a list or by ID), and Additional Fields (optional section for extra parameters).

    Use Cases: Automate deployment by publishing after successful tests, schedule workflow publications for specific times, and implement approval workflows that publish only after sign-off.

    N8n Workflow Publish
  9. 09
    Action 09

    N8n Execution: Delete

    This action removes execution records from your n8n instance. Crucial for data hygiene, compliance, and managing storage.

    Key Parameters: Credential to connect with (required dropdown for n8n credentials), Resource (required, set to "Execution"), Operation (required, set to "Delete"), and Execution ID (required text field for the unique identifier of the execution to remove).

    Use Cases: Automated cleanup of old execution logs, remove sensitive execution data for compliance, and manage storage by deleting successful executions while keeping failures.

    N8n Execution: Delete
  10. 10
    Action 10

    N8n Execution: Get Many

    This action retrieves multiple execution records, enabling monitoring, reporting, and analysis of workflow runs.

    Key Parameters: Credential to connect with (required dropdown for authentication), Resource (required, set to "Execution"), Operation (required, set to "Get Many"), Return All (optional toggle to retrieve all records), Limit (optional numeric field to cap results, e.g., 100), Filters (optional section to filter by status, workflow, or date), and Options (optional additional configuration settings).

    Use Cases: Build execution monitoring dashboards, generate daily/weekly execution reports, and find failed executions for alerting or retry logic.

    N8n Execution: Get Many
  11. 11
    Action 11

    N8n Execution: Get

    This action retrieves detailed information about a single execution, including input/output data, status, and timing.

    Key Parameters: Credential to connect with (required dropdown for credentials), Resource (required, set to "Execution"), Operation (required, set to "Get"), Execution ID (required text field for the specific execution identifier), and Options (optional section for additional parameters).

    Use Cases: Debug specific workflow runs by examining execution details, build retry logic that analyzes why an execution failed, and archive important execution data to external storage.

    N8n Execution: Get
  12. 12
    Action 12

    Get Schema

    This action retrieves the schema definition for a specific credential type, useful for dynamic credential management and validation.

    Key Parameters: Credential to connect with (required dropdown for n8n authentication), Resource (required, set to "Credential"), Operation (required, set to "Get Schema"), and Credential Type (required text field specifying the credential type, e.g., "n8nApi").

    Use Cases: Build dynamic forms for credential creation, validate credential data before creation, and document available credential types and their requirements.

    Get Schema
  13. 13
    Action 13

    Delete Credential

    This action removes a credential from your n8n instance. Important for security hygiene and credential rotation processes.

    Key Parameters: Credential to connect with (required dropdown for authentication), Resource (required, set to "Credential"), Operation (required, set to "Delete"), and Credential ID (required text field for the unique identifier of the credential to delete).

    Use Cases: Automated credential rotation (delete old, create new), clean up unused or expired credentials, and security response: quickly revoke compromised credentials.

    Delete Credential
  14. 14
    Action 14

    Create Credential

    This action creates new credentials in your n8n instance, enabling automated credential provisioning and management.

    Key Parameters: Credential to connect with (required dropdown for n8n authentication), Resource (required, set to "Credential"), Operation (required, set to "Create"), Name (required text field for the credential name, e.g., "n8n account"), Credential Type (required text field specifying the type, e.g., "n8nApi"), and Data (required JSON/code editor for the actual credential data and secrets).

    Use Cases: Automated credential provisioning for new integrations, sync credentials from a secrets manager to n8n, and implement credential rotation by creating new credentials programmatically.

    Create Credential
  15. 15
    Action 15

    N8n Audit Generate

    This action generates security and compliance audit reports for your n8n instance, crucial for governance and security monitoring.

    Key Parameters: Credential to connect with (required dropdown for n8n credentials), Resource (required, set to "Audit"), Operation (required, set to "Generate"), and Additional Options (optional section for adding filters or specific audit criteria).

    Use Cases: Schedule weekly security audit reports, trigger audits after deployment to verify compliance, and build automated security monitoring with audit result analysis. Learn how to integrate audits with Airtable for data tracking or Notion for documentation.

    N8n Audit Generate
You've seen the integration

Build your first workflow with our team

Drop your email and we'll send you the catalog of automations you can ship today.

  • Free n8n & Make scenarios to import
  • Step-by-step setup docs
  • Live cohort + community support

Frequently asked questions

  • Is the n8n n8n integration free to use?
    Yes, the native n8n integration is completely free and included with all n8n installations, whether you're using n8n Cloud or self-hosting. There are no additional costs or premium tiers for accessing the n8n node. However, you'll need to generate API credentials from your n8n instance, which requires appropriate access permissions. For n8n Cloud, API access is included in all plans. For self-hosted instances, ensure your configuration allows API access and that you've generated valid API keys.
  • Can I use the n8n integration to manage workflows across different n8n instances?
    Absolutely! While the integration connects to one n8n instance per credential, you can create multiple n8n credentials pointing to different instances (staging, production, different teams' instances) and use them within the same workflow. This is powerful for building deployment pipelines that push workflows from development to production, syncing workflows between instances, or creating a centralized management dashboard that monitors multiple n8n deployments. Just ensure each instance has its own API credentials configured. If you're looking for alternatives, explore how Make automation handles similar use cases.
  • What happens if I delete a workflow or execution using these actions—can I recover it?
    Deletion actions are permanent and immediate. Once you execute a "Delete Workflow" or "Delete Execution" action, the data is removed from your n8n instance and cannot be recovered through n8n itself. For this reason, it's highly recommended to implement backup workflows that save workflow definitions to external storage (like Git, S3, or Google Drive using our auto-backup workflow) before any deletion operations. Consider building a "soft delete" pattern where workflows are first unpublished and archived externally before actual deletion occurs. For comprehensive n8n troubleshooting, check our dedicated guide.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.