@n8n-as-code/skills 0.12.1 → 0.13.0

package/dist/assets/n8n-docs-complete.json

@@ -1,8 +1,8 @@
 {
-  "generatedAt": "2026-01-30T17:40:48.329Z",
+  "generatedAt": "2026-02-02T12:44:18.972Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1244,
+  "totalPages": 1243,
   "statistics": {
     "byCategory": {
       "other": 509,
@@ -12,7 +12,7 @@
       "code": 38,
       "data": 20,
       "flow-logic": 8,
-      "hosting": 76,
+      "hosting": 75,
       "integrations": 305,
       "cluster-nodes": 96,
       "trigger-nodes": 107,
@@ -702,11 +702,10 @@
     },
     "hosting": {
       "description": "Self-hosting, deployment, and infrastructure",
-      "totalPages": 76,
+      "totalPages": 75,
       "pages": [
         "page-0149",
         "page-0150",
-        "page-0151",
         "page-0152",
         "page-0153",
         "page-0154",
@@ -12701,181 +12700,93 @@
     },
     {
       "id": "page-0150",
-      "title": "CLI commands",
-      "url": "https://docs.n8n.io/hosting/cli-commands/index.md",
-      "urlPath": "hosting/cli-commands/index.md",
+      "title": "Community vs Enterprise",
+      "url": "https://docs.n8n.io/hosting/community-edition-features/index.md",
+      "urlPath": "hosting/community-edition-features/index.md",
       "category": "hosting",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# CLI commands for n8n\n\nn8n includes a CLI (command line interface), allowing you to perform actions using the CLI rather than the n8n editor. These include starting workflows, and exporting and importing workflows and credentials.\n\n## Running CLI commands\n\nYou can use CLI commands with self-hosted n8n. Depending on how you choose to install n8n, there are differences in how to run the commands:\n\n- npm: the `n8n` command is directly available. The documentation uses this in the examples below.\n\n- Docker: the `n8n` command is available within your Docker container:\n\n  ```\n  docker exec -u node -it <n8n-container-name> <n8n-cli-command>\n  ```\n\n## Start a workflow\n\nYou can start workflows directly using the CLI.\n\nExecute a saved workflow by its ID:\n\n```\nn8n execute --id <ID>\n```\n\n## Change the active status of a workflow\n\nYou can change the active status of a workflow using the CLI.\n\nRestart required\n\nThese commands operate on your n8n database. If you execute them while n8n is running, the changes don't take effect until you restart n8n.\n\nSet the active status of a workflow by its ID to false:\n\n```\nn8n update:workflow --id=<ID> --active=false\n```\n\nSet the active status of a workflow by its ID to true:\n\n```\nn8n update:workflow --id=<ID> --active=true\n```\n\nSet the active status to false for all the workflows:\n\n```\nn8n update:workflow --all --active=false\n```\n\nSet the active status to true for all the workflows:\n\n```\nn8n update:workflow --all --active=true\n```\n\n## Export entities\n\nYou can export your database entities from n8n using the CLI. This tooling allows you to export all entity types from one database type, such as SQLite, and import them into another database type, such as Postgres.\n\nCommand flags:\n\n| Flag                                | Description                                                                                    |\n| ----------------------------------- | ---------------------------------------------------------------------------------------------- |\n| --help                              | Help prompt.                                                                                   |\n| --outputDir                         | Output directory path                                                                          |\n| --includeExecutionHistoryDataTables | Include execution history data tables, these are excluded by default as they can be very large |\n\n```\nn8n export:entities --outputDir=./outputs --includeExecutionHistoryDataTables=true\n```\n\n## Export workflows and credentials\n\nYou can export your workflows and credentials from n8n using the CLI.\n\nCommand flags:\n\n| Flag        | Description                                                                                 |\n| ----------- | ------------------------------------------------------------------------------------------- |\n| --help      | Help prompt.                                                                                |\n| --all       | Exports all workflows/credentials.                                                          |\n| --backup    | Sets --all --pretty --separate for backups. You can optionally set --output.                |\n| --id        | The ID of the workflow to export.                                                           |\n| --output    | Outputs file name or directory if using separate files.                                     |\n| --pretty    | Formats the output in an easier to read fashion.                                            |\n| --separate  | Exports one file per workflow (useful for versioning). Must set a directory using --output. |\n| --decrypted | Exports the credentials in a plain text format.                                             |\n\n### Workflows\n\nExport all your workflows to the standard output (terminal):\n\n```\nn8n export:workflow --all\n```\n\nExport a workflow by its ID and specify the output file name:\n\n```\nn8n export:workflow --id=<ID> --output=file.json\n```\n\nExport all workflows to a specific directory in a single file:\n\n```\nn8n export:workflow --all --output=backups/latest/file.json\n```\n\nExport all the workflows to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:workflow --backup --output=backups/latest/\n```\n\n### Credentials\n\nExport all your credentials to the standard output (terminal):\n\n```\nn8n export:credentials --all\n```\n\nExport credentials by their ID and specify the output file name:\n\n```\nn8n export:credentials --id=<ID> --output=file.json\n```\n\nExport all credentials to a specific directory in a single file:\n\n```\nn8n export:credentials --all --output=backups/latest/file.json\n```\n\nExport all the credentials to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:credentials --backup --output=backups/latest/\n```\n\nExport all the credentials in plain text format. You can use this to migrate from one installation to another that has a different secret key in the configuration file.\n\nSensitive information\n\nAll sensitive information is visible in the files.\n\n```\nn8n export:credentials --all --decrypted --output=backups/decrypted.json\n```\n\n## Import entities\n\nYou can import entities from a previous `export:entities` command using this command, it allows importing of entities into a database type that differs from the exported database type. Current supported database types include: SQLite, Postgres.\n\nThe database is expected to be empty prior to import, this can be forced with the `--truncateTables` parameter.\n\nCommand flags:\n\n| Flag             | Description                                        |\n| ---------------- | -------------------------------------------------- |\n| --help           | Help prompt.                                       |\n| --inputDir       | Input directory that holds output files for import |\n| --truncateTables | Truncate tables before import                      |\n\n```\nn8n import:entities --inputDir ./outputs --truncateTables true\n```\n\n## Import workflows and credentials\n\nYou can import your workflows and credentials from n8n using the CLI.\n\nUpdate the IDs\n\nWhen exporting workflows and credentials, n8n also exports their IDs. If you have workflows and credentials with the same IDs in your existing database, they will be overwritten. To avoid this, delete or change the IDs before importing.\n\nAvailable flags:\n\n| Flag        | Description                                                                                |\n| ----------- | ------------------------------------------------------------------------------------------ |\n| --help      | Help prompt.                                                                               |\n| --input     | Input file name or directory if you use --separate.                                        |\n| --projectId | Import the workflow or credential to the specified project. Can't be used with `--userId`. |\n| --separate  | Imports `*.json` files from directory provided by --input.                                 |\n| --userId    | Import the workflow or credential to the specified user. Can't be used with `--projectId`. |\n\nMigrating to SQLite\n\nn8n limits workflow and credential names to 128 characters, but SQLite doesn't enforce size limits.\n\nThis might result in errors like **Data too long for column name** during the import process.\n\nIn this case, you can edit the names from the n8n interface and export again, or edit the JSON file directly before importing.\n\n### Workflows\n\nImport workflows from a specific file:\n\n```\nn8n import:workflow --input=file.json\n```\n\nImport all the workflow files as JSON from the specified directory:\n\n```\nn8n import:workflow --separate --input=backups/latest/\n```\n\n### Credentials\n\nImport credentials from a specific file:\n\n```\nn8n import:credentials --input=file.json\n```\n\nImport all the credentials files as JSON from the specified directory:\n\n```\nn8n import:credentials --separate --input=backups/latest/\n```\n\n## License\n\n### Clear\n\nClear your existing license from n8n's database and reset n8n to default features:\n\n```\nn8n license:clear\n```\n\nIf your license includes [floating entitlements](../../glossary/#entitlement-n8n), running this command will also attempt to release them back to the pool, making them available for other instances.\n\n### Info\n\nDisplay information about the existing license:\n\n```\nn8n license:info\n```\n\n## User management\n\nYou can reset user management using the n8n CLI. This returns user management to its pre-setup state. It removes all user accounts.\n\nUse this if you forget your password, and don't have SMTP set up to do password resets by email.\n\n```\nn8n user-management:reset\n```\n\n### Disable MFA for a user\n\nIf a user loses their recovery codes you can disable MFA for a user with this command. The user will then be able to log back in to set up MFA again.\n\n```\nn8n mfa:disable --email=johndoe@example.com\n```\n\n### Disable LDAP\n\nYou can reset the LDAP settings using the command below.\n\n```\nn8n ldap:reset\n```\n\n## Uninstall community nodes and credentials\n\nYou can manage [community nodes](../../integrations/community-nodes/installation/) using the n8n CLI. For now, you can only uninstall community nodes and credentials, which is useful if a community node causes instability.\n\nCommand flags:\n\n| Flag         | Description                                                                                                                |\n| ------------ | -------------------------------------------------------------------------------------------------------------------------- |\n| --help       | Show CLI help.                                                                                                             |\n| --credential | The credential type. Get this value by visiting the node's `<NODE>.credential.ts` file and getting the value of `name`.    |\n| --package    | Package name of the community node.                                                                                        |\n| --uninstall  | Uninstalls the node.                                                                                                       |\n| --userId     | The ID of the user who owns the credential. On self-hosted, query the database. On cloud, query the API with your API key. |\n\n### Nodes\n\nUninstall a community node by package name:\n\n```\nn8n community-node --uninstall --package <COMMUNITY_NODE_NAME>\n```\n\nFor example, to uninstall the [Evolution API community node](https://www.npmjs.com/package/n8n-nodes-evolution-api), type:\n\n```\nn8n community-node --uninstall --package n8n-nodes-evolution-api\n```\n\n### Credentials\n\nUninstall a community node credential:\n\n```\nn8n community-node --uninstall --credential <CREDENTIAL_TYPE> --userId <ID>\n```\n\nFor example, to uninstall the [Evolution API community node credential](https://www.npmjs.com/package/n8n-nodes-evolution-api), visit the [repository](https://github.com/oriondesign2015/n8n-nodes-evolution-api) and navigate to the [`credentials.ts` file](https://github.com/oriondesign2015/n8n-nodes-evolution-api/blob/main/credentials/EvolutionApi.credentials.ts) to find the `name`:\n\n```\nn8n community-node --uninstall --credential evolutionApi --userId 1234\n```\n\n## Security audit\n\nYou can run a [security audit](../securing/security-audit/) on your n8n instance, to detect common security issues.\n\n```\nn8n audit\n```\n",
-        "excerpt": "# CLI commands for n8n  n8n includes a CLI (command line interface), allowing you to perform actions using the CLI rather than the n8n editor. These include starting workflows, and exporting and importing workflows and credentials.  ## Running CLI commands  You can use CLI commands with self-hosted n8n. Depending on how you choose to install n8n, there are differences in how to run the commands:  - npm: the `n8n` command is directly available. The documentation uses this in the examples below....",
+        "markdown": "# Community Edition Features\n\nThe community edition includes almost the complete feature set of n8n, except for the features listed here.\n\nThe community edition doesn't include these features:\n\n- [Custom Variables](../../code/variables/)\n- [Environments](../../source-control-environments/)\n- [External secrets](../../external-secrets/)\n- [External storage for binary data](../scaling/external-storage/)\n- [Log streaming](../../log-streaming/) ([Logging](../logging-monitoring/logging/) *is* included)\n- [Multi-main mode](../scaling/queue-mode/#multi-main-setup) ([Queue mode](../scaling/queue-mode/) *is* included)\n- [Projects](../../user-management/rbac/projects/)\n- SSO ([SAML](../securing/set-up-sso/), [LDAP](../../user-management/ldap/))\n- Sharing ([workflows](../../workflows/sharing/), [credentials](../../credentials/credential-sharing/)) (Only the instance owner and the user who creates them can access workflows and credentials)\n- [Version control using Git](../../source-control-environments/)\n\nThese features are available on the Enterprise Cloud plan, including the self-hosted Enterprise edition. Some of these features are available on the Starter and Pro Cloud plan.\n\nSee [pricing](https://n8n.io/pricing/) for reference.\n\n## Registered Community Edition\n\nYou can unlock extra features by registering your n8n community edition. You register with your email and receive a license key.\n\nRegistering unlocks these features for the community edition:\n\n- Folders: Organize your workflows into tidy folders\n- [Debug in editor](../../workflows/executions/debug/): Copy and [pin](../../glossary/#data-pinning-n8n) execution data when working on a workflow\n- [Custom execution data](../../workflows/executions/custom-executions-data/): Save, find, and annotate execution metadata\n\nTo register a new community edition instance, select the option during your initial account creation.\n\nTo register an existing community edition instance:\n\n1. Select the **three dots icon** in the lower-left corner.\n1. Select **Settings** and then **Usage and plan**.\n1. Select **Unlock** to enter your email and then select **Send me a free license key**.\n1. Check your email for the account you entered.\n\nOnce you have a license key, activate it by clicking the button in the license email or by visiting **Options > Settings > Usage and plan** and selecting **Enter activation key**.\n\nOnce activated, your license will not expire. We may change the unlocked features in the future. This will not impact previously unlocked features.\nows and credentials\n\nYou can export your workflows and credentials from n8n using the CLI.\n\nCommand flags:\n\n| Flag        | Description                                                                                 |\n| ----------- | ------------------------------------------------------------------------------------------- |\n| --help      | Help prompt.                                                                                |\n| --all       | Exports all workflows/credentials.                                                          |\n| --backup    | Sets --all --pretty --separate for backups. You can optionally set --output.                |\n| --id        | The ID of the workflow to export.                                                           |\n| --output    | Outputs file name or directory if using separate files.                                     |\n| --pretty    | Formats the output in an easier to read fashion.                                            |\n| --separate  | Exports one file per workflow (useful for versioning). Must set a directory using --output. |\n| --decrypted | Exports the credentials in a plain text format.                                             |\n\n### Workflows\n\nExport all your workflows to the standard output (terminal):\n\n```\nn8n export:workflow --all\n```\n\nExport a workflow by its ID and specify the output file name:\n\n```\nn8n export:workflow --id=<ID> --output=file.json\n```\n\nExport all workflows to a specific directory in a single file:\n\n```\nn8n export:workflow --all --output=backups/latest/file.json\n```\n\nExport all the workflows to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:workflow --backup --output=backups/latest/\n```\n\n### Credentials\n\nExport all your credentials to the standard output (terminal):\n\n```\nn8n export:credentials --all\n```\n\nExport credentials by their ID and specify the output file name:\n\n```\nn8n export:credentials --id=<ID> --output=file.json\n```\n\nExport all credentials to a specific directory in a single file:\n\n```\nn8n export:credentials --all --output=backups/latest/file.json\n```\n\nExport all the credentials to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:credentials --backup --output=backups/latest/\n```\n\nExport all the credentials in plain text format. You can use this to migrate from one installation to another that has a different secret key in the configuration file.\n\nSensitive information\n\nAll sensitive information is visible in the files.\n\n```\nn8n export:credentials --all --decrypted --output=backups/decrypted.json\n```\n\n## Import entities\n\nYou can import entities from a previous `export:entities` command using this command, it allows importing of entities into a database type that differs from the exported database type. Current supported database types include: SQLite, Postgres.\n\nThe database is expected to be empty prior to import, this can be forced with the `--truncateTables` parameter.\n\nCommand flags:\n\n| Flag             | Description                                        |\n| ---------------- | -------------------------------------------------- |\n| --help           | Help prompt.                                       |\n| --inputDir       | Input directory that holds output files for import |\n| --truncateTables | Truncate tables before import                      |\n\n```\nn8n import:entities --inputDir ./outputs --truncateTables true\n```\n\n## Import workflows and credentials\n\nYou can import your workflows and credentials from n8n using the CLI.\n\nUpdate the IDs\n\nWhen exporting workflows and credentials, n8n also exports their IDs. If you have workflows and credentials with the same IDs in your existing database, they will be overwritten. To avoid this, delete or change the IDs before importing.\n\nAvailable flags:\n\n| Flag        | Description                                                                                |\n| ----------- | ------------------------------------------------------------------------------------------ |\n| --help      | Help prompt.                                                                               |\n| --input     | Input file name or directory if you use --separate.                                        |\n| --projectId | Import the workflow or credential to the specified project. Can't be used with `--userId`. |\n| --separate  | Imports `*.json` files from directory provided by --input.                                 |\n| --userId    | Import the workflow or credential to the specified user. Can't be used with `--projectId`. |\n\nMigrating to SQLite\n\nn8n limits workflow and credential names to 128 characters, but SQLite doesn't enforce size limits.\n\nThis might result in errors like **Data too long for column name** during the import process.\n\nIn this case, you can edit the names from the n8n interface and export again, or edit the JSON file directly before importing.\n\n### Workflows\n\nImport workflows from a specific file:\n\n```\nn8n import:workflow --input=file.json\n```\n\nImport all the workflow files as JSON from the specified directory:\n\n```\nn8n import:workflow --separate --input=backups/latest/\n```\n\n### Credentials\n\nImport credentials from a specific file:\n\n```\nn8n import:credentials --input=file.json\n```\n\nImport all the credentials files as JSON from the specified directory:\n\n```\nn8n import:credentials --separate --input=backups/latest/\n```\n\n## License\n\n### Clear\n\nClear your existing license from n8n's database and reset n8n to default features:\n\n```\nn8n license:clear\n```\n\nIf your license includes [floating entitlements](../../glossary/#entitlement-n8n), running this command will also attempt to release them back to the pool, making them available for other instances.\n\n### Info\n\nDisplay information about the existing license:\n\n```\nn8n license:info\n```\n\n## User management\n\nYou can reset user management using the n8n CLI. This returns user management to its pre-setup state. It removes all user accounts.\n\nUse this if you forget your password, and don't have SMTP set up to do password resets by email.\n\n```\nn8n user-management:reset\n```\n\n### Disable MFA for a user\n\nIf a user loses their recovery codes you can disable MFA for a user with this command. The user will then be able to log back in to set up MFA again.\n\n```\nn8n mfa:disable --email=johndoe@example.com\n```\n\n### Disable LDAP\n\nYou can reset the LDAP settings using the command below.\n\n```\nn8n ldap:reset\n```\n\n## Uninstall community nodes and credentials\n\nYou can manage [community nodes](../../integrations/community-nodes/installation/) using the n8n CLI. For now, you can only uninstall community nodes and credentials, which is useful if a community node causes instability.\n\nCommand flags:\n\n| Flag         | Description                                                                                                                |\n| ------------ | -------------------------------------------------------------------------------------------------------------------------- |\n| --help       | Show CLI help.                                                                                                             |\n| --credential | The credential type. Get this value by visiting the node's `<NODE>.credential.ts` file and getting the value of `name`.    |\n| --package    | Package name of the community node.                                                                                        |\n| --uninstall  | Uninstalls the node.                                                                                                       |\n| --userId     | The ID of the user who owns the credential. On self-hosted, query the database. On cloud, query the API with your API key. |\n\n### Nodes\n\nUninstall a community node by package name:\n\n```\nn8n community-node --uninstall --package <COMMUNITY_NODE_NAME>\n```\n\nFor example, to uninstall the [Evolution API community node](https://www.npmjs.com/package/n8n-nodes-evolution-api), type:\n\n```\nn8n community-node --uninstall --package n8n-nodes-evolution-api\n```\n\n### Credentials\n\nUninstall a community node credential:\n\n```\nn8n community-node --uninstall --credential <CREDENTIAL_TYPE> --userId <ID>\n```\n\nFor example, to uninstall the [Evolution API community node credential](https://www.npmjs.com/package/n8n-nodes-evolution-api), visit the [repository](https://github.com/oriondesign2015/n8n-nodes-evolution-api) and navigate to the [`credentials.ts` file](https://github.com/oriondesign2015/n8n-nodes-evolution-api/blob/main/credentials/EvolutionApi.credentials.ts) to find the `name`:\n\n```\nn8n community-node --uninstall --credential evolutionApi --userId 1234\n```\n\n## Security audit\n\nYou can run a [security audit](../securing/security-audit/) on your n8n instance, to detect common security issues.\n\n```\nn8n audit\n```\n",
+        "excerpt": "# Community Edition Features  The community edition includes almost the complete feature set of n8n, except for the features listed here.  The community edition doesn't include these features:  - [Custom Variables](../../code/variables/) - [Environments](../../source-control-environments/) - [External secrets](../../external-secrets/) - [External storage for binary data](../scaling/external-storage/) - [Log streaming](../../log-streaming/) ([Logging](../logging-monitoring/logging/) *is* included...",
         "sections": [
           {
-            "title": "CLI commands for n8n",
+            "title": "Community Edition Features",
             "level": 1,
-            "content": "n8n includes a CLI (command line interface), allowing you to perform actions using the CLI rather than the n8n editor. These include starting workflows, and exporting and importing workflows and credentials."
+            "content": "The community edition includes almost the complete feature set of n8n, except for the features listed here.\n\nThe community edition doesn't include these features:\n\n- [Custom Variables](../../code/variables/)\n- [Environments](../../source-control-environments/)\n- [External secrets](../../external-secrets/)\n- [External storage for binary data](../scaling/external-storage/)\n- [Log streaming](../../log-streaming/) ([Logging](../logging-monitoring/logging/) *is* included)\n- [Multi-main mode](../scaling/queue-mode/#multi-main-setup) ([Queue mode](../scaling/queue-mode/) *is* included)\n- [Projects](../../user-management/rbac/projects/)\n- SSO ([SAML](../securing/set-up-sso/), [LDAP](../../user-management/ldap/))\n- Sharing ([workflows](../../workflows/sharing/), [credentials](../../credentials/credential-sharing/)) (Only the instance owner and the user who creates them can access workflows and credentials)\n- [Version control using Git](../../source-control-environments/)\n\nThese features are ava"
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "commands",
-          "running",
-          "start",
-          "workflow",
-          "change",
-          "active",
-          "status",
-          "export",
-          "entities",
-          "workflows",
-          "credentials",
-          "import",
-          "license",
-          "clear",
-          "info",
-          "user",
-          "management",
-          "disable",
-          "ldap",
-          "uninstall",
           "community",
-          "nodes",
-          "security",
-          "audit"
+          "enterprise",
+          "edition",
+          "features",
+          "registered"
         ],
         "useCases": [],
         "operations": [],
-        "codeExamples": 30,
+        "codeExamples": 23,
         "complexity": "beginner",
         "readingTime": "7 min",
         "contentLength": 11346,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "cli commands # cli commands for n8n\n\nn8n includes a cli (command line interface), allowing you to perform actions using the cli rather than the n8n editor. these include starting workflows, and exporting and importing workflows and credentials.\n\n## running cli commands\n\nyou can use cli commands with self-hosted n8n. depending on how you choose to install n8n, there are differences in how to run the commands:\n\n- npm: the `n8n` command is directly available. the documentation uses this in the examples below.\n\n- docker: the `n8n` command is available within your docker container:\n\n  ```\n  docker exec -u node -it <n8n-container-name> <n8n-cli-command>\n  ```\n\n## start a workflow\n\nyou can start workflows directly using the cli.\n\nexecute a saved workflow by its id:\n\n```\nn8n execute --id <id>\n```\n\n## change the active status of a workflow\n\nyou can change the active status of a workflow using the cli.\n\nrestart required\n\nthese commands operate on your n8n database. if you execute them while n8n is running, the changes don't take effect until you restart n8n.\n\nset the active status of a workflow by its id to false:\n\n```\nn8n update:workflow --id=<id> --active=false\n```\n\nset the active status of a workflow by its id to true:\n\n```\nn8n update:workflow --id=<id> --active=true\n```\n\nset the active status to false for all the workflows:\n\n```\nn8n update:workflow --all --active=false\n```\n\nset the active status to true for all the workflows:\n\n```\nn8n update:workflow --all --active=true\n```\n\n## export entities\n\nyou can export your database entities from n8n using the cli. this tooling allows you to export all entity types from one database type, such as sqlite, and import them into another database type, such as postgres.\n\ncommand flags:\n\n| flag                                | description                                                                                    |\n| ----------------------------------- | ---------------------------------------------------------------------------------------------- |\n| --help                              | help prompt.                                                                                   |\n| --outputdir                         | output directory path                                                                          |\n| --includeexecutionhistorydatatables | include execution history data tables, these are excluded by default as they can be very large |\n\n```\nn8n export:entities --outputdir=./outputs --includeexecutionhistorydatatables=true\n```\n\n## export workflows and credentials\n\nyou can export your workflows and credentials from n8n using the cli.\n\ncommand flags:\n\n| flag        | description                                                                                 |\n| ----------- | ------------------------------------------------------------------------------------------- |\n| --help      | help prompt.                                                                                |\n| --all       | exports all workflows/credentials.                                                          |\n| --backup    | sets --all --pretty --separate for backups. you can optionally set --output.                |\n| --id        | the id of the workflow to export.                                                           |\n| --output    | outputs file name or directory if using separate files.                                     |\n| --pretty    | formats the output in an easier to read fashion.                                            |\n| --separate  | exports one file per workflow (useful for versioning). must set a directory using --output. |\n| --decrypted | exports the credentials in a plain text format.                                             |\n\n### workflows\n\nexport all your workflows to the standard output (terminal):\n\n```\nn8n export:workflow --all\n```\n\nexport a workflow by its id and specify the output file name:\n\n```\nn8n export:workflow --id=<id> --output=file.json\n```\n\nexport all workflows to a specific directory in a single file:\n\n```\nn8n export:workflow --all --output=backups/latest/file.json\n```\n\nexport all the workflows to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:workflow --backup --output=backups/latest/\n```\n\n### credentials\n\nexport all your credentials to the standard output (terminal):\n\n```\nn8n export:credentials --all\n```\n\nexport credentials by their id and specify the output file name:\n\n```\nn8n export:credentials --id=<id> --output=file.json\n```\n\nexport all credentials to a specific directory in a single file:\n\n```\nn8n export:credentials --all --output=backups/latest/file.json\n```\n\nexport all the credentials to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:credentials --backup --output=backups/latest/\n```\n\nexport all the credentials in plain text format. you can use this to migrate from one installation to another that has a different secret key in the configuration file.\n\nsensitive information\n\nall sensitive information is visible in the files.\n\n```\nn8n export:credentials --all --decrypted --output=backups/decrypted.json\n```\n\n## import entities\n\nyou can import entities from a previous `export:entities` command using this command, it allows importing of entities into a database type that differs from the exported database type. current supported database types include: sqlite, postgres.\n\nthe database is expected to be empty prior to import, this can be forced with the `--truncatetables` parameter.\n\ncommand flags:\n\n| flag             | description                                        |\n| ---------------- | -------------------------------------------------- |\n| --help           | help prompt.                                       |\n| --inputdir       | input directory that holds output files for import |\n| --truncatetables | truncate tables before import                      |\n\n```\nn8n import:entities --inputdir ./outputs --truncatetables true\n```\n\n## import workflows and credentials\n\nyou can import your workflows and credentials from n8n using the cli.\n\nupdate the ids\n\nwhen exporting workflows and credentials, n8n also exports their ids. if you have workflows and credentials with the same ids in your existing database, they will be overwritten. to avoid this, delete or change the ids before importing.\n\navailable flags:\n\n| flag        | description                                                                                |\n| ----------- | ------------------------------------------------------------------------------------------ |\n| --help      | help prompt.                                                                               |\n| --input     | input file name or directory if you use --separate.                                        |\n| --projectid | import the workflow or credential to the specified project. can't be used with `--userid`. |\n| --separate  | imports `*.json` files from directory provided by --input.                                 |\n| --userid    | import the workflow or credential to the specified user. can't be used with `--projectid`. |\n\nmigrating to sqlite\n\nn8n limits workflow and credential names to 128 characters, but sqlite doesn't enforce size limits.\n\nthis might result in errors like **data too long for column name** during the import process.\n\nin this case, you can edit the names from the n8n interface and export again, or edit the json file directly before importing.\n\n### workflows\n\nimport workflows from a specific file:\n\n```\nn8n import:workflow --input=file.json\n```\n\nimport all the workflow files as json from the specified directory:\n\n```\nn8n import:workflow --separate --input=backups/latest/\n```\n\n### credentials\n\nimport credentials from a specific file:\n\n```\nn8n import:credentials --input=file.json\n```\n\nimport all the credentials files as json from the specified directory:\n\n```\nn8n import:credentials --separate --input=backups/latest/\n```\n\n## license\n\n### clear\n\nclear your existing license from n8n's database and reset n8n to default features:\n\n```\nn8n license:clear\n```\n\nif your license includes [floating entitlements](../../glossary/#entitlement-n8n), running this command will also attempt to release them back to the pool, making them available for other instances.\n\n### info\n\ndisplay information about the existing license:\n\n```\nn8n license:info\n```\n\n## user management\n\nyou can reset user management using the n8n cli. this returns user management to its pre-setup state. it removes all user accounts.\n\nuse this if you forget your password, and don't have smtp set up to do password resets by email.\n\n```\nn8n user-management:reset\n```\n\n### disable mfa for a user\n\nif a user loses their recovery codes you can disable mfa for a user with this command. the user will then be able to log back in to set up mfa again.\n\n```\nn8n mfa:disable --email=johndoe@example.com\n```\n\n### disable ldap\n\nyou can reset the ldap settings using the command below.\n\n```\nn8n ldap:reset\n```\n\n## uninstall community nodes and credentials\n\nyou can manage [community nodes](../../integrations/community-nodes/installation/) using the n8n cli. for now, you can only uninstall community nodes and credentials, which is useful if a community node causes instability.\n\ncommand flags:\n\n| flag         | description                                                                                                                |\n| ------------ | -------------------------------------------------------------------------------------------------------------------------- |\n| --help       | show cli help.                                                                                                             |\n| --credential | the credential type. get this value by visiting the node's `<node>.credential.ts` file and getting the value of `name`.    |\n| --package    | package name of the community node.                                                                                        |\n| --uninstall ",
+        "fullText": "community vs enterprise # community edition features\n\nthe community edition includes almost the complete feature set of n8n, except for the features listed here.\n\nthe community edition doesn't include these features:\n\n- [custom variables](../../code/variables/)\n- [environments](../../source-control-environments/)\n- [external secrets](../../external-secrets/)\n- [external storage for binary data](../scaling/external-storage/)\n- [log streaming](../../log-streaming/) ([logging](../logging-monitoring/logging/) *is* included)\n- [multi-main mode](../scaling/queue-mode/#multi-main-setup) ([queue mode](../scaling/queue-mode/) *is* included)\n- [projects](../../user-management/rbac/projects/)\n- sso ([saml](../securing/set-up-sso/), [ldap](../../user-management/ldap/))\n- sharing ([workflows](../../workflows/sharing/), [credentials](../../credentials/credential-sharing/)) (only the instance owner and the user who creates them can access workflows and credentials)\n- [version control using git](../../source-control-environments/)\n\nthese features are available on the enterprise cloud plan, including the self-hosted enterprise edition. some of these features are available on the starter and pro cloud plan.\n\nsee [pricing](https://n8n.io/pricing/) for reference.\n\n## registered community edition\n\nyou can unlock extra features by registering your n8n community edition. you register with your email and receive a license key.\n\nregistering unlocks these features for the community edition:\n\n- folders: organize your workflows into tidy folders\n- [debug in editor](../../workflows/executions/debug/): copy and [pin](../../glossary/#data-pinning-n8n) execution data when working on a workflow\n- [custom execution data](../../workflows/executions/custom-executions-data/): save, find, and annotate execution metadata\n\nto register a new community edition instance, select the option during your initial account creation.\n\nto register an existing community edition instance:\n\n1. select the **three dots icon** in the lower-left corner.\n1. select **settings** and then **usage and plan**.\n1. select **unlock** to enter your email and then select **send me a free license key**.\n1. check your email for the account you entered.\n\nonce you have a license key, activate it by clicking the button in the license email or by visiting **options > settings > usage and plan** and selecting **enter activation key**.\n\nonce activated, your license will not expire. we may change the unlocked features in the future. this will not impact previously unlocked features.\nows and credentials\n\nyou can export your workflows and credentials from n8n using the cli.\n\ncommand flags:\n\n| flag        | description                                                                                 |\n| ----------- | ------------------------------------------------------------------------------------------- |\n| --help      | help prompt.                                                                                |\n| --all       | exports all workflows/credentials.                                                          |\n| --backup    | sets --all --pretty --separate for backups. you can optionally set --output.                |\n| --id        | the id of the workflow to export.                                                           |\n| --output    | outputs file name or directory if using separate files.                                     |\n| --pretty    | formats the output in an easier to read fashion.                                            |\n| --separate  | exports one file per workflow (useful for versioning). must set a directory using --output. |\n| --decrypted | exports the credentials in a plain text format.                                             |\n\n### workflows\n\nexport all your workflows to the standard output (terminal):\n\n```\nn8n export:workflow --all\n```\n\nexport a workflow by its id and specify the output file name:\n\n```\nn8n export:workflow --id=<id> --output=file.json\n```\n\nexport all workflows to a specific directory in a single file:\n\n```\nn8n export:workflow --all --output=backups/latest/file.json\n```\n\nexport all the workflows to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:workflow --backup --output=backups/latest/\n```\n\n### credentials\n\nexport all your credentials to the standard output (terminal):\n\n```\nn8n export:credentials --all\n```\n\nexport credentials by their id and specify the output file name:\n\n```\nn8n export:credentials --id=<id> --output=file.json\n```\n\nexport all credentials to a specific directory in a single file:\n\n```\nn8n export:credentials --all --output=backups/latest/file.json\n```\n\nexport all the credentials to a specific directory using the `--backup` flag (details above):\n\n```\nn8n export:credentials --backup --output=backups/latest/\n```\n\nexport all the credentials in plain text format. you can use this to migrate from one installation to another that has a different secret key in the configuration file.\n\nsensitive information\n\nall sensitive information is visible in the files.\n\n```\nn8n export:credentials --all --decrypted --output=backups/decrypted.json\n```\n\n## import entities\n\nyou can import entities from a previous `export:entities` command using this command, it allows importing of entities into a database type that differs from the exported database type. current supported database types include: sqlite, postgres.\n\nthe database is expected to be empty prior to import, this can be forced with the `--truncatetables` parameter.\n\ncommand flags:\n\n| flag             | description                                        |\n| ---------------- | -------------------------------------------------- |\n| --help           | help prompt.                                       |\n| --inputdir       | input directory that holds output files for import |\n| --truncatetables | truncate tables before import                      |\n\n```\nn8n import:entities --inputdir ./outputs --truncatetables true\n```\n\n## import workflows and credentials\n\nyou can import your workflows and credentials from n8n using the cli.\n\nupdate the ids\n\nwhen exporting workflows and credentials, n8n also exports their ids. if you have workflows and credentials with the same ids in your existing database, they will be overwritten. to avoid this, delete or change the ids before importing.\n\navailable flags:\n\n| flag        | description                                                                                |\n| ----------- | ------------------------------------------------------------------------------------------ |\n| --help      | help prompt.                                                                               |\n| --input     | input file name or directory if you use --separate.                                        |\n| --projectid | import the workflow or credential to the specified project. can't be used with `--userid`. |\n| --separate  | imports `*.json` files from directory provided by --input.                                 |\n| --userid    | import the workflow or credential to the specified user. can't be used with `--projectid`. |\n\nmigrating to sqlite\n\nn8n limits workflow and credential names to 128 characters, but sqlite doesn't enforce size limits.\n\nthis might result in errors like **data too long for column name** during the import process.\n\nin this case, you can edit the names from the n8n interface and export again, or edit the json file directly before importing.\n\n### workflows\n\nimport workflows from a specific file:\n\n```\nn8n import:workflow --input=file.json\n```\n\nimport all the workflow files as json from the specified directory:\n\n```\nn8n import:workflow --separate --input=backups/latest/\n```\n\n### credentials\n\nimport credentials from a specific file:\n\n```\nn8n import:credentials --input=file.json\n```\n\nimport all the credentials files as json from the specified directory:\n\n```\nn8n import:credentials --separate --input=backups/latest/\n```\n\n## license\n\n### clear\n\nclear your existing license from n8n's database and reset n8n to default features:\n\n```\nn8n license:clear\n```\n\nif your license includes [floating entitlements](../../glossary/#entitlement-n8n), running this command will also attempt to release them back to the pool, making them available for other instances.\n\n### info\n\ndisplay information about the existing license:\n\n```\nn8n license:info\n```\n\n## user management\n\nyou can reset user management using the n8n cli. this returns user management to its pre-setup state. it removes all user accounts.\n\nuse this if you forget your password, and don't have smtp set up to do password resets by email.\n\n```\nn8n user-management:reset\n```\n\n### disable mfa for a user\n\nif a user loses their recovery codes you can disable mfa for a user with this command. the user will then be able to log back in to set up mfa again.\n\n```\nn8n mfa:disable --email=johndoe@example.com\n```\n\n### disable ldap\n\nyou can reset the ldap settings using the command below.\n\n```\nn8n ldap:reset\n```\n\n## uninstall community nodes and credentials\n\nyou can manage [community nodes](../../integrations/community-nodes/installation/) using the n8n cli. for now, you can only uninstall community nodes and credentials, which is useful if a community node causes instability.\n\ncommand flags:\n\n| flag         | description                                                                                                                |\n| ------------ | -------------------------------------------------------------------------------------------------------------------------- |\n| --help       | show cli help.                                                                                                             |\n| --credential | the credential type. get this value by visiting the node's `<node>.credential.ts` file and getting the value of `name`.    |\n| --package    | package name of the community node.                                                                                        |\n| -",
         "importantTerms": [
           "credentials",
+          "community",
           "export",
-          "workflow",
-          "import",
           "file",
+          "import",
           "workflows",
+          "your",
           "output",
-          "using",
+          "user",
+          "workflow",
           "node",
-          "from",
-          "community",
-          "command",
+          "credential",
           "this",
-          "your",
+          "from",
+          "features",
+          "using",
+          "license",
           "directory",
-          "database",
           "json",
-          "credential",
-          "user",
           "uninstall",
+          "edition",
+          "nodes",
           "name",
-          "active",
+          "command",
           "help",
-          "nodes",
-          "entities",
           "backups",
           "input",
-          "commands",
           "with",
-          "flag",
           "separate",
+          "database",
           "package",
           "evolution",
-          "status",
-          "true",
-          "type",
+          "data",
+          "management",
+          "email",
+          "flag",
           "files",
           "specific",
           "latest",
-          "license",
-          "update",
-          "flags",
-          "description",
+          "ldap",
+          "https",
+          "select",
+          "will",
           "backup",
+          "entities",
           "userid",
           "reset",
-          "importing",
-          "available",
-          "them",
-          "false"
-        ]
-      }
-    },
-    {
-      "id": "page-0151",
-      "title": "Community vs Enterprise",
-      "url": "https://docs.n8n.io/hosting/community-edition-features/index.md",
-      "urlPath": "hosting/community-edition-features/index.md",
-      "category": "hosting",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Community Edition Features\n\nThe community edition includes almost the complete feature set of n8n, except for the features listed here.\n\nThe community edition doesn't include these features:\n\n- [Custom Variables](../../code/variables/)\n- [Environments](../../source-control-environments/)\n- [External secrets](../../external-secrets/)\n- [External storage for binary data](../scaling/external-storage/)\n- [Log streaming](../../log-streaming/) ([Logging](../logging-monitoring/logging/) *is* included)\n- [Multi-main mode](../scaling/queue-mode/#multi-main-setup) ([Queue mode](../scaling/queue-mode/) *is* included)\n- [Projects](../../user-management/rbac/projects/)\n- SSO ([SAML](../securing/set-up-sso/), [LDAP](../../user-management/ldap/))\n- Sharing ([workflows](../../workflows/sharing/), [credentials](../../credentials/credential-sharing/)) (Only the instance owner and the user who creates them can access workflows and credentials)\n- [Version control using Git](../../source-control-environments/)\n\nThese features are available on the Enterprise Cloud plan, including the self-hosted Enterprise edition. Some of these features are available on the Starter and Pro Cloud plan.\n\nSee [pricing](https://n8n.io/pricing/) for reference.\n\n## Registered Community Edition\n\nYou can unlock extra features by registering your n8n community edition. You register with your email and receive a license key.\n\nRegistering unlocks these features for the community edition:\n\n- Folders: Organize your workflows into tidy folders\n- [Debug in editor](../../workflows/executions/debug/): Copy and [pin](../../glossary/#data-pinning-n8n) execution data when working on a workflow\n- [Custom execution data](../../workflows/executions/custom-executions-data/): Save, find, and annotate execution metadata\n\nTo register a new community edition instance, select the option during your initial account creation.\n\nTo register an existing community edition instance:\n\n1. Select the **three dots icon** in the lower-left corner.\n1. Select **Settings** and then **Usage and plan**.\n1. Select **Unlock** to enter your email and then select **Send me a free license key**.\n1. Check your email for the account you entered.\n\nOnce you have a license key, activate it by clicking the button in the license email or by visiting **Options > Settings > Usage and plan** and selecting **Enter activation key**.\n\nOnce activated, your license will not expire. We may change the unlocked features in the future. This will not impact previously unlocked features.\n",
-        "excerpt": "# Community Edition Features  The community edition includes almost the complete feature set of n8n, except for the features listed here.  The community edition doesn't include these features:  - [Custom Variables](../../code/variables/) - [Environments](../../source-control-environments/) - [External secrets](../../external-secrets/) - [External storage for binary data](../scaling/external-storage/) - [Log streaming](../../log-streaming/) ([Logging](../logging-monitoring/logging/) *is* included...",
-        "sections": [
-          {
-            "title": "Community Edition Features",
-            "level": 1,
-            "content": "The community edition includes almost the complete feature set of n8n, except for the features listed here.\n\nThe community edition doesn't include these features:\n\n- [Custom Variables](../../code/variables/)\n- [Environments](../../source-control-environments/)\n- [External secrets](../../external-secrets/)\n- [External storage for binary data](../scaling/external-storage/)\n- [Log streaming](../../log-streaming/) ([Logging](../logging-monitoring/logging/) *is* included)\n- [Multi-main mode](../scaling/queue-mode/#multi-main-setup) ([Queue mode](../scaling/queue-mode/) *is* included)\n- [Projects](../../user-management/rbac/projects/)\n- SSO ([SAML](../securing/set-up-sso/), [LDAP](../../user-management/ldap/))\n- Sharing ([workflows](../../workflows/sharing/), [credentials](../../credentials/credential-sharing/)) (Only the instance owner and the user who creates them can access workflows and credentials)\n- [Version control using Git](../../source-control-environments/)\n\nThese features are ava"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "community",
-          "enterprise",
-          "edition",
-          "features",
-          "registered"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 2527,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "community vs enterprise # community edition features\n\nthe community edition includes almost the complete feature set of n8n, except for the features listed here.\n\nthe community edition doesn't include these features:\n\n- [custom variables](../../code/variables/)\n- [environments](../../source-control-environments/)\n- [external secrets](../../external-secrets/)\n- [external storage for binary data](../scaling/external-storage/)\n- [log streaming](../../log-streaming/) ([logging](../logging-monitoring/logging/) *is* included)\n- [multi-main mode](../scaling/queue-mode/#multi-main-setup) ([queue mode](../scaling/queue-mode/) *is* included)\n- [projects](../../user-management/rbac/projects/)\n- sso ([saml](../securing/set-up-sso/), [ldap](../../user-management/ldap/))\n- sharing ([workflows](../../workflows/sharing/), [credentials](../../credentials/credential-sharing/)) (only the instance owner and the user who creates them can access workflows and credentials)\n- [version control using git](../../source-control-environments/)\n\nthese features are available on the enterprise cloud plan, including the self-hosted enterprise edition. some of these features are available on the starter and pro cloud plan.\n\nsee [pricing](https://n8n.io/pricing/) for reference.\n\n## registered community edition\n\nyou can unlock extra features by registering your n8n community edition. you register with your email and receive a license key.\n\nregistering unlocks these features for the community edition:\n\n- folders: organize your workflows into tidy folders\n- [debug in editor](../../workflows/executions/debug/): copy and [pin](../../glossary/#data-pinning-n8n) execution data when working on a workflow\n- [custom execution data](../../workflows/executions/custom-executions-data/): save, find, and annotate execution metadata\n\nto register a new community edition instance, select the option during your initial account creation.\n\nto register an existing community edition instance:\n\n1. select the **three dots icon** in the lower-left corner.\n1. select **settings** and then **usage and plan**.\n1. select **unlock** to enter your email and then select **send me a free license key**.\n1. check your email for the account you entered.\n\nonce you have a license key, activate it by clicking the button in the license email or by visiting **options > settings > usage and plan** and selecting **enter activation key**.\n\nonce activated, your license will not expire. we may change the unlocked features in the future. this will not impact previously unlocked features.\n community edition features",
-        "importantTerms": [
-          "community",
-          "edition",
-          "features",
-          "your",
-          "workflows",
-          "data",
-          "license",
-          "select",
           "these",
           "external",
-          "mode",
-          "plan",
-          "email",
-          "enterprise",
-          "custom",
-          "environments",
-          "control",
-          "scaling",
-          "logging",
-          "queue",
-          "user",
-          "sharing",
-          "credentials",
-          "instance",
-          "register",
-          "executions",
-          "execution"
+          "mode"
         ]
       }
     },
@@ -50310,7 +50221,7 @@
       "nodeName": "git",
       "nodeType": "n8n-nodes-base.git",
       "content": {
-        "markdown": "# Git\n\n[Git](https://git-scm.com/) is a free and open-source distributed version control system designed to handle everything from small to large projects with speed and efficiency.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/git/).\n\n## Operations\n\n- **Add** a file or folder to commit. Performs a [git add](https://git-scm.com/docs/git-add).\n- **Add Config**: Add configuration property. Performs a [git config](https://git-scm.com/docs/git-config) set or add.\n- **Clone** a repository: Performs a [git clone](https://git-scm.com/docs/git-clone).\n- **Commit** files or folders to git. Performs a [git commit](https://git-scm.com/docs/git-commit).\n- **Fetch** from remote repository. Performs a [git fetch](https://git-scm.com/docs/git-fetch).\n- **List Config**: Return current configuration. Performs a [git config](https://git-scm.com/docs/git-config) query.\n- **Log**: Return git commit history. Performs a [git log](https://git-scm.com/docs/git-log).\n- **Pull** from remote repository: Performs a [git pull](https://git-scm.com/docs/git-pull).\n- **Push** to remote repository: Performs a [git push](https://git-scm.com/docs/git-push).\n- **Push Tags** to remote repository: Performs a [git push --tags](https://git-scm.com/docs/git-push#Documentation/git-push.txt---tags).\n- Return **Status** of current repository: Performs a [git status](https://git-scm.com/docs/git-status).\n- Create a new **Tag**: Performs a [git tag](https://git-scm.com/docs/git-tag).\n- **User Setup**: Set the user.\n\nRefer to the sections below for more details on the parameters and options for each operation.\n\n## Add\n\nConfigure this operation with these parameters:\n\n- **Repository Path**: Enter the local path of the git repository.\n- **Paths to Add**: Enter a comma-separated list of paths of files or folders to add in this field. You can use absolute paths or relative paths from the **Repository Path**.\n\n## Add Config\n\nConfigure this operation with these parameters:\n\n- **Repository Path**: Enter the local path of the git repository.\n- **Key**: Enter the name of the key to set.\n- **Value**: Enter the value of the key to set.\n\n### Add Config options\n\nThe add config operation adds the **Mode** option. Choose whether to **Set** or **Append** the setting in the local config.\n",
+        "markdown": "# Git\n\n[Git](https://git-scm.com/) is a free and open-source distributed version control system designed to handle everything from small to large projects with speed and efficiency.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/git/).\n\n## Operations\n\n- **Add** a file or folder to commit. Performs a [git add](https://git-scm.com/docs/git-add).\n- **Add Config**: Add configuration property. Performs a [git config](https://git-scm.com/docs/git-config) set or add.\n- **Clone** a repository: Performs a [git clone](https://git-scm.com/docs/git-clone).\n- **Commit** files or folders to git. Performs a [git commit](https://git-scm.com/docs/git-commit).\n- **Fetch** from remote repository. Performs a [git fetch](https://git-scm.com/docs/git-fetch).\n- **List Config**: Return current configuration. Performs a [git config](https://git-scm.com/docs/git-config) query.\n- **Log**: Return git commit history. Performs a [git log](https://git-scm.com/docs/git-log).\n- **Pull** from remote repository: Performs a [git pull](https://git-scm.com/docs/git-pull).\n- **Push** to remote repository: Performs a [git push](https://git-scm.com/docs/git-push).\n- **Push Tags** to remote repository: Performs a [git push --tags](https://git-scm.com/docs/git-push#Documentation/git-push.txt---tags).\n- Return **Status** of current repository: Performs a [git status](https://git-scm.com/docs/git-status).\n- **Switch Branch:** Performs a [git switch](https://git-scm.com/docs/git-switch).\n- Create a new **Tag**: Performs a [git tag](https://git-scm.com/docs/git-tag).\n- **User Setup**: Set the user.\n\nRefer to the sections below for more details on the parameters and options for each operation.\n\n## Add\n\nConfigure this operation with these parameters:\n\n- **Repository Path**: Enter the local path of the git repository.\n- **Paths to Add**: Enter a comma-separated list of paths of files or folders to add in this field. You can use absolute paths or relative paths from the **Repository Path**.\n\n## Add Config\n\nConfigure this operation with these parameters:\n\n- **Repository Path**: Enter the local path of the git repository.\n- **Key**: Enter the name of the key to set.\n- **Value**: Enter the value of the key to set.\n\n### Add Config options\n\nThe add config operation adds the **Mode** option. Choose whether to **Set** or **Append** the setting in the local config.\n",
         "excerpt": "# Git  [Git](https://git-scm.com/) is a free and open-source distributed version control system designed to handle everything from small to large projects with speed and efficiency.  Credentials  You can find authentication information for this node [here](../../credentials/git/).  ## Operations  - **Add** a file or folder to commit. Performs a [git add](https://git-scm.com/docs/git-add). - **Add Config**: Add configuration property. Performs a [git config](https://git-scm.com/docs/git-config) s...",
         "sections": [
           {
@@ -50333,11 +50244,11 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "2 min",
-        "contentLength": 2312,
+        "contentLength": 2395,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "git # git\n\n[git](https://git-scm.com/) is a free and open-source distributed version control system designed to handle everything from small to large projects with speed and efficiency.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/git/).\n\n## operations\n\n- **add** a file or folder to commit. performs a [git add](https://git-scm.com/docs/git-add).\n- **add config**: add configuration property. performs a [git config](https://git-scm.com/docs/git-config) set or add.\n- **clone** a repository: performs a [git clone](https://git-scm.com/docs/git-clone).\n- **commit** files or folders to git. performs a [git commit](https://git-scm.com/docs/git-commit).\n- **fetch** from remote repository. performs a [git fetch](https://git-scm.com/docs/git-fetch).\n- **list config**: return current configuration. performs a [git config](https://git-scm.com/docs/git-config) query.\n- **log**: return git commit history. performs a [git log](https://git-scm.com/docs/git-log).\n- **pull** from remote repository: performs a [git pull](https://git-scm.com/docs/git-pull).\n- **push** to remote repository: performs a [git push](https://git-scm.com/docs/git-push).\n- **push tags** to remote repository: performs a [git push --tags](https://git-scm.com/docs/git-push#documentation/git-push.txt---tags).\n- return **status** of current repository: performs a [git status](https://git-scm.com/docs/git-status).\n- create a new **tag**: performs a [git tag](https://git-scm.com/docs/git-tag).\n- **user setup**: set the user.\n\nrefer to the sections below for more details on the parameters and options for each operation.\n\n## add\n\nconfigure this operation with these parameters:\n\n- **repository path**: enter the local path of the git repository.\n- **paths to add**: enter a comma-separated list of paths of files or folders to add in this field. you can use absolute paths or relative paths from the **repository path**.\n\n## add config\n\nconfigure this operation with these parameters:\n\n- **repository path**: enter the local path of the git repository.\n- **key**: enter the name of the key to set.\n- **value**: enter the value of the key to set.\n\n### add config options\n\nthe add config operation adds the **mode** option. choose whether to **set** or **append** the setting in the local config.\n git",
+        "fullText": "git # git\n\n[git](https://git-scm.com/) is a free and open-source distributed version control system designed to handle everything from small to large projects with speed and efficiency.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/git/).\n\n## operations\n\n- **add** a file or folder to commit. performs a [git add](https://git-scm.com/docs/git-add).\n- **add config**: add configuration property. performs a [git config](https://git-scm.com/docs/git-config) set or add.\n- **clone** a repository: performs a [git clone](https://git-scm.com/docs/git-clone).\n- **commit** files or folders to git. performs a [git commit](https://git-scm.com/docs/git-commit).\n- **fetch** from remote repository. performs a [git fetch](https://git-scm.com/docs/git-fetch).\n- **list config**: return current configuration. performs a [git config](https://git-scm.com/docs/git-config) query.\n- **log**: return git commit history. performs a [git log](https://git-scm.com/docs/git-log).\n- **pull** from remote repository: performs a [git pull](https://git-scm.com/docs/git-pull).\n- **push** to remote repository: performs a [git push](https://git-scm.com/docs/git-push).\n- **push tags** to remote repository: performs a [git push --tags](https://git-scm.com/docs/git-push#documentation/git-push.txt---tags).\n- return **status** of current repository: performs a [git status](https://git-scm.com/docs/git-status).\n- **switch branch:** performs a [git switch](https://git-scm.com/docs/git-switch).\n- create a new **tag**: performs a [git tag](https://git-scm.com/docs/git-tag).\n- **user setup**: set the user.\n\nrefer to the sections below for more details on the parameters and options for each operation.\n\n## add\n\nconfigure this operation with these parameters:\n\n- **repository path**: enter the local path of the git repository.\n- **paths to add**: enter a comma-separated list of paths of files or folders to add in this field. you can use absolute paths or relative paths from the **repository path**.\n\n## add config\n\nconfigure this operation with these parameters:\n\n- **repository path**: enter the local path of the git repository.\n- **key**: enter the name of the key to set.\n- **value**: enter the value of the key to set.\n\n### add config options\n\nthe add config operation adds the **mode** option. choose whether to **set** or **append** the setting in the local config.\n git",
         "importantTerms": [
           "https",
           "performs",
@@ -50360,6 +50271,7 @@
           "pull",
           "tags",
           "status",
+          "switch",
           "parameters",
           "local"
         ]
@@ -89544,7 +89456,6 @@
       "start": [
         "page-0001",
         "page-0003",
-        "page-0150",
         "page-0166",
         "page-0193",
         "page-0199",
@@ -89579,7 +89490,7 @@
         "page-0030",
         "page-0038",
         "page-0050",
-        "page-0151",
+        "page-0150",
         "page-0542",
         "page-0690",
         "page-1187",
@@ -90410,7 +90321,6 @@
         "page-0002",
         "page-0003",
         "page-0013",
-        "page-0150",
         "page-1123",
         "page-1144",
         "page-1173",
@@ -90465,7 +90375,6 @@
         "page-0140",
         "page-0145",
         "page-0147",
-        "page-0150",
         "page-0152",
         "page-0163",
         "page-0191",
@@ -90634,7 +90543,6 @@
         "page-0142",
         "page-0143",
         "page-0144",
-        "page-0150",
         "page-0152",
         "page-0161",
         "page-0184",
@@ -91153,7 +91061,6 @@
         "page-0141",
         "page-0144",
         "page-0145",
-        "page-0150",
         "page-0152",
         "page-0192",
         "page-0645",
@@ -91188,7 +91095,6 @@
       ],
       "security": [
         "page-0003",
-        "page-0150",
         "page-0186",
         "page-0220",
         "page-0293",
@@ -91484,7 +91390,6 @@
         "page-0003",
         "page-0007",
         "page-0138",
-        "page-0150",
         "page-0214",
         "page-0216",
         "page-0223",
@@ -92405,7 +92310,6 @@
         "page-0005",
         "page-0021",
         "page-0135",
-        "page-0150",
         "page-0152",
         "page-0173",
         "page-0220",
@@ -93923,7 +93827,6 @@
         "page-0147",
         "page-0148",
         "page-0150",
-        "page-0151",
         "page-0225",
         "page-0227",
         "page-0841",
@@ -94061,7 +93964,6 @@
       "license": [
         "page-0010",
         "page-0014",
-        "page-0150",
         "page-0182",
         "page-1187"
       ],
@@ -94216,7 +94118,6 @@
       ],
       "status": [
         "page-0012",
-        "page-0150",
         "page-1226"
       ],
       "viewing": [
@@ -97507,7 +97408,6 @@
       ],
       "commands": [
         "page-0018",
-        "page-0150",
         "page-0694"
       ],
       "credits": [
@@ -97591,7 +97491,6 @@
         "page-0019",
         "page-0134",
         "page-0135",
-        "page-0150",
         "page-0152",
         "page-0157",
         "page-0168",
@@ -101586,7 +101485,6 @@
       ],
       "management": [
         "page-0135",
-        "page-0150",
         "page-0157",
         "page-0190",
         "page-0443",
@@ -101842,79 +101740,16 @@
         "page-0148",
         "page-1171"
       ],
-      "running": [
-        "page-0150",
-        "page-0214",
-        "page-0509",
-        "page-0516",
-        "page-0613",
-        "page-0621",
-        "page-0625",
-        "page-0650",
-        "page-0675",
-        "page-0689"
-      ],
-      "active": [
-        "page-0150",
-        "page-0166",
-        "page-1188"
-      ],
-      "export": [
-        "page-0150",
-        "page-1187",
-        "page-1224"
-      ],
-      "entities": [
-        "page-0150"
-      ],
-      "import": [
-        "page-0150",
-        "page-0696",
-        "page-1187",
-        "page-1224"
-      ],
-      "clear": [
-        "page-0150",
-        "page-0507",
-        "page-0544",
-        "page-0547",
-        "page-0551",
-        "page-0698"
-      ],
-      "info": [
-        "page-0150",
-        "page-1015",
-        "page-1019"
-      ],
-      "ldap": [
-        "page-0150",
-        "page-0658",
-        "page-0836",
-        "page-1187",
-        "page-1207"
-      ],
-      "uninstall": [
-        "page-0150",
-        "page-1134",
-        "page-1135",
-        "page-1136"
-      ],
-      "audit": [
-        "page-0150",
-        "page-0220",
-        "page-0664",
-        "page-1187"
-      ],
       "enterprise": [
-        "page-0151",
+        "page-0150",
         "page-1176",
         "page-1188"
       ],
       "edition": [
-        "page-0151"
+        "page-0150"
       ],
       "registered": [
-        "page-0151"
+        "page-0150"
       ],
       "technology": [
         "page-0152"
@@ -102293,6 +102128,10 @@
       "jobs": [
         "page-0166"
       ],
+      "active": [
+        "page-0166",
+        "page-1188"
+      ],
       "being": [
         "page-0166"
       ],
@@ -103102,6 +102941,17 @@
         "page-1084",
         "page-1187"
       ],
+      "running": [
+        "page-0214",
+        "page-0509",
+        "page-0516",
+        "page-0613",
+        "page-0621",
+        "page-0625",
+        "page-0650",
+        "page-0675",
+        "page-0689"
+      ],
       "queues": [
         "page-0214"
       ],
@@ -103176,6 +103026,11 @@
         "page-1136",
         "page-1188"
       ],
+      "audit": [
+        "page-0220",
+        "page-0664",
+        "page-1187"
+      ],
       "report": [
         "page-0220",
         "page-1130"
@@ -105250,6 +105105,13 @@
       "spreadsheet": [
         "page-0506"
       ],
+      "clear": [
+        "page-0507",
+        "page-0544",
+        "page-0547",
+        "page-0551",
+        "page-0698"
+      ],
       "rows": [
         "page-0507",
         "page-0509",
@@ -106369,6 +106231,12 @@
       "decode": [
         "page-0657"
       ],
+      "ldap": [
+        "page-0658",
+        "page-0836",
+        "page-1187",
+        "page-1207"
+      ],
       "involving": [
         "page-0660"
       ],
@@ -106629,6 +106497,11 @@
       "optimize": [
         "page-0696"
       ],
+      "import": [
+        "page-0696",
+        "page-1187",
+        "page-1224"
+      ],
       "requesting": [
         "page-0697"
       ],
@@ -107166,6 +107039,10 @@
         "page-1154",
         "page-1163"
       ],
+      "info": [
+        "page-1015",
+        "page-1019"
+      ],
       "poll": [
         "page-1025",
         "page-1121"
@@ -107256,6 +107133,11 @@
         "page-1132",
         "page-1214"
       ],
+      "uninstall": [
+        "page-1134",
+        "page-1135",
+        "page-1136"
+      ],
       "downgrade": [
         "page-1134",
         "page-1135"
@@ -107802,6 +107684,10 @@
         "page-1187",
         "page-1188"
       ],
+      "export": [
+        "page-1187",
+        "page-1224"
+      ],
       "sticky": [
         "page-1187",
         "page-1188",
@@ -108905,7 +108791,6 @@
       "hosting": [
         "page-0149",
         "page-0150",
-        "page-0151",
         "page-0152",
         "page-0153",
         "page-0154",