@n8n-as-code/skills 1.6.1-next.1 → 1.6.1-next.2

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

@@ -1,8 +1,8 @@
 {
-  "generatedAt": "2026-04-03T13:29:18.782Z",
+  "generatedAt": "2026-04-03T13:36:27.568Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1262,
+  "totalPages": 1261,
   "statistics": {
     "byCategory": {
       "other": 517,
@@ -12,7 +12,7 @@
       "code": 20,
       "data": 38,
       "flow-logic": 8,
-      "hosting": 80,
+      "hosting": 79,
       "integrations": 306,
       "cluster-nodes": 101,
       "trigger-nodes": 107,
@@ -21,7 +21,7 @@
     },
     "withNodeNames": 471,
     "withUseCases": 39,
-    "withCodeExamples": 180
+    "withCodeExamples": 179
   },
   "categories": {
     "other": {
@@ -710,7 +710,7 @@
     },
     "hosting": {
       "description": "Self-hosting, deployment, and infrastructure",
-      "totalPages": 80,
+      "totalPages": 79,
       "pages": [
         "page-0150",
         "page-0151",
@@ -764,7 +764,6 @@
         "page-0199",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0203",
         "page-0204",
         "page-0205",
@@ -16823,123 +16822,6 @@
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
-      "content": {
-        "markdown": "# Hosting n8n on Azure\n\nThis hosting guide shows you how to self-host n8n on Azure. It uses n8n with Postgres as a database backend using Kubernetes to manage the necessary resources and reverse proxy.\n\n## Prerequisites\n\nYou need [The Azure command line tool](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli)\n\nSelf-hosting knowledge prerequisites\n\nSelf-hosting n8n requires technical knowledge, including:\n\n- Setting up and configuring servers and containers\n- Managing application resources and scaling\n- Securing servers and applications\n- Configuring n8n\n\nn8n recommends self-hosting for expert users. Mistakes can lead to data loss, security issues, and downtime. If you aren't experienced at managing servers, n8n recommends [n8n Cloud](https://n8n.io/cloud/).\n\nStable and Beta versions\n\nn8n releases a new minor version most weeks. The `stable` version is for production use. `beta` is the most recent release. The `beta` version may be unstable. To report issues, use the [forum](https://community.n8n.io/c/questions/12).\n\nCurrent `stable`: 2.14.2 Current `beta`: 2.15.0\n\n## Hosting options\n\nAzure offers several ways suitable for hosting n8n, including Azure Container Instances (optimized for running containers), Linux Virtual Machines, and Azure Kubernetes Service (containers running with Kubernetes).\n\nThis guide uses the Azure Kubernetes Service (AKS) as the hosting option. Using Kubernetes requires some additional complexity and configuration, but is the best method for scaling n8n as demand changes.\n\nThe steps in this guide use a mix of the Azure UI and command line tool, but you can use either to accomplish most tasks.\n\n## Open the Azure Kubernetes Service\n\nFrom [the Azure portal](https://portal.azure.com/) select **Kubernetes services**.\n\n## Create a cluster\n\nFrom the Kubernetes services page, select **Create** > **Create a Kubernetes cluster**.\n\nYou can select any of the configuration options that suit your needs, then select **Create** when done.\n\n## Set Kubectl context\n\nThe remainder of the steps in this guide require you to set the Azure instance as the Kubectl context. You can find the connection details for a cluster instance by opening its details page and then the **Connect** button. The resulting code snippets shows the steps to paste and run into a terminal to change your local Kubernetes settings to use the new cluster.\n\n## Clone configuration repository\n\nKubernetes and n8n require a series of configuration files. You can clone these from [this repository](https://github.com/n8n-io/n8n-hosting). The following steps tell you which file configures what and what you need to change.\n\nClone the repository with the following command:\n\n```\ngit clone https://github.com/n8n-io/n8n-hosting.git\n```\n\nAnd change directory:\n\n```\ncd n8n-hosting/kubernetes\n```\n\n## Configure Postgres\n\nFor larger scale n8n deployments, Postgres provides a more robust database backend than SQLite.\n\n### Configure volume for persistent storage\n\nTo maintain data between pod restarts, the Postgres deployment needs a persistent volume. The default storage class is suitable for this purpose and is defined in the `postgres-claim0-persistentvolumeclaim.yaml` manifest.\n\nSpecialized storage classes\n\nIf you have specialised or higher requirements for storage classes, [read more on the options Azure offers in the documentation](https://learn.microsoft.com/en-us/azure/aks/concepts-storage#storage-classes).\n\n### Postgres environment variables\n\nPostgres needs some environment variables set to pass to the application running in the containers.\n\nThe example `postgres-secret.yaml` file contains placeholders you need to replace with your own values. Postgres will use these details when creating the database..\n\nThe `postgres-deployment.yaml` manifest then uses the values from this manifest file to send to the application pods.\n\n## Configure n8n\n\n### Create a volume for file storage\n\nWhile not essential for running n8n, using persistent volumes is required for:\n\n- Using nodes that interact with files, such as the binary data node.\n- If you want to persist [manual n8n encryption keys](../../../configuration/environment-variables/deployment/) between restarts. This saves a file containing the key into file storage during startup.\n\nThe `n8n-claim0-persistentvolumeclaim.yaml` manifest creates this, and the n8n Deployment mounts that claim in the `volumes` section of the `n8n-deployment.yaml` manifest.\n\n```\n…\nvolumes:\n  - name: n8n-claim0\n    persistentVolumeClaim:\n      claimName: n8n-claim0\n…\n```\n\n### Pod resources\n\n[Kubernetes lets you](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) optionally specify the minimum resources application containers need and the limits they can run to. The example YAML files cloned above contain the following in the `resources` section of the `n8n-deployment.yaml` file:\n\n```\n…\nresources:\n  requests:\n    memory: \"250Mi\"\n  limits:\n    memory: \"500Mi\"\n…\n```\n\nThis defines a minimum of 250mb per container, a maximum of 500mb, and lets Kubernetes handle CPU. You can change these values to match your own needs. As a guide, here are the resources values for the n8n cloud offerings:\n\n- **Start**: 320mb RAM, 10 millicore CPU burstable\n- **Pro (10k executions)**: 640mb RAM, 20 millicore CPU burstable\n- **Pro (50k executions)**: 1280mb RAM, 80 millicore CPU burstable\n\n### Optional: Environment variables\n\nYou can configure n8n settings and behaviors using environment variables.\n\nCreate an `n8n-secret.yaml` file. Refer to [Environment variables](../../../configuration/environment-variables/) for n8n environment variables details.\n\n## Deployments\n\nThe two deployment manifests (`n8n-deployment.yaml` and `postgres-deployment.yaml`) define the n8n and Postgres applications to Kubernetes.\n\nThe manifests define the following:\n\n- Send the environment variables defined to each application pod\n- Define the container image to use\n- Set resource consumption limits with the `resources` object\n- The `volumes` defined earlier and `volumeMounts` to define the path in the container to mount volumes.\n- Scaling and restart policies. The example manifests define one instance of each pod. You should change this to meet your needs.\n\n## Services\n\nThe two service manifests (`postgres-service.yaml` and `n8n-service.yaml`) expose the services to the outside world using the Kubernetes load balancer using ports 5432 and 5678 respectively.\n\n## Send to Kubernetes cluster\n\nSend all the manifests to the cluster with the following command:\n\n```\nkubectl apply -f .\n```\n\nNamespace error\n\nYou may see an error message about not finding an \"n8n\" namespace as that resources isn't ready yet. You can run the same command again, or apply the namespace manifest first with the following command:\n\n```\nkubectl apply -f namespace.yaml\n```\n\n## Set up DNS\n\nn8n typically operates on a subdomain. Create a DNS record with your provider for the subdomain and point it to the IP address of the n8n service. Find the IP address of the n8n service from the **Services & ingresses** menu item of the cluster you want to use under the **External IP** column. You need to add the n8n port, \"5678\" to the URL.\n\nStatic IP addresses with AKS\n\n[Read this tutorial](https://learn.microsoft.com/en-us/azure/aks/static-ip) for more details on how to use a static IP address with AKS.\n\n## Delete resources\n\nRemove the resources created by the manifests with the following command:\n\n```\nkubectl delete -f .\n```\n\n## Next steps\n\n- Learn more about [configuring](../../../configuration/environment-variables/) and [scaling](../../../scaling/overview/) n8n.\n- Or explore using n8n: try the [Quickstarts](../../../../try-it-out/).\n",
-        "excerpt": "# Hosting n8n on Azure  This hosting guide shows you how to self-host n8n on Azure. It uses n8n with Postgres as a database backend using Kubernetes to manage the necessary resources and reverse proxy.  ## Prerequisites  You need [The Azure command line tool](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli)  Self-hosting knowledge prerequisites  Self-hosting n8n requires technical knowledge, including:  - Setting up and configuring servers and containers - Managing application reso...",
-        "sections": [
-          {
-            "title": "Hosting n8n on Azure",
-            "level": 1,
-            "content": "This hosting guide shows you how to self-host n8n on Azure. It uses n8n with Postgres as a database backend using Kubernetes to manage the necessary resources and reverse proxy."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "azure",
-          "hosting",
-          "prerequisites",
-          "options",
-          "open",
-          "kubernetes",
-          "service",
-          "create",
-          "cluster",
-          "kubectl",
-          "context",
-          "clone",
-          "configuration",
-          "repository",
-          "configure",
-          "postgres",
-          "volume",
-          "persistent",
-          "storage",
-          "environment",
-          "variables",
-          "file",
-          "resources",
-          "optional:",
-          "deployments",
-          "services",
-          "send",
-          "delete",
-          "next",
-          "steps"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 7,
-        "complexity": "beginner",
-        "readingTime": "6 min",
-        "contentLength": 7701,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "azure # hosting n8n on azure\n\nthis hosting guide shows you how to self-host n8n on azure. it uses n8n with postgres as a database backend using kubernetes to manage the necessary resources and reverse proxy.\n\n## prerequisites\n\nyou need [the azure command line tool](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli)\n\nself-hosting knowledge prerequisites\n\nself-hosting n8n requires technical knowledge, including:\n\n- setting up and configuring servers and containers\n- managing application resources and scaling\n- securing servers and applications\n- configuring n8n\n\nn8n recommends self-hosting for expert users. mistakes can lead to data loss, security issues, and downtime. if you aren't experienced at managing servers, n8n recommends [n8n cloud](https://n8n.io/cloud/).\n\nstable and beta versions\n\nn8n releases a new minor version most weeks. the `stable` version is for production use. `beta` is the most recent release. the `beta` version may be unstable. to report issues, use the [forum](https://community.n8n.io/c/questions/12).\n\ncurrent `stable`: 2.14.2 current `beta`: 2.15.0\n\n## hosting options\n\nazure offers several ways suitable for hosting n8n, including azure container instances (optimized for running containers), linux virtual machines, and azure kubernetes service (containers running with kubernetes).\n\nthis guide uses the azure kubernetes service (aks) as the hosting option. using kubernetes requires some additional complexity and configuration, but is the best method for scaling n8n as demand changes.\n\nthe steps in this guide use a mix of the azure ui and command line tool, but you can use either to accomplish most tasks.\n\n## open the azure kubernetes service\n\nfrom [the azure portal](https://portal.azure.com/) select **kubernetes services**.\n\n## create a cluster\n\nfrom the kubernetes services page, select **create** > **create a kubernetes cluster**.\n\nyou can select any of the configuration options that suit your needs, then select **create** when done.\n\n## set kubectl context\n\nthe remainder of the steps in this guide require you to set the azure instance as the kubectl context. you can find the connection details for a cluster instance by opening its details page and then the **connect** button. the resulting code snippets shows the steps to paste and run into a terminal to change your local kubernetes settings to use the new cluster.\n\n## clone configuration repository\n\nkubernetes and n8n require a series of configuration files. you can clone these from [this repository](https://github.com/n8n-io/n8n-hosting). the following steps tell you which file configures what and what you need to change.\n\nclone the repository with the following command:\n\n```\ngit clone https://github.com/n8n-io/n8n-hosting.git\n```\n\nand change directory:\n\n```\ncd n8n-hosting/kubernetes\n```\n\n## configure postgres\n\nfor larger scale n8n deployments, postgres provides a more robust database backend than sqlite.\n\n### configure volume for persistent storage\n\nto maintain data between pod restarts, the postgres deployment needs a persistent volume. the default storage class is suitable for this purpose and is defined in the `postgres-claim0-persistentvolumeclaim.yaml` manifest.\n\nspecialized storage classes\n\nif you have specialised or higher requirements for storage classes, [read more on the options azure offers in the documentation](https://learn.microsoft.com/en-us/azure/aks/concepts-storage#storage-classes).\n\n### postgres environment variables\n\npostgres needs some environment variables set to pass to the application running in the containers.\n\nthe example `postgres-secret.yaml` file contains placeholders you need to replace with your own values. postgres will use these details when creating the database..\n\nthe `postgres-deployment.yaml` manifest then uses the values from this manifest file to send to the application pods.\n\n## configure n8n\n\n### create a volume for file storage\n\nwhile not essential for running n8n, using persistent volumes is required for:\n\n- using nodes that interact with files, such as the binary data node.\n- if you want to persist [manual n8n encryption keys](../../../configuration/environment-variables/deployment/) between restarts. this saves a file containing the key into file storage during startup.\n\nthe `n8n-claim0-persistentvolumeclaim.yaml` manifest creates this, and the n8n deployment mounts that claim in the `volumes` section of the `n8n-deployment.yaml` manifest.\n\n```\n…\nvolumes:\n  - name: n8n-claim0\n    persistentvolumeclaim:\n      claimname: n8n-claim0\n…\n```\n\n### pod resources\n\n[kubernetes lets you](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/) optionally specify the minimum resources application containers need and the limits they can run to. the example yaml files cloned above contain the following in the `resources` section of the `n8n-deployment.yaml` file:\n\n```\n…\nresources:\n  requests:\n    memory: \"250mi\"\n  limits:\n    memory: \"500mi\"\n…\n```\n\nthis defines a minimum of 250mb per container, a maximum of 500mb, and lets kubernetes handle cpu. you can change these values to match your own needs. as a guide, here are the resources values for the n8n cloud offerings:\n\n- **start**: 320mb ram, 10 millicore cpu burstable\n- **pro (10k executions)**: 640mb ram, 20 millicore cpu burstable\n- **pro (50k executions)**: 1280mb ram, 80 millicore cpu burstable\n\n### optional: environment variables\n\nyou can configure n8n settings and behaviors using environment variables.\n\ncreate an `n8n-secret.yaml` file. refer to [environment variables](../../../configuration/environment-variables/) for n8n environment variables details.\n\n## deployments\n\nthe two deployment manifests (`n8n-deployment.yaml` and `postgres-deployment.yaml`) define the n8n and postgres applications to kubernetes.\n\nthe manifests define the following:\n\n- send the environment variables defined to each application pod\n- define the container image to use\n- set resource consumption limits with the `resources` object\n- the `volumes` defined earlier and `volumemounts` to define the path in the container to mount volumes.\n- scaling and restart policies. the example manifests define one instance of each pod. you should change this to meet your needs.\n\n## services\n\nthe two service manifests (`postgres-service.yaml` and `n8n-service.yaml`) expose the services to the outside world using the kubernetes load balancer using ports 5432 and 5678 respectively.\n\n## send to kubernetes cluster\n\nsend all the manifests to the cluster with the following command:\n\n```\nkubectl apply -f .\n```\n\nnamespace error\n\nyou may see an error message about not finding an \"n8n\" namespace as that resources isn't ready yet. you can run the same command again, or apply the namespace manifest first with the following command:\n\n```\nkubectl apply -f namespace.yaml\n```\n\n## set up dns\n\nn8n typically operates on a subdomain. create a dns record with your provider for the subdomain and point it to the ip address of the n8n service. find the ip address of the n8n service from the **services & ingresses** menu item of the cluster you want to use under the **external ip** column. you need to add the n8n port, \"5678\" to the url.\n\nstatic ip addresses with aks\n\n[read this tutorial](https://learn.microsoft.com/en-us/azure/aks/static-ip) for more details on how to use a static ip address with aks.\n\n## delete resources\n\nremove the resources created by the manifests with the following command:\n\n```\nkubectl delete -f .\n```\n\n## next steps\n\n- learn more about [configuring](../../../configuration/environment-variables/) and [scaling](../../../scaling/overview/) n8n.\n- or explore using n8n: try the [quickstarts](../../../../try-it-out/).\n hosting n8n on azure",
-        "importantTerms": [
-          "azure",
-          "kubernetes",
-          "postgres",
-          "yaml",
-          "hosting",
-          "this",
-          "with",
-          "resources",
-          "environment",
-          "variables",
-          "https",
-          "deployment",
-          "using",
-          "service",
-          "configuration",
-          "file",
-          "storage",
-          "command",
-          "create",
-          "cluster",
-          "following",
-          "containers",
-          "your",
-          "manifest",
-          "manifests",
-          "guide",
-          "need",
-          "application",
-          "scaling",
-          "steps",
-          "from",
-          "services",
-          "needs",
-          "kubectl",
-          "details",
-          "change",
-          "volumes",
-          "define",
-          "self",
-          "learn",
-          "beta",
-          "container",
-          "running",
-          "select",
-          "that",
-          "clone",
-          "configure",
-          "more",
-          "values",
-          "send"
-        ]
-      }
-    },
-    {
-      "id": "page-0202",
-      "title": "Digital Ocean",
-      "url": "https://docs.n8n.io/hosting/installation/server-setups/digital-ocean/index.md",
-      "urlPath": "hosting/installation/server-setups/digital-ocean/index.md",
-      "category": "hosting",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
       "content": {
         "markdown": "# Hosting n8n on DigitalOcean\n\nThis hosting guide shows you how to self-host n8n on a DigitalOcean droplet. It uses:\n\n- [Caddy](https://caddyserver.com) (a reverse proxy) to allow access to the Droplet from the internet. Caddy will also automatically create and manage SSL / TLS certificates for your n8n instance.\n- [Docker Compose](https://docs.docker.com/compose/) to create and define the application components and how they work together.\n\nSelf-hosting knowledge prerequisites\n\nSelf-hosting n8n requires technical knowledge, including:\n\n- Setting up and configuring servers and containers\n- Managing application resources and scaling\n- Securing servers and applications\n- Configuring n8n\n\nn8n recommends self-hosting for expert users. Mistakes can lead to data loss, security issues, and downtime. If you aren't experienced at managing servers, n8n recommends [n8n Cloud](https://n8n.io/cloud/).\n\nStable and Beta versions\n\nn8n releases a new minor version most weeks. The `stable` version is for production use. `beta` is the most recent release. The `beta` version may be unstable. To report issues, use the [forum](https://community.n8n.io/c/questions/12).\n\nCurrent `stable`: 2.14.2 Current `beta`: 2.15.0\n\n## Create a Droplet\n\n1. [Log in](https://cloud.digitalocean.com/login) to DigitalOcean.\n1. Select the project to host the Droplet, or [create a new project](https://docs.digitalocean.com/products/projects/how-to/create/).\n1. In your project, select **Droplets** from the **Manage** menu.\n1. [Create a new Droplet](https://docs.digitalocean.com/products/droplets/how-to/create/) using the [Docker image](https://marketplace.digitalocean.com/apps/docker) available on the **Marketplace** tab.\n\nDroplet resources\n\nWhen creating the Droplet, DigitalOcean asks you to choose a plan. For most usage levels, a basic shared CPU plan is enough.\n\nSSH key or Password\n\nDigitalOcean lets you choose between SSH key and password-based authentication. SSH keys are considered more secure.\n\n## Log in to your Droplet and create new user\n\nThe rest of this guide requires you to log in to the Droplet using a terminal with SSH. Refer to [How to Connect to Droplets with SSH](https://docs.digitalocean.com/products/droplets/how-to/connect-with-ssh/) for more information.\n\nYou should create a new user, to avoid working as the root user:\n\n1. Log in as root.\n\n1. Create a new user:\n\n   ```\n   adduser <username>\n   ```\n\n1. Follow the prompts in the CLI to finish creating the user.\n\n1. Grant the new user administrative privileges:\n\n   ```\n   usermod -aG sudo <username>\n   ```\n\n   You can now run commands with superuser privileges by using `sudo` before the command.\n\n1. Follow the steps to set up SSH for the new user: [Add Public Key Authentication](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-14-04#step-four-add-public-key-authentication-recommended).\n\n1. Log out of the droplet.\n\n1. Log in using SSH as the new user.\n\n## Clone configuration repository\n\nDocker Compose, n8n, and Caddy require a series of folders and configuration files. You can clone these from [this repository](https://github.com/n8n-io/n8n-docker-caddy) into the home folder of the logged-in user on your Droplet. The following steps will tell you which file to change and what changes to make.\n\nClone the repository with the following command:\n\n```\ngit clone https://github.com/n8n-io/n8n-docker-caddy.git\n```\n\nAnd change directory to the root of the repository you cloned:\n\n```\ncd n8n-docker-caddy\n```\n\n## Default folders and files\n\nThe host operating system (the DigitalOcean Droplet) copies the two folders you created to Docker containers to make them available to Docker. The two folders are:\n\n- `caddy_config`: Holds the Caddy configuration files.\n- `local_files`: A folder for files you upload or add using n8n.\n\n### Create Docker volumes\n\nTo persist the Caddy cache between restarts and speed up start times, create [a Docker volume](https://docs.docker.com/storage/volumes/) that Docker reuses between restarts:\n\n```\nsudo docker volume create caddy_data\n```\n\nCreate a Docker volume for the n8n data:\n\n```\nsudo docker volume create n8n_data\n```\n\n## Set up DNS\n\nn8n typically operates on a subdomain. Create a DNS record with your provider for the subdomain and point it to the IP address of the Droplet. The exact steps for this depend on your DNS provider, but typically you need to create a new \"A\" record for the n8n subdomain. DigitalOcean provide [An Introduction to DNS Terminology, Components, and Concepts](https://www.digitalocean.com/community/tutorials/an-introduction-to-dns-terminology-components-and-concepts).\n\n## Open ports\n\nn8n runs as a web application, so the Droplet needs to allow incoming access to traffic on port 80 for non-secure traffic, and port 443 for secure traffic.\n\nOpen the following ports in the Droplet's firewall by running the following two commands:\n\n```\nsudo ufw allow 80\nsudo ufw allow 443\n```\n\n## Configure n8n\n\nn8n needs some environment variables set to pass to the application running in the Docker container. The example `.env` file contains placeholders you need to replace with values of your own.\n\nOpen the file with the following command:\n\n```\nnano .env\n```\n\nThe file contains inline comments to help you know what to change.\n\nRefer to [Environment variables](../../../configuration/environment-variables/) for n8n environment variables details.\n\n## The Docker Compose file\n\nThe Docker Compose file (`docker-compose.yml`) defines the services the application needs, in this case Caddy and n8n.\n\n- The Caddy service definition defines the ports it uses and the local volumes to copy to the containers.\n- The n8n service definition defines the ports it uses, the environment variables n8n needs to run (some defined in the `.env` file), and the volumes it needs to copy to the containers.\n\nThe Docker Compose file uses the environment variables set in the `.env` file, so you shouldn't need to change it's content, but to take a look, run the following command:\n\n```\nnano docker-compose.yml\n```\n\n## Configure Caddy\n\nCaddy needs to know which domains it should serve, and which port to expose to the outside world. Edit the `Caddyfile` file in the `caddy_config` folder.\n\n```\nnano caddy_config/Caddyfile\n```\n\nChange the placeholder domain to yours. If you followed the steps to name the subdomain n8n, your full domain is similar to `n8n.example.com`. The `n8n` in the `reverse_proxy` setting tells Caddy to use the service definition defined in the `docker-compose.yml` file:\n\n```\nn8n.<domain>.<suffix> {\n    reverse_proxy n8n:5678 {\n      flush_interval -1\n    }\n}\n```\n\nIf you were to use `automate.example.com`, your `Caddyfile` may look something like:\n\n```\nautomate.example.com {\n    reverse_proxy n8n:5678 {\n      flush_interval -1\n    }\n}\n```\n\n## Start Docker Compose\n\nStart n8n and Caddy with the following command:\n\n```\nsudo docker compose up -d\n```\n\nThis may take a few minutes.\n\n## Test your setup\n\nIn your browser, open the URL formed of the subdomain and domain name defined earlier. Enter the user name and password defined earlier, and you should be able to access n8n.\n\n## Stop n8n and Caddy\n\nYou can stop n8n and Caddy with the following command:\n\n```\nsudo docker compose stop\n```\n\n## Updating\n\nIf you run n8n using a Docker Compose file, follow these steps to update n8n:\n\n```\n# Navigate to the directory containing your docker compose file\ncd </path/to/your/compose/file/directory>\n\n# Pull latest version\ndocker compose pull\n\n# Stop and remove older version\ndocker compose down\n\n# Start the container\ndocker compose up -d\n```\n\n## Next steps\n\n- Learn more about [configuring](../../../configuration/environment-variables/) and [scaling](../../../scaling/overview/) n8n.\n- Or explore using n8n: try the [Quickstarts](../../../../try-it-out/).\n",
         "excerpt": "# Hosting n8n on DigitalOcean  This hosting guide shows you how to self-host n8n on a DigitalOcean droplet. It uses:  - [Caddy](https://caddyserver.com) (a reverse proxy) to allow access to the Droplet from the internet. Caddy will also automatically create and manage SSL / TLS certificates for your n8n instance. - [Docker Compose](https://docs.docker.com/compose/) to create and define the application components and how they work together.  Self-hosting knowledge prerequisites  Self-hosting n8n...",
@@ -16973,42 +16855,34 @@
       },
       "metadata": {
         "keywords": [
-          "digital",
-          "ocean",
+          "azure",
           "hosting",
-          "digitalocean",
+          "prerequisites",
+          "options",
+          "open",
+          "kubernetes",
+          "service",
           "create",
-          "droplet",
-          "your",
-          "user",
+          "cluster",
+          "kubectl",
+          "context",
           "clone",
           "configuration",
           "repository",
-          "default",
-          "folders",
-          "files",
-          "docker",
-          "volumes",
-          "open",
-          "ports",
           "configure",
-          "compose",
+          "postgres",
+          "volume",
+          "persistent",
+          "storage",
+          "environment",
+          "variables",
           "file",
-          "caddy",
-          "start",
-          "test",
-          "setup",
-          "stop",
-          "updating",
-          "navigate",
-          "directory",
-          "containing",
-          "pull",
-          "latest",
-          "version",
-          "remove",
-          "older",
-          "container",
+          "resources",
+          "optional:",
+          "deployments",
+          "services",
+          "send",
+          "delete",
           "next",
           "steps"
         ],
@@ -17021,7 +16895,7 @@
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "digital ocean # hosting n8n on digitalocean\n\nthis hosting guide shows you how to self-host n8n on a digitalocean droplet. it uses:\n\n- [caddy](https://caddyserver.com) (a reverse proxy) to allow access to the droplet from the internet. caddy will also automatically create and manage ssl / tls certificates for your n8n instance.\n- [docker compose](https://docs.docker.com/compose/) to create and define the application components and how they work together.\n\nself-hosting knowledge prerequisites\n\nself-hosting n8n requires technical knowledge, including:\n\n- setting up and configuring servers and containers\n- managing application resources and scaling\n- securing servers and applications\n- configuring n8n\n\nn8n recommends self-hosting for expert users. mistakes can lead to data loss, security issues, and downtime. if you aren't experienced at managing servers, n8n recommends [n8n cloud](https://n8n.io/cloud/).\n\nstable and beta versions\n\nn8n releases a new minor version most weeks. the `stable` version is for production use. `beta` is the most recent release. the `beta` version may be unstable. to report issues, use the [forum](https://community.n8n.io/c/questions/12).\n\ncurrent `stable`: 2.14.2 current `beta`: 2.15.0\n\n## create a droplet\n\n1. [log in](https://cloud.digitalocean.com/login) to digitalocean.\n1. select the project to host the droplet, or [create a new project](https://docs.digitalocean.com/products/projects/how-to/create/).\n1. in your project, select **droplets** from the **manage** menu.\n1. [create a new droplet](https://docs.digitalocean.com/products/droplets/how-to/create/) using the [docker image](https://marketplace.digitalocean.com/apps/docker) available on the **marketplace** tab.\n\ndroplet resources\n\nwhen creating the droplet, digitalocean asks you to choose a plan. for most usage levels, a basic shared cpu plan is enough.\n\nssh key or password\n\ndigitalocean lets you choose between ssh key and password-based authentication. ssh keys are considered more secure.\n\n## log in to your droplet and create new user\n\nthe rest of this guide requires you to log in to the droplet using a terminal with ssh. refer to [how to connect to droplets with ssh](https://docs.digitalocean.com/products/droplets/how-to/connect-with-ssh/) for more information.\n\nyou should create a new user, to avoid working as the root user:\n\n1. log in as root.\n\n1. create a new user:\n\n   ```\n   adduser <username>\n   ```\n\n1. follow the prompts in the cli to finish creating the user.\n\n1. grant the new user administrative privileges:\n\n   ```\n   usermod -ag sudo <username>\n   ```\n\n   you can now run commands with superuser privileges by using `sudo` before the command.\n\n1. follow the steps to set up ssh for the new user: [add public key authentication](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-14-04#step-four-add-public-key-authentication-recommended).\n\n1. log out of the droplet.\n\n1. log in using ssh as the new user.\n\n## clone configuration repository\n\ndocker compose, n8n, and caddy require a series of folders and configuration files. you can clone these from [this repository](https://github.com/n8n-io/n8n-docker-caddy) into the home folder of the logged-in user on your droplet. the following steps will tell you which file to change and what changes to make.\n\nclone the repository with the following command:\n\n```\ngit clone https://github.com/n8n-io/n8n-docker-caddy.git\n```\n\nand change directory to the root of the repository you cloned:\n\n```\ncd n8n-docker-caddy\n```\n\n## default folders and files\n\nthe host operating system (the digitalocean droplet) copies the two folders you created to docker containers to make them available to docker. the two folders are:\n\n- `caddy_config`: holds the caddy configuration files.\n- `local_files`: a folder for files you upload or add using n8n.\n\n### create docker volumes\n\nto persist the caddy cache between restarts and speed up start times, create [a docker volume](https://docs.docker.com/storage/volumes/) that docker reuses between restarts:\n\n```\nsudo docker volume create caddy_data\n```\n\ncreate a docker volume for the n8n data:\n\n```\nsudo docker volume create n8n_data\n```\n\n## set up dns\n\nn8n typically operates on a subdomain. create a dns record with your provider for the subdomain and point it to the ip address of the droplet. the exact steps for this depend on your dns provider, but typically you need to create a new \"a\" record for the n8n subdomain. digitalocean provide [an introduction to dns terminology, components, and concepts](https://www.digitalocean.com/community/tutorials/an-introduction-to-dns-terminology-components-and-concepts).\n\n## open ports\n\nn8n runs as a web application, so the droplet needs to allow incoming access to traffic on port 80 for non-secure traffic, and port 443 for secure traffic.\n\nopen the following ports in the droplet's firewall by running the following two commands:\n\n```\nsudo ufw allow 80\nsudo ufw allow 443\n```\n\n## configure n8n\n\nn8n needs some environment variables set to pass to the application running in the docker container. the example `.env` file contains placeholders you need to replace with values of your own.\n\nopen the file with the following command:\n\n```\nnano .env\n```\n\nthe file contains inline comments to help you know what to change.\n\nrefer to [environment variables](../../../configuration/environment-variables/) for n8n environment variables details.\n\n## the docker compose file\n\nthe docker compose file (`docker-compose.yml`) defines the services the application needs, in this case caddy and n8n.\n\n- the caddy service definition defines the ports it uses and the local volumes to copy to the containers.\n- the n8n service definition defines the ports it uses, the environment variables n8n needs to run (some defined in the `.env` file), and the volumes it needs to copy to the containers.\n\nthe docker compose file uses the environment variables set in the `.env` file, so you shouldn't need to change it's content, but to take a look, run the following command:\n\n```\nnano docker-compose.yml\n```\n\n## configure caddy\n\ncaddy needs to know which domains it should serve, and which port to expose to the outside world. edit the `caddyfile` file in the `caddy_config` folder.\n\n```\nnano caddy_config/caddyfile\n```\n\nchange the placeholder domain to yours. if you followed the steps to name the subdomain n8n, your full domain is similar to `n8n.example.com`. the `n8n` in the `reverse_proxy` setting tells caddy to use the service definition defined in the `docker-compose.yml` file:\n\n```\nn8n.<domain>.<suffix> {\n    reverse_proxy n8n:5678 {\n      flush_interval -1\n    }\n}\n```\n\nif you were to use `automate.example.com`, your `caddyfile` may look something like:\n\n```\nautomate.example.com {\n    reverse_proxy n8n:5678 {\n      flush_interval -1\n    }\n}\n```\n\n## start docker compose\n\nstart n8n and caddy with the following command:\n\n```\nsudo docker compose up -d\n```\n\nthis may take a few minutes.\n\n## test your setup\n\nin your browser, open the url formed of the subdomain and domain name defined earlier. enter the user name and password defined earlier, and you should be able to access n8n.\n\n## stop n8n and caddy\n\nyou can stop n8n and caddy with the following command:\n\n```\nsudo docker compose stop\n```\n\n## updating\n\nif you run n8n using a docker compose file, follow these steps to update n8n:\n\n```\n# navigate to the directory containing your docker compose file\ncd </path/to/your/compose/file/directory>\n\n# pull latest version\ndocker compose pull\n\n# stop and remove older version\ndocker compose down\n\n# start the container\ndocker compose up -d\n```\n\n## next steps\n\n- learn more about [configuring](../../../configuration/environment-variables/) and [scaling](../../../scaling/overview/) n8n.\n- or explore using n8n: try the [quickstarts](../../../../try-it-out/).\n hosting n8n on digitalocean navigate to the directory containing your docker compose file pull latest version stop and remove older version start the container",
+        "fullText": "azure # hosting n8n on digitalocean\n\nthis hosting guide shows you how to self-host n8n on a digitalocean droplet. it uses:\n\n- [caddy](https://caddyserver.com) (a reverse proxy) to allow access to the droplet from the internet. caddy will also automatically create and manage ssl / tls certificates for your n8n instance.\n- [docker compose](https://docs.docker.com/compose/) to create and define the application components and how they work together.\n\nself-hosting knowledge prerequisites\n\nself-hosting n8n requires technical knowledge, including:\n\n- setting up and configuring servers and containers\n- managing application resources and scaling\n- securing servers and applications\n- configuring n8n\n\nn8n recommends self-hosting for expert users. mistakes can lead to data loss, security issues, and downtime. if you aren't experienced at managing servers, n8n recommends [n8n cloud](https://n8n.io/cloud/).\n\nstable and beta versions\n\nn8n releases a new minor version most weeks. the `stable` version is for production use. `beta` is the most recent release. the `beta` version may be unstable. to report issues, use the [forum](https://community.n8n.io/c/questions/12).\n\ncurrent `stable`: 2.14.2 current `beta`: 2.15.0\n\n## create a droplet\n\n1. [log in](https://cloud.digitalocean.com/login) to digitalocean.\n1. select the project to host the droplet, or [create a new project](https://docs.digitalocean.com/products/projects/how-to/create/).\n1. in your project, select **droplets** from the **manage** menu.\n1. [create a new droplet](https://docs.digitalocean.com/products/droplets/how-to/create/) using the [docker image](https://marketplace.digitalocean.com/apps/docker) available on the **marketplace** tab.\n\ndroplet resources\n\nwhen creating the droplet, digitalocean asks you to choose a plan. for most usage levels, a basic shared cpu plan is enough.\n\nssh key or password\n\ndigitalocean lets you choose between ssh key and password-based authentication. ssh keys are considered more secure.\n\n## log in to your droplet and create new user\n\nthe rest of this guide requires you to log in to the droplet using a terminal with ssh. refer to [how to connect to droplets with ssh](https://docs.digitalocean.com/products/droplets/how-to/connect-with-ssh/) for more information.\n\nyou should create a new user, to avoid working as the root user:\n\n1. log in as root.\n\n1. create a new user:\n\n   ```\n   adduser <username>\n   ```\n\n1. follow the prompts in the cli to finish creating the user.\n\n1. grant the new user administrative privileges:\n\n   ```\n   usermod -ag sudo <username>\n   ```\n\n   you can now run commands with superuser privileges by using `sudo` before the command.\n\n1. follow the steps to set up ssh for the new user: [add public key authentication](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-14-04#step-four-add-public-key-authentication-recommended).\n\n1. log out of the droplet.\n\n1. log in using ssh as the new user.\n\n## clone configuration repository\n\ndocker compose, n8n, and caddy require a series of folders and configuration files. you can clone these from [this repository](https://github.com/n8n-io/n8n-docker-caddy) into the home folder of the logged-in user on your droplet. the following steps will tell you which file to change and what changes to make.\n\nclone the repository with the following command:\n\n```\ngit clone https://github.com/n8n-io/n8n-docker-caddy.git\n```\n\nand change directory to the root of the repository you cloned:\n\n```\ncd n8n-docker-caddy\n```\n\n## default folders and files\n\nthe host operating system (the digitalocean droplet) copies the two folders you created to docker containers to make them available to docker. the two folders are:\n\n- `caddy_config`: holds the caddy configuration files.\n- `local_files`: a folder for files you upload or add using n8n.\n\n### create docker volumes\n\nto persist the caddy cache between restarts and speed up start times, create [a docker volume](https://docs.docker.com/storage/volumes/) that docker reuses between restarts:\n\n```\nsudo docker volume create caddy_data\n```\n\ncreate a docker volume for the n8n data:\n\n```\nsudo docker volume create n8n_data\n```\n\n## set up dns\n\nn8n typically operates on a subdomain. create a dns record with your provider for the subdomain and point it to the ip address of the droplet. the exact steps for this depend on your dns provider, but typically you need to create a new \"a\" record for the n8n subdomain. digitalocean provide [an introduction to dns terminology, components, and concepts](https://www.digitalocean.com/community/tutorials/an-introduction-to-dns-terminology-components-and-concepts).\n\n## open ports\n\nn8n runs as a web application, so the droplet needs to allow incoming access to traffic on port 80 for non-secure traffic, and port 443 for secure traffic.\n\nopen the following ports in the droplet's firewall by running the following two commands:\n\n```\nsudo ufw allow 80\nsudo ufw allow 443\n```\n\n## configure n8n\n\nn8n needs some environment variables set to pass to the application running in the docker container. the example `.env` file contains placeholders you need to replace with values of your own.\n\nopen the file with the following command:\n\n```\nnano .env\n```\n\nthe file contains inline comments to help you know what to change.\n\nrefer to [environment variables](../../../configuration/environment-variables/) for n8n environment variables details.\n\n## the docker compose file\n\nthe docker compose file (`docker-compose.yml`) defines the services the application needs, in this case caddy and n8n.\n\n- the caddy service definition defines the ports it uses and the local volumes to copy to the containers.\n- the n8n service definition defines the ports it uses, the environment variables n8n needs to run (some defined in the `.env` file), and the volumes it needs to copy to the containers.\n\nthe docker compose file uses the environment variables set in the `.env` file, so you shouldn't need to change it's content, but to take a look, run the following command:\n\n```\nnano docker-compose.yml\n```\n\n## configure caddy\n\ncaddy needs to know which domains it should serve, and which port to expose to the outside world. edit the `caddyfile` file in the `caddy_config` folder.\n\n```\nnano caddy_config/caddyfile\n```\n\nchange the placeholder domain to yours. if you followed the steps to name the subdomain n8n, your full domain is similar to `n8n.example.com`. the `n8n` in the `reverse_proxy` setting tells caddy to use the service definition defined in the `docker-compose.yml` file:\n\n```\nn8n.<domain>.<suffix> {\n    reverse_proxy n8n:5678 {\n      flush_interval -1\n    }\n}\n```\n\nif you were to use `automate.example.com`, your `caddyfile` may look something like:\n\n```\nautomate.example.com {\n    reverse_proxy n8n:5678 {\n      flush_interval -1\n    }\n}\n```\n\n## start docker compose\n\nstart n8n and caddy with the following command:\n\n```\nsudo docker compose up -d\n```\n\nthis may take a few minutes.\n\n## test your setup\n\nin your browser, open the url formed of the subdomain and domain name defined earlier. enter the user name and password defined earlier, and you should be able to access n8n.\n\n## stop n8n and caddy\n\nyou can stop n8n and caddy with the following command:\n\n```\nsudo docker compose stop\n```\n\n## updating\n\nif you run n8n using a docker compose file, follow these steps to update n8n:\n\n```\n# navigate to the directory containing your docker compose file\ncd </path/to/your/compose/file/directory>\n\n# pull latest version\ndocker compose pull\n\n# stop and remove older version\ndocker compose down\n\n# start the container\ndocker compose up -d\n```\n\n## next steps\n\n- learn more about [configuring](../../../configuration/environment-variables/) and [scaling](../../../scaling/overview/) n8n.\n- or explore using n8n: try the [quickstarts](../../../../try-it-out/).\n hosting n8n on digitalocean navigate to the directory containing your docker compose file pull latest version stop and remove older version start the container",
         "importantTerms": [
           "docker",
           "compose",
@@ -38571,102 +38445,6 @@
     },
     {
       "id": "page-0503",
-      "title": "Event operations",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/event-operations/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/event-operations/index.md",
-      "category": "integrations",
-      "subcategory": "app-nodes",
-      "nodeName": "googlecalendar",
-      "nodeType": "n8n-nodes-base.googlecalendar",
-      "content": {
-        "markdown": "# Google Calendar Event operations\n\nUse these operations to create, delete, get, and update events in Google Calendar. Refer to [Google Calendar](../) for more information on the Google Calendar node itself.\n\n## Create\n\nUse this operation to add an event to a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Create**.\n- **Calendar**: Choose a calendar you want to add an event to. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Start Time**: The start time for the event. By default, uses an expression evaluating to the current time (`{{ $now }}`).\n- **End Time**: The end time for the event. By default, this uses an expression evaluating to an hour from now (`{{ $now.plus(1, 'hour') }}`).\n- **Use Default Reminders**: Whether to enable default reminders for the event according to the calendar configuration.\n\n### Options\n\n- **All Day**: Whether the event is all day or not.\n\n- **Attendees**: Attendees to invite to the event.\n\n- **Color Name or ID**: The color of the event. Choose from the list or specify the ID using an expression.\n\n- **Conference Data**: Creates a conference link (Hangouts, Meet, etc.) and attaches it to the event.\n\n- **Description**: A description for the event.\n\n- **Guests Can Invite Others**: Whether attendees other than the organizer can invite others to the event.\n\n- **Guests Can Modify**: Whether attendees other than the organizer can modify the event.\n\n- **Guests Can See Other Guests**: Whether attendees other than the organizer can see who the event's attendees are.\n\n- **ID**: Opaque identifier of the event.\n\n- **Location**: Geographic location of the event as free-form text.\n\n- **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n\n- **Repeat Frequency**: The repetition interval for recurring events.\n\n- **Repeat How Many Times?**: The number of instances to create for recurring events.\n\n- **Repeat Until**: The date at which recurring events should stop.\n\n- **RRULE**: Recurrence rule. When set, ignores the Repeat Frequency, Repeat How Many Times, and Repeat Until parameters.\n\n- **Send Updates**: Whether to send notifications about the creation of the new event.\n\n- **Show Me As**: Whether the event blocks time on the calendar.\n\n- **Summary**: The title of the event.\n\nRefer to the [Events: insert | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/insert) API documentation for more information.\n\n## Delete\n\nUse this operation to delete an event from a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Delete**.\n- **Calendar**: Choose a calendar you want to delete an event from. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Event ID**: The ID of the event to delete.\n\n### Options\n\n- **Send Updates**: Whether to send notifications about the deletion of the event.\n\nRefer to the [Events: delete | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/delete) API documentation for more information.\n\n## Get\n\nUse this operation to retrieve an event from a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Get**.\n- **Calendar**: Choose a calendar you want to get an event from. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Event ID**: The ID of the event to get.\n\n### Options\n\n- **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n- **Return Next Instance of Recurrent Event**: Whether to return the next instance of a recurring event instead of the event itself.\n- **Timezone**: The timezone used in the response. By default, uses the n8n timezone.\n\nRefer to the [Events: get | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/get) API documentation for more information.\n\n## Get Many\n\nUse this operation to retrieve more than one event from a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Get Many**.\n- **Calendar**: Choose a calendar you want to get an event from. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Return All**: Whether to return all results or only up to a given limit.\n- **Limit**: (When \"Return All\" isn't selected) The maximum number of results to return.\n- **After**: Retrieve events that occur after this time. At least part of the event must be after this time. By default, this uses an expression evaluating to the current time (`{{ $now }}`). Switch the field to \"fixed\" to select a date from a date widget.\n- **Before**: Retrieve events that occur before this time. At least part of the event must be before this time. By default, this uses an expression evaluating to the current time plus a week (`{{ $now.plus({ week: 1 }) }}`). Switch the field to \"fixed\" to select a date from a date widget.\n\n### Options\n\n- **Fields**: Specify the fields to return. By default, returns a set of commonly used fields predefined by Google. Use \"\\*\" to return all fields. You can find out more in [Google Calendar's documentation on working with partial resources](https://developers.google.com/calendar/api/guides/performance#partial).\n\n- **iCalUID**: Specifies an event ID (in the iCalendar format) to include in the response.\n\n- **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n\n- **Order By**: The order to use for the events in the response.\n\n- **Query**: Free text search terms to find events that match. This searches all fields except for extended properties.\n\n- **Recurring Event Handling**: What to do for recurring events:\n\n  - **All Occurrences**: Return all instances of the recurring event for the specified time range.\n  - **First Occurrence**: Return the first event of a recurring event within the specified time range.\n  - **Next Occurrence**: Return the next instance of a recurring event within the specified time range.\n\n- **Show Deleted**: Whether to include deleted events (with status equal to \"cancelled\") in the results.\n\n- **Show Hidden Invitations**: Whether to include hidden invitations in the results.\n\n- **Timezone**: The timezone used in the response. By default, uses the n8n timezone.\n\n- **Updated Min**: The lower bounds for an event's last modification time (as an [RFC 3339 timestamp](https://datatracker.ietf.org/doc/html/rfc3339))\n\nRefer to the [Events: list | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/list) API documentation for more information.\n\n## Update\n\nUse this operation to update an event in a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n\n- **Resource**: Select **Event**.\n\n- **Operation**: Select **Update**.\n\n- **Calendar**: Choose a calendar you want to add an event to. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n\n- **Event ID**: The ID of the event to update.\n\n- **Modify**: For recurring events, choose whether to update the recurring event or a specific instance of the recurring event.\n\n- **Use Default Reminders**: Whether to enable default reminders for the event according to the calendar configuration.\n\n- **Update Fields**: The fields of the event to update:\n\n  - **All Day**: Whether the event is all day or not.\n  - **Attendees**: Attendees to invite to the event. You can choose to either add attendees or replace the existing attendee list.\n  - **Color Name or ID**: The color of the event. Choose from the list or specify the ID using an expression.\n  - **Description**: A description for the event.\n  - **End**: The end time of the event.\n  - **Guests Can Invite Others**: Whether attendees other than the organizer can invite others to the event.\n  - **Guests Can Modify**: Whether attendees other than the organizer can make changes to the event.\n  - **Guests Can See Other Guests**: Whether attendees other than the organizer can see who the event's attendees are.\n  - **ID**: Opaque identifier of the event.\n  - **Location**: Geographic location of the event as free-form text.\n  - **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n  - **Repeat Frequency**: The repetition interval for recurring events.\n  - **Repeat How Many Times?**: The number of instances to create for recurring events.\n  - **Repeat Until**: The date at which recurring events should stop.\n  - **RRULE**: Recurrence rule. When set, ignores the Repeat Frequency, Repeat How Many Times, and Repeat Until parameters.\n  - **Send Updates**: Whether to send notifications about the creation of the new event.\n  - **Show Me As**: Whether the event blocks time on the calendar.\n  - **Start**: The start time of the event.\n  - **Summary**: The title of the event.\n  - **Visibility**: The visibility of the event:\n    - **Confidential**: The event is private. This value is provided for compatibility.\n    - **Default**: Uses the default visibility for events on the calendar.\n    - **Public**: The event is public and the event details are visible to all readers of the calendar.\n    - **Private**: The event is private and only event attendees may view event details.\n\nRefer to the [Events: update | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/update) API documentation for more information.\n",
-        "excerpt": "# Google Calendar Event operations  Use these operations to create, delete, get, and update events in Google Calendar. Refer to [Google Calendar](../) for more information on the Google Calendar node itself.  ## Create  Use this operation to add an event to a Google Calendar.  Enter these parameters:  - **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/). - **Resource**: Select **Event**. - **Operation**: Select **Create**. - *...",
-        "sections": [
-          {
-            "title": "Google Calendar Event operations",
-            "level": 1,
-            "content": "Use these operations to create, delete, get, and update events in Google Calendar. Refer to [Google Calendar](../) for more information on the Google Calendar node itself."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "event",
-          "operations",
-          "google",
-          "calendar",
-          "create",
-          "options",
-          "delete",
-          "many",
-          "update"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "intermediate",
-        "readingTime": "8 min",
-        "contentLength": 10453,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "event operations # google calendar event operations\n\nuse these operations to create, delete, get, and update events in google calendar. refer to [google calendar](../) for more information on the google calendar node itself.\n\n## create\n\nuse this operation to add an event to a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **create**.\n- **calendar**: choose a calendar you want to add an event to. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **start time**: the start time for the event. by default, uses an expression evaluating to the current time (`{{ $now }}`).\n- **end time**: the end time for the event. by default, this uses an expression evaluating to an hour from now (`{{ $now.plus(1, 'hour') }}`).\n- **use default reminders**: whether to enable default reminders for the event according to the calendar configuration.\n\n### options\n\n- **all day**: whether the event is all day or not.\n\n- **attendees**: attendees to invite to the event.\n\n- **color name or id**: the color of the event. choose from the list or specify the id using an expression.\n\n- **conference data**: creates a conference link (hangouts, meet, etc.) and attaches it to the event.\n\n- **description**: a description for the event.\n\n- **guests can invite others**: whether attendees other than the organizer can invite others to the event.\n\n- **guests can modify**: whether attendees other than the organizer can modify the event.\n\n- **guests can see other guests**: whether attendees other than the organizer can see who the event's attendees are.\n\n- **id**: opaque identifier of the event.\n\n- **location**: geographic location of the event as free-form text.\n\n- **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n\n- **repeat frequency**: the repetition interval for recurring events.\n\n- **repeat how many times?**: the number of instances to create for recurring events.\n\n- **repeat until**: the date at which recurring events should stop.\n\n- **rrule**: recurrence rule. when set, ignores the repeat frequency, repeat how many times, and repeat until parameters.\n\n- **send updates**: whether to send notifications about the creation of the new event.\n\n- **show me as**: whether the event blocks time on the calendar.\n\n- **summary**: the title of the event.\n\nrefer to the [events: insert | google calendar](https://developers.google.com/calendar/api/v3/reference/events/insert) api documentation for more information.\n\n## delete\n\nuse this operation to delete an event from a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **delete**.\n- **calendar**: choose a calendar you want to delete an event from. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **event id**: the id of the event to delete.\n\n### options\n\n- **send updates**: whether to send notifications about the deletion of the event.\n\nrefer to the [events: delete | google calendar](https://developers.google.com/calendar/api/v3/reference/events/delete) api documentation for more information.\n\n## get\n\nuse this operation to retrieve an event from a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **get**.\n- **calendar**: choose a calendar you want to get an event from. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **event id**: the id of the event to get.\n\n### options\n\n- **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n- **return next instance of recurrent event**: whether to return the next instance of a recurring event instead of the event itself.\n- **timezone**: the timezone used in the response. by default, uses the n8n timezone.\n\nrefer to the [events: get | google calendar](https://developers.google.com/calendar/api/v3/reference/events/get) api documentation for more information.\n\n## get many\n\nuse this operation to retrieve more than one event from a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **get many**.\n- **calendar**: choose a calendar you want to get an event from. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **return all**: whether to return all results or only up to a given limit.\n- **limit**: (when \"return all\" isn't selected) the maximum number of results to return.\n- **after**: retrieve events that occur after this time. at least part of the event must be after this time. by default, this uses an expression evaluating to the current time (`{{ $now }}`). switch the field to \"fixed\" to select a date from a date widget.\n- **before**: retrieve events that occur before this time. at least part of the event must be before this time. by default, this uses an expression evaluating to the current time plus a week (`{{ $now.plus({ week: 1 }) }}`). switch the field to \"fixed\" to select a date from a date widget.\n\n### options\n\n- **fields**: specify the fields to return. by default, returns a set of commonly used fields predefined by google. use \"\\*\" to return all fields. you can find out more in [google calendar's documentation on working with partial resources](https://developers.google.com/calendar/api/guides/performance#partial).\n\n- **icaluid**: specifies an event id (in the icalendar format) to include in the response.\n\n- **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n\n- **order by**: the order to use for the events in the response.\n\n- **query**: free text search terms to find events that match. this searches all fields except for extended properties.\n\n- **recurring event handling**: what to do for recurring events:\n\n  - **all occurrences**: return all instances of the recurring event for the specified time range.\n  - **first occurrence**: return the first event of a recurring event within the specified time range.\n  - **next occurrence**: return the next instance of a recurring event within the specified time range.\n\n- **show deleted**: whether to include deleted events (with status equal to \"cancelled\") in the results.\n\n- **show hidden invitations**: whether to include hidden invitations in the results.\n\n- **timezone**: the timezone used in the response. by default, uses the n8n timezone.\n\n- **updated min**: the lower bounds for an event's last modification time (as an [rfc 3339 timestamp](https://datatracker.ietf.org/doc/html/rfc3339))\n\nrefer to the [events: list | google calendar](https://developers.google.com/calendar/api/v3/reference/events/list) api documentation for more information.\n\n## update\n\nuse this operation to update an event in a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n\n- **resource**: select **event**.\n\n- **operation**: select **update**.\n\n- **calendar**: choose a calendar you want to add an event to. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n\n- **event id**: the id of the event to update.\n\n- **modify**: for recurring events, choose whether to update the recurring event or a specific instance of the recurring event.\n\n- **use default reminders**: whether to enable default reminders for the event according to the calendar configuration.\n\n- **update fields**: the fields of the event to update:\n\n  - **all day**: whether the event is all day or not.\n  - **attendees**: attendees to invite to the event. you can choose to either add attendees or replace the existing attendee list.\n  - **color name or id**: the color of the event. choose from the list or specify the id using an expression.\n  - **description**: a description for the event.\n  - **end**: the end time of the event.\n  - **guests can invite others**: whether attendees other than the organizer can invite others to the event.\n  - **guests can modify**: whether attendees other than the organizer can make changes to the event.\n  - **guests can see other guests**: whether attendees other than the organizer can see who the event's attendees are.\n  - **id**: opaque identifier of the event.\n  - **location**: geographic location of the event as free-form text.\n  - **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n  - **repeat frequency**: the repetition interval for recurring events.\n  - **repeat how many times?**: the number of instances to create for recurring events.\n  - **repeat until**: the date at which recurring events should stop.\n  - **rrule**: recurrence rule. when set, ignores the repeat frequency, repeat how many times, and repeat until parameters.\n  - **send updates**: whether to send notifications about the creation of the new event.\n  - **show me as**: whether the event blocks time on the calendar.\n  - **start**: the start time of the event.\n  - **summary**: the title of the event.\n  - **visibility**: the visibility of the event:\n    - **confidential**: the event is private. ",
-        "importantTerms": [
-          "event",
-          "calendar",
-          "google",
-          "attendees",
-          "events",
-          "select",
-          "from",
-          "whether",
-          "time",
-          "list",
-          "recurring",
-          "this",
-          "choose",
-          "default",
-          "more",
-          "repeat",
-          "than",
-          "number",
-          "return",
-          "create",
-          "update",
-          "operation",
-          "enter",
-          "credentials",
-          "delete",
-          "guests",
-          "other",
-          "response",
-          "parameters",
-          "with",
-          "title",
-          "uses",
-          "include",
-          "specified",
-          "https",
-          "fields",
-          "these",
-          "refer",
-          "information",
-          "existing",
-          "expression",
-          "invite",
-          "organizer",
-          "only",
-          "many",
-          "date",
-          "send",
-          "developers",
-          "documentation",
-          "timezone"
-        ]
-      }
-    },
-    {
-      "id": "page-0504",
       "title": "Google Drive",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googledrive/index.md",
@@ -38753,7 +38531,7 @@
       }
     },
     {
-      "id": "page-0505",
+      "id": "page-0504",
       "title": "Common issues",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/common-issues/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googledrive/common-issues/index.md",
@@ -38839,7 +38617,7 @@
       }
     },
     {
-      "id": "page-0506",
+      "id": "page-0505",
       "title": "File and folder operations",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/file-folder-operations/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googledrive/file-folder-operations/index.md",
@@ -38919,7 +38697,7 @@
       }
     },
     {
-      "id": "page-0507",
+      "id": "page-0506",
       "title": "File operations",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/file-operations/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googledrive/file-operations/index.md",
@@ -39020,6 +38798,102 @@
         ]
       }
     },
+    {
+      "id": "page-0507",
+      "title": "Event operations",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/event-operations/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/event-operations/index.md",
+      "category": "integrations",
+      "subcategory": "app-nodes",
+      "nodeName": "googlecalendar",
+      "nodeType": "n8n-nodes-base.googlecalendar",
+      "content": {
+        "markdown": "# Google Calendar Event operations\n\nUse these operations to create, delete, get, and update events in Google Calendar. Refer to [Google Calendar](../) for more information on the Google Calendar node itself.\n\n## Create\n\nUse this operation to add an event to a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Create**.\n- **Calendar**: Choose a calendar you want to add an event to. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Start Time**: The start time for the event. By default, uses an expression evaluating to the current time (`{{ $now }}`).\n- **End Time**: The end time for the event. By default, this uses an expression evaluating to an hour from now (`{{ $now.plus(1, 'hour') }}`).\n- **Use Default Reminders**: Whether to enable default reminders for the event according to the calendar configuration.\n\n### Options\n\n- **All Day**: Whether the event is all day or not.\n\n- **Attendees**: Attendees to invite to the event.\n\n- **Color Name or ID**: The color of the event. Choose from the list or specify the ID using an expression.\n\n- **Conference Data**: Creates a conference link (Hangouts, Meet, etc.) and attaches it to the event.\n\n- **Description**: A description for the event.\n\n- **Guests Can Invite Others**: Whether attendees other than the organizer can invite others to the event.\n\n- **Guests Can Modify**: Whether attendees other than the organizer can modify the event.\n\n- **Guests Can See Other Guests**: Whether attendees other than the organizer can see who the event's attendees are.\n\n- **ID**: Opaque identifier of the event.\n\n- **Location**: Geographic location of the event as free-form text.\n\n- **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n\n- **Repeat Frequency**: The repetition interval for recurring events.\n\n- **Repeat How Many Times?**: The number of instances to create for recurring events.\n\n- **Repeat Until**: The date at which recurring events should stop.\n\n- **RRULE**: Recurrence rule. When set, ignores the Repeat Frequency, Repeat How Many Times, and Repeat Until parameters.\n\n- **Send Updates**: Whether to send notifications about the creation of the new event.\n\n- **Show Me As**: Whether the event blocks time on the calendar.\n\n- **Summary**: The title of the event.\n\nRefer to the [Events: insert | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/insert) API documentation for more information.\n\n## Delete\n\nUse this operation to delete an event from a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Delete**.\n- **Calendar**: Choose a calendar you want to delete an event from. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Event ID**: The ID of the event to delete.\n\n### Options\n\n- **Send Updates**: Whether to send notifications about the deletion of the event.\n\nRefer to the [Events: delete | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/delete) API documentation for more information.\n\n## Get\n\nUse this operation to retrieve an event from a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Get**.\n- **Calendar**: Choose a calendar you want to get an event from. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Event ID**: The ID of the event to get.\n\n### Options\n\n- **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n- **Return Next Instance of Recurrent Event**: Whether to return the next instance of a recurring event instead of the event itself.\n- **Timezone**: The timezone used in the response. By default, uses the n8n timezone.\n\nRefer to the [Events: get | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/get) API documentation for more information.\n\n## Get Many\n\nUse this operation to retrieve more than one event from a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n- **Resource**: Select **Event**.\n- **Operation**: Select **Get Many**.\n- **Calendar**: Choose a calendar you want to get an event from. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n- **Return All**: Whether to return all results or only up to a given limit.\n- **Limit**: (When \"Return All\" isn't selected) The maximum number of results to return.\n- **After**: Retrieve events that occur after this time. At least part of the event must be after this time. By default, this uses an expression evaluating to the current time (`{{ $now }}`). Switch the field to \"fixed\" to select a date from a date widget.\n- **Before**: Retrieve events that occur before this time. At least part of the event must be before this time. By default, this uses an expression evaluating to the current time plus a week (`{{ $now.plus({ week: 1 }) }}`). Switch the field to \"fixed\" to select a date from a date widget.\n\n### Options\n\n- **Fields**: Specify the fields to return. By default, returns a set of commonly used fields predefined by Google. Use \"\\*\" to return all fields. You can find out more in [Google Calendar's documentation on working with partial resources](https://developers.google.com/calendar/api/guides/performance#partial).\n\n- **iCalUID**: Specifies an event ID (in the iCalendar format) to include in the response.\n\n- **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n\n- **Order By**: The order to use for the events in the response.\n\n- **Query**: Free text search terms to find events that match. This searches all fields except for extended properties.\n\n- **Recurring Event Handling**: What to do for recurring events:\n\n  - **All Occurrences**: Return all instances of the recurring event for the specified time range.\n  - **First Occurrence**: Return the first event of a recurring event within the specified time range.\n  - **Next Occurrence**: Return the next instance of a recurring event within the specified time range.\n\n- **Show Deleted**: Whether to include deleted events (with status equal to \"cancelled\") in the results.\n\n- **Show Hidden Invitations**: Whether to include hidden invitations in the results.\n\n- **Timezone**: The timezone used in the response. By default, uses the n8n timezone.\n\n- **Updated Min**: The lower bounds for an event's last modification time (as an [RFC 3339 timestamp](https://datatracker.ietf.org/doc/html/rfc3339))\n\nRefer to the [Events: list | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/list) API documentation for more information.\n\n## Update\n\nUse this operation to update an event in a Google Calendar.\n\nEnter these parameters:\n\n- **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/).\n\n- **Resource**: Select **Event**.\n\n- **Operation**: Select **Update**.\n\n- **Calendar**: Choose a calendar you want to add an event to. Select **From list** to choose the title from the dropdown list or **By ID** to enter a calendar ID.\n\n- **Event ID**: The ID of the event to update.\n\n- **Modify**: For recurring events, choose whether to update the recurring event or a specific instance of the recurring event.\n\n- **Use Default Reminders**: Whether to enable default reminders for the event according to the calendar configuration.\n\n- **Update Fields**: The fields of the event to update:\n\n  - **All Day**: Whether the event is all day or not.\n  - **Attendees**: Attendees to invite to the event. You can choose to either add attendees or replace the existing attendee list.\n  - **Color Name or ID**: The color of the event. Choose from the list or specify the ID using an expression.\n  - **Description**: A description for the event.\n  - **End**: The end time of the event.\n  - **Guests Can Invite Others**: Whether attendees other than the organizer can invite others to the event.\n  - **Guests Can Modify**: Whether attendees other than the organizer can make changes to the event.\n  - **Guests Can See Other Guests**: Whether attendees other than the organizer can see who the event's attendees are.\n  - **ID**: Opaque identifier of the event.\n  - **Location**: Geographic location of the event as free-form text.\n  - **Max Attendees**: The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only returns the participant.\n  - **Repeat Frequency**: The repetition interval for recurring events.\n  - **Repeat How Many Times?**: The number of instances to create for recurring events.\n  - **Repeat Until**: The date at which recurring events should stop.\n  - **RRULE**: Recurrence rule. When set, ignores the Repeat Frequency, Repeat How Many Times, and Repeat Until parameters.\n  - **Send Updates**: Whether to send notifications about the creation of the new event.\n  - **Show Me As**: Whether the event blocks time on the calendar.\n  - **Start**: The start time of the event.\n  - **Summary**: The title of the event.\n  - **Visibility**: The visibility of the event:\n    - **Confidential**: The event is private. This value is provided for compatibility.\n    - **Default**: Uses the default visibility for events on the calendar.\n    - **Public**: The event is public and the event details are visible to all readers of the calendar.\n    - **Private**: The event is private and only event attendees may view event details.\n\nRefer to the [Events: update | Google Calendar](https://developers.google.com/calendar/api/v3/reference/events/update) API documentation for more information.\n",
+        "excerpt": "# Google Calendar Event operations  Use these operations to create, delete, get, and update events in Google Calendar. Refer to [Google Calendar](../) for more information on the Google Calendar node itself.  ## Create  Use this operation to add an event to a Google Calendar.  Enter these parameters:  - **Credential to connect with**: Create or select an existing [Google Calendar credentials](../../../credentials/google/). - **Resource**: Select **Event**. - **Operation**: Select **Create**. - *...",
+        "sections": [
+          {
+            "title": "Google Calendar Event operations",
+            "level": 1,
+            "content": "Use these operations to create, delete, get, and update events in Google Calendar. Refer to [Google Calendar](../) for more information on the Google Calendar node itself."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "event",
+          "operations",
+          "google",
+          "calendar",
+          "create",
+          "options",
+          "delete",
+          "many",
+          "update"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "intermediate",
+        "readingTime": "8 min",
+        "contentLength": 10453,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "event operations # google calendar event operations\n\nuse these operations to create, delete, get, and update events in google calendar. refer to [google calendar](../) for more information on the google calendar node itself.\n\n## create\n\nuse this operation to add an event to a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **create**.\n- **calendar**: choose a calendar you want to add an event to. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **start time**: the start time for the event. by default, uses an expression evaluating to the current time (`{{ $now }}`).\n- **end time**: the end time for the event. by default, this uses an expression evaluating to an hour from now (`{{ $now.plus(1, 'hour') }}`).\n- **use default reminders**: whether to enable default reminders for the event according to the calendar configuration.\n\n### options\n\n- **all day**: whether the event is all day or not.\n\n- **attendees**: attendees to invite to the event.\n\n- **color name or id**: the color of the event. choose from the list or specify the id using an expression.\n\n- **conference data**: creates a conference link (hangouts, meet, etc.) and attaches it to the event.\n\n- **description**: a description for the event.\n\n- **guests can invite others**: whether attendees other than the organizer can invite others to the event.\n\n- **guests can modify**: whether attendees other than the organizer can modify the event.\n\n- **guests can see other guests**: whether attendees other than the organizer can see who the event's attendees are.\n\n- **id**: opaque identifier of the event.\n\n- **location**: geographic location of the event as free-form text.\n\n- **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n\n- **repeat frequency**: the repetition interval for recurring events.\n\n- **repeat how many times?**: the number of instances to create for recurring events.\n\n- **repeat until**: the date at which recurring events should stop.\n\n- **rrule**: recurrence rule. when set, ignores the repeat frequency, repeat how many times, and repeat until parameters.\n\n- **send updates**: whether to send notifications about the creation of the new event.\n\n- **show me as**: whether the event blocks time on the calendar.\n\n- **summary**: the title of the event.\n\nrefer to the [events: insert | google calendar](https://developers.google.com/calendar/api/v3/reference/events/insert) api documentation for more information.\n\n## delete\n\nuse this operation to delete an event from a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **delete**.\n- **calendar**: choose a calendar you want to delete an event from. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **event id**: the id of the event to delete.\n\n### options\n\n- **send updates**: whether to send notifications about the deletion of the event.\n\nrefer to the [events: delete | google calendar](https://developers.google.com/calendar/api/v3/reference/events/delete) api documentation for more information.\n\n## get\n\nuse this operation to retrieve an event from a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **get**.\n- **calendar**: choose a calendar you want to get an event from. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **event id**: the id of the event to get.\n\n### options\n\n- **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n- **return next instance of recurrent event**: whether to return the next instance of a recurring event instead of the event itself.\n- **timezone**: the timezone used in the response. by default, uses the n8n timezone.\n\nrefer to the [events: get | google calendar](https://developers.google.com/calendar/api/v3/reference/events/get) api documentation for more information.\n\n## get many\n\nuse this operation to retrieve more than one event from a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n- **resource**: select **event**.\n- **operation**: select **get many**.\n- **calendar**: choose a calendar you want to get an event from. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n- **return all**: whether to return all results or only up to a given limit.\n- **limit**: (when \"return all\" isn't selected) the maximum number of results to return.\n- **after**: retrieve events that occur after this time. at least part of the event must be after this time. by default, this uses an expression evaluating to the current time (`{{ $now }}`). switch the field to \"fixed\" to select a date from a date widget.\n- **before**: retrieve events that occur before this time. at least part of the event must be before this time. by default, this uses an expression evaluating to the current time plus a week (`{{ $now.plus({ week: 1 }) }}`). switch the field to \"fixed\" to select a date from a date widget.\n\n### options\n\n- **fields**: specify the fields to return. by default, returns a set of commonly used fields predefined by google. use \"\\*\" to return all fields. you can find out more in [google calendar's documentation on working with partial resources](https://developers.google.com/calendar/api/guides/performance#partial).\n\n- **icaluid**: specifies an event id (in the icalendar format) to include in the response.\n\n- **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n\n- **order by**: the order to use for the events in the response.\n\n- **query**: free text search terms to find events that match. this searches all fields except for extended properties.\n\n- **recurring event handling**: what to do for recurring events:\n\n  - **all occurrences**: return all instances of the recurring event for the specified time range.\n  - **first occurrence**: return the first event of a recurring event within the specified time range.\n  - **next occurrence**: return the next instance of a recurring event within the specified time range.\n\n- **show deleted**: whether to include deleted events (with status equal to \"cancelled\") in the results.\n\n- **show hidden invitations**: whether to include hidden invitations in the results.\n\n- **timezone**: the timezone used in the response. by default, uses the n8n timezone.\n\n- **updated min**: the lower bounds for an event's last modification time (as an [rfc 3339 timestamp](https://datatracker.ietf.org/doc/html/rfc3339))\n\nrefer to the [events: list | google calendar](https://developers.google.com/calendar/api/v3/reference/events/list) api documentation for more information.\n\n## update\n\nuse this operation to update an event in a google calendar.\n\nenter these parameters:\n\n- **credential to connect with**: create or select an existing [google calendar credentials](../../../credentials/google/).\n\n- **resource**: select **event**.\n\n- **operation**: select **update**.\n\n- **calendar**: choose a calendar you want to add an event to. select **from list** to choose the title from the dropdown list or **by id** to enter a calendar id.\n\n- **event id**: the id of the event to update.\n\n- **modify**: for recurring events, choose whether to update the recurring event or a specific instance of the recurring event.\n\n- **use default reminders**: whether to enable default reminders for the event according to the calendar configuration.\n\n- **update fields**: the fields of the event to update:\n\n  - **all day**: whether the event is all day or not.\n  - **attendees**: attendees to invite to the event. you can choose to either add attendees or replace the existing attendee list.\n  - **color name or id**: the color of the event. choose from the list or specify the id using an expression.\n  - **description**: a description for the event.\n  - **end**: the end time of the event.\n  - **guests can invite others**: whether attendees other than the organizer can invite others to the event.\n  - **guests can modify**: whether attendees other than the organizer can make changes to the event.\n  - **guests can see other guests**: whether attendees other than the organizer can see who the event's attendees are.\n  - **id**: opaque identifier of the event.\n  - **location**: geographic location of the event as free-form text.\n  - **max attendees**: the maximum number of attendees to include in the response. if there are more than the specified number of attendees, only returns the participant.\n  - **repeat frequency**: the repetition interval for recurring events.\n  - **repeat how many times?**: the number of instances to create for recurring events.\n  - **repeat until**: the date at which recurring events should stop.\n  - **rrule**: recurrence rule. when set, ignores the repeat frequency, repeat how many times, and repeat until parameters.\n  - **send updates**: whether to send notifications about the creation of the new event.\n  - **show me as**: whether the event blocks time on the calendar.\n  - **start**: the start time of the event.\n  - **summary**: the title of the event.\n  - **visibility**: the visibility of the event:\n    - **confidential**: the event is private. ",
+        "importantTerms": [
+          "event",
+          "calendar",
+          "google",
+          "attendees",
+          "events",
+          "select",
+          "from",
+          "whether",
+          "time",
+          "list",
+          "recurring",
+          "this",
+          "choose",
+          "default",
+          "more",
+          "repeat",
+          "than",
+          "number",
+          "return",
+          "create",
+          "update",
+          "operation",
+          "enter",
+          "credentials",
+          "delete",
+          "guests",
+          "other",
+          "response",
+          "parameters",
+          "with",
+          "title",
+          "uses",
+          "include",
+          "specified",
+          "https",
+          "fields",
+          "these",
+          "refer",
+          "information",
+          "existing",
+          "expression",
+          "invite",
+          "organizer",
+          "only",
+          "many",
+          "date",
+          "send",
+          "developers",
+          "documentation",
+          "timezone"
+        ]
+      }
+    },
     {
       "id": "page-0508",
       "title": "Folder operations",
@@ -47550,6 +47424,69 @@
     },
     {
       "id": "page-0604",
+      "title": "Postgres Chat Memory",
+      "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/index.md",
+      "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/index.md",
+      "category": "cluster-nodes",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Postgres Chat Memory node\n\nUse the Postgres Chat Memory node to use Postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.\n\nOn this page, you'll find a list of operations the Postgres Chat Memory node supports, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/postgres/).\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## Node parameters\n\n- **Session Key**: Enter the key to use to store the memory in the workflow data.\n- **Table Name**: Enter the name of the table to store the chat history in. The system will create the table if doesn't exist.\n- **Context Window Length**: Enter the number of previous interactions to consider for context.\n\n## Related resources\n\nRefer to [LangChain's Postgres Chat Message History documentation](https://js.langchain.com/docs/integrations/memory/postgres) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n\n## Single memory instance\n\nIf you add more than one Postgres Chat Memory node to your workflow, all nodes access the same memory instance by default. Be careful when doing destructive actions that override existing memory contents, such as the override all messages operation in the [Chat Memory Manager](../n8n-nodes-langchain.memorymanager/) node. If you want more than one memory instance in your workflow, set different session IDs in different memory nodes.\n",
+        "excerpt": "# Postgres Chat Memory node  Use the Postgres Chat Memory node to use Postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.  On this page, you'll find a list of operations the Postgres Chat Memory node supports, and links to more resources.  Credentials  You can find authentication information for this node [here](../../../credentials/postgres/).  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items us...",
+        "sections": [
+          {
+            "title": "Postgres Chat Memory node",
+            "level": 1,
+            "content": "Use the Postgres Chat Memory node to use Postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.\n\nOn this page, you'll find a list of operations the Postgres Chat Memory node supports, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/postgres/).\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to t"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "postgres",
+          "chat",
+          "memory",
+          "node",
+          "parameters",
+          "related",
+          "resources",
+          "single",
+          "instance"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 2094,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "postgres chat memory # postgres chat memory node\n\nuse the postgres chat memory node to use postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.\n\non this page, you'll find a list of operations the postgres chat memory node supports, and links to more resources.\n\ncredentials\n\nyou can find authentication information for this node [here](../../../credentials/postgres/).\n\nparameter resolution in sub-nodes\n\nsub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nmost nodes, including root nodes, take any number of items as input, process these items, and output the results. you can use expressions to refer to input items, and the node resolves the expression for each item in turn. for example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nin sub-nodes, the expression always resolves to the first item. for example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## node parameters\n\n- **session key**: enter the key to use to store the memory in the workflow data.\n- **table name**: enter the name of the table to store the chat history in. the system will create the table if doesn't exist.\n- **context window length**: enter the number of previous interactions to consider for context.\n\n## related resources\n\nrefer to [langchain's postgres chat message history documentation](https://js.langchain.com/docs/integrations/memory/postgres) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n\n## single memory instance\n\nif you add more than one postgres chat memory node to your workflow, all nodes access the same memory instance by default. be careful when doing destructive actions that override existing memory contents, such as the override all messages operation in the [chat memory manager](../n8n-nodes-langchain.memorymanager/) node. if you want more than one memory instance in your workflow, set different session ids in different memory nodes.\n postgres chat memory node",
+        "importantTerms": [
+          "memory",
+          "postgres",
+          "chat",
+          "node",
+          "nodes",
+          "name",
+          "expression",
+          "more",
+          "items",
+          "input",
+          "resolves",
+          "history",
+          "enter",
+          "workflow",
+          "table",
+          "langchain",
+          "instance"
+        ]
+      }
+    },
+    {
+      "id": "page-0605",
       "title": "Redis Chat Memory",
       "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryredischat/index.md",
       "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryredischat/index.md",
@@ -47624,7 +47561,7 @@
       }
     },
     {
-      "id": "page-0605",
+      "id": "page-0606",
       "title": "Xata",
       "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryxata/index.md",
       "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryxata/index.md",
@@ -47695,7 +47632,7 @@
       }
     },
     {
-      "id": "page-0606",
+      "id": "page-0607",
       "title": "Zep",
       "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryzep/index.md",
       "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryzep/index.md",
@@ -47755,69 +47692,6 @@
         ]
       }
     },
-    {
-      "id": "page-0607",
-      "title": "Postgres Chat Memory",
-      "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/index.md",
-      "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/index.md",
-      "category": "cluster-nodes",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Postgres Chat Memory node\n\nUse the Postgres Chat Memory node to use Postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.\n\nOn this page, you'll find a list of operations the Postgres Chat Memory node supports, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/postgres/).\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## Node parameters\n\n- **Session Key**: Enter the key to use to store the memory in the workflow data.\n- **Table Name**: Enter the name of the table to store the chat history in. The system will create the table if doesn't exist.\n- **Context Window Length**: Enter the number of previous interactions to consider for context.\n\n## Related resources\n\nRefer to [LangChain's Postgres Chat Message History documentation](https://js.langchain.com/docs/integrations/memory/postgres) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n\n## Single memory instance\n\nIf you add more than one Postgres Chat Memory node to your workflow, all nodes access the same memory instance by default. Be careful when doing destructive actions that override existing memory contents, such as the override all messages operation in the [Chat Memory Manager](../n8n-nodes-langchain.memorymanager/) node. If you want more than one memory instance in your workflow, set different session IDs in different memory nodes.\n",
-        "excerpt": "# Postgres Chat Memory node  Use the Postgres Chat Memory node to use Postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.  On this page, you'll find a list of operations the Postgres Chat Memory node supports, and links to more resources.  Credentials  You can find authentication information for this node [here](../../../credentials/postgres/).  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items us...",
-        "sections": [
-          {
-            "title": "Postgres Chat Memory node",
-            "level": 1,
-            "content": "Use the Postgres Chat Memory node to use Postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.\n\nOn this page, you'll find a list of operations the Postgres Chat Memory node supports, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/postgres/).\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to t"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "postgres",
-          "chat",
-          "memory",
-          "node",
-          "parameters",
-          "related",
-          "resources",
-          "single",
-          "instance"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 2094,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "postgres chat memory # postgres chat memory node\n\nuse the postgres chat memory node to use postgres as a [memory](../../../../../glossary/#ai-memory) server for storing chat history.\n\non this page, you'll find a list of operations the postgres chat memory node supports, and links to more resources.\n\ncredentials\n\nyou can find authentication information for this node [here](../../../credentials/postgres/).\n\nparameter resolution in sub-nodes\n\nsub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nmost nodes, including root nodes, take any number of items as input, process these items, and output the results. you can use expressions to refer to input items, and the node resolves the expression for each item in turn. for example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nin sub-nodes, the expression always resolves to the first item. for example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## node parameters\n\n- **session key**: enter the key to use to store the memory in the workflow data.\n- **table name**: enter the name of the table to store the chat history in. the system will create the table if doesn't exist.\n- **context window length**: enter the number of previous interactions to consider for context.\n\n## related resources\n\nrefer to [langchain's postgres chat message history documentation](https://js.langchain.com/docs/integrations/memory/postgres) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n\n## single memory instance\n\nif you add more than one postgres chat memory node to your workflow, all nodes access the same memory instance by default. be careful when doing destructive actions that override existing memory contents, such as the override all messages operation in the [chat memory manager](../n8n-nodes-langchain.memorymanager/) node. if you want more than one memory instance in your workflow, set different session ids in different memory nodes.\n postgres chat memory node",
-        "importantTerms": [
-          "memory",
-          "postgres",
-          "chat",
-          "node",
-          "nodes",
-          "name",
-          "expression",
-          "more",
-          "items",
-          "input",
-          "resolves",
-          "history",
-          "enter",
-          "workflow",
-          "table",
-          "langchain",
-          "instance"
-        ]
-      }
-    },
     {
       "id": "page-0608",
       "title": "Model Selector",
@@ -48228,32 +48102,31 @@
     },
     {
       "id": "page-0614",
-      "title": "Workflow Retriever",
-      "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrieverworkflow/index.md",
-      "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrieverworkflow/index.md",
+      "title": "Vector Store Retriever",
+      "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrievervectorstore/index.md",
+      "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrievervectorstore/index.md",
       "category": "cluster-nodes",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Workflow Retriever node\n\nUse the Workflow Retriever node to retrieve data from an n8n workflow for use in a Retrieval QA Chain or another Retriever node.\n\nOn this page, you'll find the node parameters for the Workflow Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## Node parameters\n\n### Source\n\nTell n8n which workflow to call. You can choose either:\n\n- **Database** and enter a workflow ID.\n- **Parameter** and copy in a complete [workflow JSON](../../../../../workflows/export-import/).\n\n### Workflow values\n\nSet values to pass to the workflow you're calling.\n\nThese values appear in the output data of the trigger node in the workflow you call. You can access these values in expressions in the workflow. For example, if you have:\n\n- **Workflow Values** with a **Name** of `myCustomValue`\n- A workflow with an Execute Sub-workflow Trigger node as its trigger\n\nThe expression to access the value of `myCustomValue` is `{{ $('Execute Sub-workflow Trigger').item.json.myCustomValue }}`.\n\n## Templates and examples\n\n**AI Crew to Automate Fundamental Stock Analysis - Q&A Workflow**\n\nby Derek Cheung\n\n[View template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**Build a PDF Document RAG System with Mistral OCR, Qdrant and Gemini AI**\n\nby Davide Boizza\n\n[View template details](https://n8n.io/workflows/4400-build-a-pdf-document-rag-system-with-mistral-ocr-qdrant-and-gemini-ai/)\n\n**AI: Ask questions about any data source (using the n8n workflow retriever)**\n\nby n8n Team\n\n[View template details](https://n8n.io/workflows/1958-ai-ask-questions-about-any-data-source-using-the-n8n-workflow-retriever/)\n\n[Browse Workflow Retriever integration templates](https://n8n.io/integrations/workflow-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChain's general retriever documentation](https://js.langchain.com/docs/concepts/retrievers/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
-        "excerpt": "# Workflow Retriever node  Use the Workflow Retriever node to retrieve data from an n8n workflow for use in a Retrieval QA Chain or another Retriever node.  On this page, you'll find the node parameters for the Workflow Retriever node, and links to more resources.  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items using an expression.  Most nodes, including root nodes, take any number of items as input, process these items, and output t...",
+        "markdown": "# Vector Store Retriever node\n\nUse the Vector Store Retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).\n\nOn this page, you'll find the node parameters for the Vector Store Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## Node parameters\n\n- **Limit**: Enter the maximum number of results to return.\n\n## Templates and examples\n\n**Ask questions about a PDF using AI**\n\nby David Roberts\n\n[View template details](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/)\n\n**AI Crew to Automate Fundamental Stock Analysis - Q&A Workflow**\n\nby Derek Cheung\n\n[View template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**Advanced AI Demo (Presented at AI Developers #14 meetup)**\n\nby Max Tkacz\n\n[View template details](https://n8n.io/workflows/2358-advanced-ai-demo-presented-at-ai-developers-14-meetup/)\n\n[Browse Vector Store Retriever integration templates](https://n8n.io/integrations/vector-store-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChain's vector store retriever documentation](https://js.langchain.com/docs/how_to/vectorstore_retriever/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "excerpt": "# Vector Store Retriever node  Use the Vector Store Retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).  On this page, you'll find the node parameters for the Vector Store Retriever node, and links to more resources.  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items using an expression.  Most nodes, including root nodes, take any number of items as input, process these items, and output...",
         "sections": [
           {
-            "title": "Workflow Retriever node",
+            "title": "Vector Store Retriever node",
             "level": 1,
-            "content": "Use the Workflow Retriever node to retrieve data from an n8n workflow for use in a Retrieval QA Chain or another Retriever node.\n\nOn this page, you'll find the node parameters for the Workflow Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name."
+            "content": "Use the Vector Store Retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).\n\nOn this page, you'll find the node parameters for the Vector Store Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "workflow",
+          "vector",
+          "store",
           "retriever",
           "node",
           "parameters",
-          "source",
-          "values",
           "templates",
           "examples",
           "related",
@@ -48264,69 +48137,62 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "2 min",
-        "contentLength": 2714,
+        "contentLength": 1988,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "workflow retriever # workflow retriever node\n\nuse the workflow retriever node to retrieve data from an n8n workflow for use in a retrieval qa chain or another retriever node.\n\non this page, you'll find the node parameters for the workflow retriever node, and links to more resources.\n\nparameter resolution in sub-nodes\n\nsub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nmost nodes, including root nodes, take any number of items as input, process these items, and output the results. you can use expressions to refer to input items, and the node resolves the expression for each item in turn. for example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nin sub-nodes, the expression always resolves to the first item. for example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## node parameters\n\n### source\n\ntell n8n which workflow to call. you can choose either:\n\n- **database** and enter a workflow id.\n- **parameter** and copy in a complete [workflow json](../../../../../workflows/export-import/).\n\n### workflow values\n\nset values to pass to the workflow you're calling.\n\nthese values appear in the output data of the trigger node in the workflow you call. you can access these values in expressions in the workflow. for example, if you have:\n\n- **workflow values** with a **name** of `mycustomvalue`\n- a workflow with an execute sub-workflow trigger node as its trigger\n\nthe expression to access the value of `mycustomvalue` is `{{ $('execute sub-workflow trigger').item.json.mycustomvalue }}`.\n\n## templates and examples\n\n**ai crew to automate fundamental stock analysis - q&a workflow**\n\nby derek cheung\n\n[view template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**build a pdf document rag system with mistral ocr, qdrant and gemini ai**\n\nby davide boizza\n\n[view template details](https://n8n.io/workflows/4400-build-a-pdf-document-rag-system-with-mistral-ocr-qdrant-and-gemini-ai/)\n\n**ai: ask questions about any data source (using the n8n workflow retriever)**\n\nby n8n team\n\n[view template details](https://n8n.io/workflows/1958-ai-ask-questions-about-any-data-source-using-the-n8n-workflow-retriever/)\n\n[browse workflow retriever integration templates](https://n8n.io/integrations/workflow-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nrefer to [langchain's general retriever documentation](https://js.langchain.com/docs/concepts/retrievers/) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n workflow retriever node",
+        "fullText": "vector store retriever # vector store retriever node\n\nuse the vector store retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).\n\non this page, you'll find the node parameters for the vector store retriever node, and links to more resources.\n\nparameter resolution in sub-nodes\n\nsub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nmost nodes, including root nodes, take any number of items as input, process these items, and output the results. you can use expressions to refer to input items, and the node resolves the expression for each item in turn. for example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nin sub-nodes, the expression always resolves to the first item. for example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## node parameters\n\n- **limit**: enter the maximum number of results to return.\n\n## templates and examples\n\n**ask questions about a pdf using ai**\n\nby david roberts\n\n[view template details](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/)\n\n**ai crew to automate fundamental stock analysis - q&a workflow**\n\nby derek cheung\n\n[view template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**advanced ai demo (presented at ai developers #14 meetup)**\n\nby max tkacz\n\n[view template details](https://n8n.io/workflows/2358-advanced-ai-demo-presented-at-ai-developers-14-meetup/)\n\n[browse vector store retriever integration templates](https://n8n.io/integrations/vector-store-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nrefer to [langchain's vector store retriever documentation](https://js.langchain.com/docs/how_to/vectorstore_retriever/) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n vector store retriever node",
         "importantTerms": [
-          "workflow",
+          "vector",
+          "store",
           "retriever",
           "node",
-          "name",
-          "values",
           "nodes",
-          "expression",
+          "name",
           "https",
-          "workflows",
-          "data",
+          "expression",
           "items",
           "input",
           "resolves",
-          "json",
-          "trigger",
-          "with",
           "view",
+          "workflows",
+          "advanced",
           "using",
-          "these",
-          "item",
-          "example",
-          "source",
-          "mycustomvalue",
           "templates",
+          "about",
           "template",
-          "details",
-          "about"
+          "details"
         ]
       }
     },
     {
       "id": "page-0615",
-      "title": "Vector Store Retriever",
-      "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrievervectorstore/index.md",
-      "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrievervectorstore/index.md",
+      "title": "Workflow Retriever",
+      "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrieverworkflow/index.md",
+      "urlPath": "integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.retrieverworkflow/index.md",
       "category": "cluster-nodes",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Vector Store Retriever node\n\nUse the Vector Store Retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).\n\nOn this page, you'll find the node parameters for the Vector Store Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## Node parameters\n\n- **Limit**: Enter the maximum number of results to return.\n\n## Templates and examples\n\n**Ask questions about a PDF using AI**\n\nby David Roberts\n\n[View template details](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/)\n\n**AI Crew to Automate Fundamental Stock Analysis - Q&A Workflow**\n\nby Derek Cheung\n\n[View template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**Advanced AI Demo (Presented at AI Developers #14 meetup)**\n\nby Max Tkacz\n\n[View template details](https://n8n.io/workflows/2358-advanced-ai-demo-presented-at-ai-developers-14-meetup/)\n\n[Browse Vector Store Retriever integration templates](https://n8n.io/integrations/vector-store-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChain's vector store retriever documentation](https://js.langchain.com/docs/how_to/vectorstore_retriever/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
-        "excerpt": "# Vector Store Retriever node  Use the Vector Store Retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).  On this page, you'll find the node parameters for the Vector Store Retriever node, and links to more resources.  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items using an expression.  Most nodes, including root nodes, take any number of items as input, process these items, and output...",
+        "markdown": "# Workflow Retriever node\n\nUse the Workflow Retriever node to retrieve data from an n8n workflow for use in a Retrieval QA Chain or another Retriever node.\n\nOn this page, you'll find the node parameters for the Workflow Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## Node parameters\n\n### Source\n\nTell n8n which workflow to call. You can choose either:\n\n- **Database** and enter a workflow ID.\n- **Parameter** and copy in a complete [workflow JSON](../../../../../workflows/export-import/).\n\n### Workflow values\n\nSet values to pass to the workflow you're calling.\n\nThese values appear in the output data of the trigger node in the workflow you call. You can access these values in expressions in the workflow. For example, if you have:\n\n- **Workflow Values** with a **Name** of `myCustomValue`\n- A workflow with an Execute Sub-workflow Trigger node as its trigger\n\nThe expression to access the value of `myCustomValue` is `{{ $('Execute Sub-workflow Trigger').item.json.myCustomValue }}`.\n\n## Templates and examples\n\n**AI Crew to Automate Fundamental Stock Analysis - Q&A Workflow**\n\nby Derek Cheung\n\n[View template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**Build a PDF Document RAG System with Mistral OCR, Qdrant and Gemini AI**\n\nby Davide Boizza\n\n[View template details](https://n8n.io/workflows/4400-build-a-pdf-document-rag-system-with-mistral-ocr-qdrant-and-gemini-ai/)\n\n**AI: Ask questions about any data source (using the n8n workflow retriever)**\n\nby n8n Team\n\n[View template details](https://n8n.io/workflows/1958-ai-ask-questions-about-any-data-source-using-the-n8n-workflow-retriever/)\n\n[Browse Workflow Retriever integration templates](https://n8n.io/integrations/workflow-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChain's general retriever documentation](https://js.langchain.com/docs/concepts/retrievers/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "excerpt": "# Workflow Retriever node  Use the Workflow Retriever node to retrieve data from an n8n workflow for use in a Retrieval QA Chain or another Retriever node.  On this page, you'll find the node parameters for the Workflow Retriever node, and links to more resources.  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items using an expression.  Most nodes, including root nodes, take any number of items as input, process these items, and output t...",
         "sections": [
           {
-            "title": "Vector Store Retriever node",
+            "title": "Workflow Retriever node",
             "level": 1,
-            "content": "Use the Vector Store Retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).\n\nOn this page, you'll find the node parameters for the Vector Store Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name."
+            "content": "Use the Workflow Retriever node to retrieve data from an n8n workflow for use in a Retrieval QA Chain or another Retriever node.\n\nOn this page, you'll find the node parameters for the Workflow Retriever node, and links to more resources.\n\nParameter resolution in sub-nodes\n\nSub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nMost nodes, including root nodes, take any number of items as input, process these items, and output the results. You can use expressions to refer to input items, and the node resolves the expression for each item in turn. For example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nIn sub-nodes, the expression always resolves to the first item. For example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "vector",
-          "store",
+          "workflow",
           "retriever",
           "node",
           "parameters",
+          "source",
+          "values",
           "templates",
           "examples",
           "related",
@@ -48337,31 +48203,39 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "2 min",
-        "contentLength": 1988,
+        "contentLength": 2714,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "vector store retriever # vector store retriever node\n\nuse the vector store retriever node to retrieve documents from a [vector store](../../../../../glossary/#ai-vector-store).\n\non this page, you'll find the node parameters for the vector store retriever node, and links to more resources.\n\nparameter resolution in sub-nodes\n\nsub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nmost nodes, including root nodes, take any number of items as input, process these items, and output the results. you can use expressions to refer to input items, and the node resolves the expression for each item in turn. for example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nin sub-nodes, the expression always resolves to the first item. for example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## node parameters\n\n- **limit**: enter the maximum number of results to return.\n\n## templates and examples\n\n**ask questions about a pdf using ai**\n\nby david roberts\n\n[view template details](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/)\n\n**ai crew to automate fundamental stock analysis - q&a workflow**\n\nby derek cheung\n\n[view template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**advanced ai demo (presented at ai developers #14 meetup)**\n\nby max tkacz\n\n[view template details](https://n8n.io/workflows/2358-advanced-ai-demo-presented-at-ai-developers-14-meetup/)\n\n[browse vector store retriever integration templates](https://n8n.io/integrations/vector-store-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nrefer to [langchain's vector store retriever documentation](https://js.langchain.com/docs/how_to/vectorstore_retriever/) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n vector store retriever node",
+        "fullText": "workflow retriever # workflow retriever node\n\nuse the workflow retriever node to retrieve data from an n8n workflow for use in a retrieval qa chain or another retriever node.\n\non this page, you'll find the node parameters for the workflow retriever node, and links to more resources.\n\nparameter resolution in sub-nodes\n\nsub-nodes behave differently to other nodes when processing multiple items using an expression.\n\nmost nodes, including root nodes, take any number of items as input, process these items, and output the results. you can use expressions to refer to input items, and the node resolves the expression for each item in turn. for example, given an input of five `name` values, the expression `{{ $json.name }}` resolves to each name in turn.\n\nin sub-nodes, the expression always resolves to the first item. for example, given an input of five `name` values, the expression `{{ $json.name }}` always resolves to the first name.\n\n## node parameters\n\n### source\n\ntell n8n which workflow to call. you can choose either:\n\n- **database** and enter a workflow id.\n- **parameter** and copy in a complete [workflow json](../../../../../workflows/export-import/).\n\n### workflow values\n\nset values to pass to the workflow you're calling.\n\nthese values appear in the output data of the trigger node in the workflow you call. you can access these values in expressions in the workflow. for example, if you have:\n\n- **workflow values** with a **name** of `mycustomvalue`\n- a workflow with an execute sub-workflow trigger node as its trigger\n\nthe expression to access the value of `mycustomvalue` is `{{ $('execute sub-workflow trigger').item.json.mycustomvalue }}`.\n\n## templates and examples\n\n**ai crew to automate fundamental stock analysis - q&a workflow**\n\nby derek cheung\n\n[view template details](https://n8n.io/workflows/2183-ai-crew-to-automate-fundamental-stock-analysis-qanda-workflow/)\n\n**build a pdf document rag system with mistral ocr, qdrant and gemini ai**\n\nby davide boizza\n\n[view template details](https://n8n.io/workflows/4400-build-a-pdf-document-rag-system-with-mistral-ocr-qdrant-and-gemini-ai/)\n\n**ai: ask questions about any data source (using the n8n workflow retriever)**\n\nby n8n team\n\n[view template details](https://n8n.io/workflows/1958-ai-ask-questions-about-any-data-source-using-the-n8n-workflow-retriever/)\n\n[browse workflow retriever integration templates](https://n8n.io/integrations/workflow-retriever/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nrefer to [langchain's general retriever documentation](https://js.langchain.com/docs/concepts/retrievers/) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n workflow retriever node",
         "importantTerms": [
-          "vector",
-          "store",
+          "workflow",
           "retriever",
           "node",
-          "nodes",
           "name",
-          "https",
+          "values",
+          "nodes",
           "expression",
+          "https",
+          "workflows",
+          "data",
           "items",
           "input",
           "resolves",
+          "json",
+          "trigger",
+          "with",
           "view",
-          "workflows",
-          "advanced",
           "using",
+          "these",
+          "item",
+          "example",
+          "source",
+          "mycustomvalue",
           "templates",
-          "about",
           "template",
-          "details"
+          "details",
+          "about"
         ]
       }
     },
@@ -60145,66 +60019,6 @@
     },
     {
       "id": "page-0761",
-      "title": "Webex by Cisco credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/ciscowebex/index.md",
-      "urlPath": "integrations/builtin/credentials/ciscowebex/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Webex by Cisco credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Webex by Cisco](../../app-nodes/n8n-nodes-base.ciscowebex/)\n- [Webex by Cisco Trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)\n\n## Prerequisites\n\nCreate a [Webex by Cisco](https://www.webex.com/) account (this should automatically get you [developer account access](https://developer.webex.com)).\n\n## Supported authentication methods\n\n- OAuth2\n\n## Related resources\n\nRefer to [Webex's API documentation](https://developer.webex.com/docs/getting-started) for more information about the service.\n\n## Using OAuth2\n\nNote for n8n Cloud users\n\nYou'll only need to enter the Credentials Name and select the **Connect my account** button in the OAuth credential to connect your Webex by Cisco account to n8n.\n\nShould you need to configure OAuth2 from scratch, you'll need to create an integration to use this credential. Refer to the instructions in the [Webex Registering your Integration documentation](https://developer.webex.com/docs/integrations#registering-your-integration) to begin.\n\nn8n recommends using the following **Scopes** for your integration:\n\n- `spark:rooms_read`\n- `spark:messages_write`\n- `spark:messages_read`\n- `spark:memberships_read`\n- `spark:memberships_write`\n- `meeting:recordings_write`\n- `meeting:recordings_read`\n- `meeting:preferences_read`\n- `meeting:schedules_write`\n- `meeting:schedules_read`\n",
-        "excerpt": "# Webex by Cisco credentials  You can use these credentials to authenticate the following nodes:  - [Webex by Cisco](../../app-nodes/n8n-nodes-base.ciscowebex/) - [Webex by Cisco Trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)  ## Prerequisites  Create a [Webex by Cisco](https://www.webex.com/) account (this should automatically get you [developer account access](https://developer.webex.com)).  ## Supported authentication methods  - OAuth2  ## Related resources  Refer to [Webex's...",
-        "sections": [
-          {
-            "title": "Webex by Cisco credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Webex by Cisco](../../app-nodes/n8n-nodes-base.ciscowebex/)\n- [Webex by Cisco Trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "webex",
-          "cisco",
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using",
-          "oauth2"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 1435,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "webex by cisco credentials # webex by cisco credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [webex by cisco](../../app-nodes/n8n-nodes-base.ciscowebex/)\n- [webex by cisco trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)\n\n## prerequisites\n\ncreate a [webex by cisco](https://www.webex.com/) account (this should automatically get you [developer account access](https://developer.webex.com)).\n\n## supported authentication methods\n\n- oauth2\n\n## related resources\n\nrefer to [webex's api documentation](https://developer.webex.com/docs/getting-started) for more information about the service.\n\n## using oauth2\n\nnote for n8n cloud users\n\nyou'll only need to enter the credentials name and select the **connect my account** button in the oauth credential to connect your webex by cisco account to n8n.\n\nshould you need to configure oauth2 from scratch, you'll need to create an integration to use this credential. refer to the instructions in the [webex registering your integration documentation](https://developer.webex.com/docs/integrations#registering-your-integration) to begin.\n\nn8n recommends using the following **scopes** for your integration:\n\n- `spark:rooms_read`\n- `spark:messages_write`\n- `spark:messages_read`\n- `spark:memberships_read`\n- `spark:memberships_write`\n- `meeting:recordings_write`\n- `meeting:recordings_read`\n- `meeting:preferences_read`\n- `meeting:schedules_write`\n- `meeting:schedules_read`\n webex by cisco credentials",
-        "importantTerms": [
-          "webex",
-          "cisco",
-          "credentials",
-          "nodes",
-          "spark",
-          "meeting",
-          "https",
-          "account",
-          "developer",
-          "your",
-          "integration",
-          "need"
-        ]
-      }
-    },
-    {
-      "id": "page-0762",
       "title": "Clearbit credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/clearbit/index.md",
       "urlPath": "integrations/builtin/credentials/clearbit/index.md",
@@ -60254,7 +60068,7 @@
       }
     },
     {
-      "id": "page-0763",
+      "id": "page-0762",
       "title": "ClickUp credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/clickup/index.md",
       "urlPath": "integrations/builtin/credentials/clickup/index.md",
@@ -60326,7 +60140,7 @@
       }
     },
     {
-      "id": "page-0764",
+      "id": "page-0763",
       "title": "Clockify credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/clockify/index.md",
       "urlPath": "integrations/builtin/credentials/clockify/index.md",
@@ -60376,7 +60190,7 @@
       }
     },
     {
-      "id": "page-0765",
+      "id": "page-0764",
       "title": "Cloudflare credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/cloudflare/index.md",
       "urlPath": "integrations/builtin/credentials/cloudflare/index.md",
@@ -60430,6 +60244,66 @@
         ]
       }
     },
+    {
+      "id": "page-0765",
+      "title": "Webex by Cisco credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/ciscowebex/index.md",
+      "urlPath": "integrations/builtin/credentials/ciscowebex/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Webex by Cisco credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Webex by Cisco](../../app-nodes/n8n-nodes-base.ciscowebex/)\n- [Webex by Cisco Trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)\n\n## Prerequisites\n\nCreate a [Webex by Cisco](https://www.webex.com/) account (this should automatically get you [developer account access](https://developer.webex.com)).\n\n## Supported authentication methods\n\n- OAuth2\n\n## Related resources\n\nRefer to [Webex's API documentation](https://developer.webex.com/docs/getting-started) for more information about the service.\n\n## Using OAuth2\n\nNote for n8n Cloud users\n\nYou'll only need to enter the Credentials Name and select the **Connect my account** button in the OAuth credential to connect your Webex by Cisco account to n8n.\n\nShould you need to configure OAuth2 from scratch, you'll need to create an integration to use this credential. Refer to the instructions in the [Webex Registering your Integration documentation](https://developer.webex.com/docs/integrations#registering-your-integration) to begin.\n\nn8n recommends using the following **Scopes** for your integration:\n\n- `spark:rooms_read`\n- `spark:messages_write`\n- `spark:messages_read`\n- `spark:memberships_read`\n- `spark:memberships_write`\n- `meeting:recordings_write`\n- `meeting:recordings_read`\n- `meeting:preferences_read`\n- `meeting:schedules_write`\n- `meeting:schedules_read`\n",
+        "excerpt": "# Webex by Cisco credentials  You can use these credentials to authenticate the following nodes:  - [Webex by Cisco](../../app-nodes/n8n-nodes-base.ciscowebex/) - [Webex by Cisco Trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)  ## Prerequisites  Create a [Webex by Cisco](https://www.webex.com/) account (this should automatically get you [developer account access](https://developer.webex.com)).  ## Supported authentication methods  - OAuth2  ## Related resources  Refer to [Webex's...",
+        "sections": [
+          {
+            "title": "Webex by Cisco credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Webex by Cisco](../../app-nodes/n8n-nodes-base.ciscowebex/)\n- [Webex by Cisco Trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "webex",
+          "cisco",
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using",
+          "oauth2"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 1435,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "webex by cisco credentials # webex by cisco credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [webex by cisco](../../app-nodes/n8n-nodes-base.ciscowebex/)\n- [webex by cisco trigger](../../trigger-nodes/n8n-nodes-base.ciscowebextrigger/)\n\n## prerequisites\n\ncreate a [webex by cisco](https://www.webex.com/) account (this should automatically get you [developer account access](https://developer.webex.com)).\n\n## supported authentication methods\n\n- oauth2\n\n## related resources\n\nrefer to [webex's api documentation](https://developer.webex.com/docs/getting-started) for more information about the service.\n\n## using oauth2\n\nnote for n8n cloud users\n\nyou'll only need to enter the credentials name and select the **connect my account** button in the oauth credential to connect your webex by cisco account to n8n.\n\nshould you need to configure oauth2 from scratch, you'll need to create an integration to use this credential. refer to the instructions in the [webex registering your integration documentation](https://developer.webex.com/docs/integrations#registering-your-integration) to begin.\n\nn8n recommends using the following **scopes** for your integration:\n\n- `spark:rooms_read`\n- `spark:messages_write`\n- `spark:messages_read`\n- `spark:memberships_read`\n- `spark:memberships_write`\n- `meeting:recordings_write`\n- `meeting:recordings_read`\n- `meeting:preferences_read`\n- `meeting:schedules_write`\n- `meeting:schedules_read`\n webex by cisco credentials",
+        "importantTerms": [
+          "webex",
+          "cisco",
+          "credentials",
+          "nodes",
+          "spark",
+          "meeting",
+          "https",
+          "account",
+          "developer",
+          "your",
+          "integration",
+          "need"
+        ]
+      }
+    },
     {
       "id": "page-0766",
       "title": "Cockpit credentials",
@@ -61457,60 +61331,6 @@
     },
     {
       "id": "page-0784",
-      "title": "DHL credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/dhl/index.md",
-      "urlPath": "integrations/builtin/credentials/dhl/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# DHL credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [DHL](../../app-nodes/n8n-nodes-base.dhl/)\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [DHL's Developer documentation](https://support-developer.dhl.com/support/home) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need a [DHL Developer](https://developer.dhl.com/user/register) account and:\n\n- An **API Key**\n\nTo get an API key, create an app:\n\n1. In the DHL Developer portal, select the user icon to open your [User Apps](https://developer.dhl.com/user/apps).\n1. Select **+ Create App**.\n1. Enter an **App name**, like `n8n integration`.\n1. Enter a **Machine name**, like `n8n_integration`.\n1. In **SELECT APIs**, select **Shipment Tracking - Unified**. The API is added to the **Add API to app** section.\n1. In the **Add API to app** section, select the **+** next to the **Shipment Tracking - Unified** API.\n1. Select **Create App**. The **Apps** page opens, displaying the app you just created.\n1. Select the app you just created to view its details.\n1. Select **Show key** next to **API Key**.\n1. Copy the **API Key** and enter it in your n8n credential.\n\nRefer to [How to create an app?](https://support-developer.dhl.com/support/solutions/articles/47001177011-how-to-create-an-app-) for more information.\n",
-        "excerpt": "# DHL credentials  You can use these credentials to authenticate the following nodes:  - [DHL](../../app-nodes/n8n-nodes-base.dhl/)  ## Supported authentication methods  - API key  ## Related resources  Refer to [DHL's Developer documentation](https://support-developer.dhl.com/support/home) for more information about the service.  ## Using API key  To configure this credential, you'll need a [DHL Developer](https://developer.dhl.com/user/register) account and:  - An **API Key**  To get an API ke...",
-        "sections": [
-          {
-            "title": "DHL credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [DHL](../../app-nodes/n8n-nodes-base.dhl/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "credentials",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 1386,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "dhl credentials # dhl credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [dhl](../../app-nodes/n8n-nodes-base.dhl/)\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [dhl's developer documentation](https://support-developer.dhl.com/support/home) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need a [dhl developer](https://developer.dhl.com/user/register) account and:\n\n- an **api key**\n\nto get an api key, create an app:\n\n1. in the dhl developer portal, select the user icon to open your [user apps](https://developer.dhl.com/user/apps).\n1. select **+ create app**.\n1. enter an **app name**, like `n8n integration`.\n1. enter a **machine name**, like `n8n_integration`.\n1. in **select apis**, select **shipment tracking - unified**. the api is added to the **add api to app** section.\n1. in the **add api to app** section, select the **+** next to the **shipment tracking - unified** api.\n1. select **create app**. the **apps** page opens, displaying the app you just created.\n1. select the app you just created to view its details.\n1. select **show key** next to **api key**.\n1. copy the **api key** and enter it in your n8n credential.\n\nrefer to [how to create an app?](https://support-developer.dhl.com/support/solutions/articles/47001177011-how-to-create-an-app-) for more information.\n dhl credentials",
-        "importantTerms": [
-          "select",
-          "developer",
-          "create",
-          "credentials",
-          "https",
-          "support",
-          "user",
-          "nodes",
-          "apps",
-          "enter"
-        ]
-      }
-    },
-    {
-      "id": "page-0785",
       "title": "Discord credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/discord/index.md",
       "urlPath": "integrations/builtin/credentials/discord/index.md",
@@ -61610,7 +61430,7 @@
       }
     },
     {
-      "id": "page-0786",
+      "id": "page-0785",
       "title": "Discourse credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/discourse/index.md",
       "urlPath": "integrations/builtin/credentials/discourse/index.md",
@@ -61666,7 +61486,7 @@
       }
     },
     {
-      "id": "page-0787",
+      "id": "page-0786",
       "title": "Disqus credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/disqus/index.md",
       "urlPath": "integrations/builtin/credentials/disqus/index.md",
@@ -61720,6 +61540,60 @@
         ]
       }
     },
+    {
+      "id": "page-0787",
+      "title": "DHL credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/dhl/index.md",
+      "urlPath": "integrations/builtin/credentials/dhl/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# DHL credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [DHL](../../app-nodes/n8n-nodes-base.dhl/)\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [DHL's Developer documentation](https://support-developer.dhl.com/support/home) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need a [DHL Developer](https://developer.dhl.com/user/register) account and:\n\n- An **API Key**\n\nTo get an API key, create an app:\n\n1. In the DHL Developer portal, select the user icon to open your [User Apps](https://developer.dhl.com/user/apps).\n1. Select **+ Create App**.\n1. Enter an **App name**, like `n8n integration`.\n1. Enter a **Machine name**, like `n8n_integration`.\n1. In **SELECT APIs**, select **Shipment Tracking - Unified**. The API is added to the **Add API to app** section.\n1. In the **Add API to app** section, select the **+** next to the **Shipment Tracking - Unified** API.\n1. Select **Create App**. The **Apps** page opens, displaying the app you just created.\n1. Select the app you just created to view its details.\n1. Select **Show key** next to **API Key**.\n1. Copy the **API Key** and enter it in your n8n credential.\n\nRefer to [How to create an app?](https://support-developer.dhl.com/support/solutions/articles/47001177011-how-to-create-an-app-) for more information.\n",
+        "excerpt": "# DHL credentials  You can use these credentials to authenticate the following nodes:  - [DHL](../../app-nodes/n8n-nodes-base.dhl/)  ## Supported authentication methods  - API key  ## Related resources  Refer to [DHL's Developer documentation](https://support-developer.dhl.com/support/home) for more information about the service.  ## Using API key  To configure this credential, you'll need a [DHL Developer](https://developer.dhl.com/user/register) account and:  - An **API Key**  To get an API ke...",
+        "sections": [
+          {
+            "title": "DHL credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [DHL](../../app-nodes/n8n-nodes-base.dhl/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "credentials",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 1386,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "dhl credentials # dhl credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [dhl](../../app-nodes/n8n-nodes-base.dhl/)\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [dhl's developer documentation](https://support-developer.dhl.com/support/home) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need a [dhl developer](https://developer.dhl.com/user/register) account and:\n\n- an **api key**\n\nto get an api key, create an app:\n\n1. in the dhl developer portal, select the user icon to open your [user apps](https://developer.dhl.com/user/apps).\n1. select **+ create app**.\n1. enter an **app name**, like `n8n integration`.\n1. enter a **machine name**, like `n8n_integration`.\n1. in **select apis**, select **shipment tracking - unified**. the api is added to the **add api to app** section.\n1. in the **add api to app** section, select the **+** next to the **shipment tracking - unified** api.\n1. select **create app**. the **apps** page opens, displaying the app you just created.\n1. select the app you just created to view its details.\n1. select **show key** next to **api key**.\n1. copy the **api key** and enter it in your n8n credential.\n\nrefer to [how to create an app?](https://support-developer.dhl.com/support/solutions/articles/47001177011-how-to-create-an-app-) for more information.\n dhl credentials",
+        "importantTerms": [
+          "select",
+          "developer",
+          "create",
+          "credentials",
+          "https",
+          "support",
+          "user",
+          "nodes",
+          "apps",
+          "enter"
+        ]
+      }
+    },
     {
       "id": "page-0788",
       "title": "Drift credentials",
@@ -66555,77 +66429,6 @@
     },
     {
       "id": "page-0864",
-      "title": "Mailjet credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/mailjet/index.md",
-      "urlPath": "integrations/builtin/credentials/mailjet/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Mailjet credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Mailjet](../../app-nodes/n8n-nodes-base.mailjet/)\n- [Mailjet Trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)\n\n## Prerequisites\n\nCreate a [Mailjet](https://www.mailjet.com/) account.\n\n## Supported authentication methods\n\n- Email API key: For use with Mailjet's Email API\n- SMS token: For use with Mailjet's SMS API\n\n## Related resources\n\nRefer to [Mailjet's Email API documentation](https://dev.mailjet.com/email/guides/) and [Mailjet's SMS API documentation](https://dev.mailjet.com/sms/reference/send-message/) for more information about each service.\n\n## Using Email API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: View and generate API keys in your Mailjet [API Key Management](https://app.mailjet.com/signin) page.\n- A **Secret Key**: View your API Secret Keys in your Mailjet [API Key Management](https://app.mailjet.com/signin) page.\n- *Optional:* Select whether to use **Sandbox Mode** for calls made using this credential. When turned on, all API calls use Sandbox mode: the API will still validate the payloads but won't deliver the actual messages. This can be useful to troubleshoot any payload error messages without actually sending messages. Refer to Mailjet's [Sandbox Mode documentation](https://dev.mailjet.com/email/guides/send-api-v31/#sandbox-mode) for more information.\n\nFor this credential, you can use either:\n\n- Mailjet's primary API key and secret key\n- A subaccount API key and secret key\n\nRefer to Mailjet's [How to create a subaccount (or additional API key) documentation](https://documentation.mailjet.com/hc/en-us/articles/360042561974-How-to-create-a-subaccount-or-additional-API-Key) for detailed instructions on creating more API keys. Refer to [What are subaccounts and how does it help me?](https://documentation.mailjet.com/hc/en-us/articles/360042561854-What-are-subaccounts-and-how-does-it-help-me) page for more information on Mailjet subaccounts and when you might want to use one.\n\n## Using SMS Token\n\nTo configure this credential, you'll need:\n\n- An access **Token**: Generate a new token from Mailjet's [SMS Dashboard](https://app.mailjet.com/sms).\n",
-        "excerpt": "# Mailjet credentials  You can use these credentials to authenticate the following nodes:  - [Mailjet](../../app-nodes/n8n-nodes-base.mailjet/) - [Mailjet Trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)  ## Prerequisites  Create a [Mailjet](https://www.mailjet.com/) account.  ## Supported authentication methods  - Email API key: For use with Mailjet's Email API - SMS token: For use with Mailjet's SMS API  ## Related resources  Refer to [Mailjet's Email API documentation](https://dev...",
-        "sections": [
-          {
-            "title": "Mailjet credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Mailjet](../../app-nodes/n8n-nodes-base.mailjet/)\n- [Mailjet Trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "mailjet",
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using",
-          "email",
-          "token"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 2223,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "mailjet credentials # mailjet credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [mailjet](../../app-nodes/n8n-nodes-base.mailjet/)\n- [mailjet trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)\n\n## prerequisites\n\ncreate a [mailjet](https://www.mailjet.com/) account.\n\n## supported authentication methods\n\n- email api key: for use with mailjet's email api\n- sms token: for use with mailjet's sms api\n\n## related resources\n\nrefer to [mailjet's email api documentation](https://dev.mailjet.com/email/guides/) and [mailjet's sms api documentation](https://dev.mailjet.com/sms/reference/send-message/) for more information about each service.\n\n## using email api key\n\nto configure this credential, you'll need:\n\n- an **api key**: view and generate api keys in your mailjet [api key management](https://app.mailjet.com/signin) page.\n- a **secret key**: view your api secret keys in your mailjet [api key management](https://app.mailjet.com/signin) page.\n- *optional:* select whether to use **sandbox mode** for calls made using this credential. when turned on, all api calls use sandbox mode: the api will still validate the payloads but won't deliver the actual messages. this can be useful to troubleshoot any payload error messages without actually sending messages. refer to mailjet's [sandbox mode documentation](https://dev.mailjet.com/email/guides/send-api-v31/#sandbox-mode) for more information.\n\nfor this credential, you can use either:\n\n- mailjet's primary api key and secret key\n- a subaccount api key and secret key\n\nrefer to mailjet's [how to create a subaccount (or additional api key) documentation](https://documentation.mailjet.com/hc/en-us/articles/360042561974-how-to-create-a-subaccount-or-additional-api-key) for detailed instructions on creating more api keys. refer to [what are subaccounts and how does it help me?](https://documentation.mailjet.com/hc/en-us/articles/360042561854-what-are-subaccounts-and-how-does-it-help-me) page for more information on mailjet subaccounts and when you might want to use one.\n\n## using sms token\n\nto configure this credential, you'll need:\n\n- an access **token**: generate a new token from mailjet's [sms dashboard](https://app.mailjet.com/sms).\n mailjet credentials",
-        "importantTerms": [
-          "mailjet",
-          "https",
-          "email",
-          "documentation",
-          "nodes",
-          "this",
-          "credentials",
-          "token",
-          "refer",
-          "more",
-          "credential",
-          "secret",
-          "sandbox",
-          "mode",
-          "create",
-          "information",
-          "using",
-          "keys",
-          "your",
-          "page",
-          "messages",
-          "subaccount",
-          "subaccounts"
-        ]
-      }
-    },
-    {
-      "id": "page-0865",
       "title": "Malcore credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/malcore/index.md",
       "urlPath": "integrations/builtin/credentials/malcore/index.md",
@@ -66676,7 +66479,7 @@
       }
     },
     {
-      "id": "page-0866",
+      "id": "page-0865",
       "title": "Mandrill credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/mandrill/index.md",
       "urlPath": "integrations/builtin/credentials/mandrill/index.md",
@@ -66732,7 +66535,7 @@
       }
     },
     {
-      "id": "page-0867",
+      "id": "page-0866",
       "title": "Marketstack credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/marketstack/index.md",
       "urlPath": "integrations/builtin/credentials/marketstack/index.md",
@@ -66782,6 +66585,77 @@
         ]
       }
     },
+    {
+      "id": "page-0867",
+      "title": "Mailjet credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/mailjet/index.md",
+      "urlPath": "integrations/builtin/credentials/mailjet/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Mailjet credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Mailjet](../../app-nodes/n8n-nodes-base.mailjet/)\n- [Mailjet Trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)\n\n## Prerequisites\n\nCreate a [Mailjet](https://www.mailjet.com/) account.\n\n## Supported authentication methods\n\n- Email API key: For use with Mailjet's Email API\n- SMS token: For use with Mailjet's SMS API\n\n## Related resources\n\nRefer to [Mailjet's Email API documentation](https://dev.mailjet.com/email/guides/) and [Mailjet's SMS API documentation](https://dev.mailjet.com/sms/reference/send-message/) for more information about each service.\n\n## Using Email API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: View and generate API keys in your Mailjet [API Key Management](https://app.mailjet.com/signin) page.\n- A **Secret Key**: View your API Secret Keys in your Mailjet [API Key Management](https://app.mailjet.com/signin) page.\n- *Optional:* Select whether to use **Sandbox Mode** for calls made using this credential. When turned on, all API calls use Sandbox mode: the API will still validate the payloads but won't deliver the actual messages. This can be useful to troubleshoot any payload error messages without actually sending messages. Refer to Mailjet's [Sandbox Mode documentation](https://dev.mailjet.com/email/guides/send-api-v31/#sandbox-mode) for more information.\n\nFor this credential, you can use either:\n\n- Mailjet's primary API key and secret key\n- A subaccount API key and secret key\n\nRefer to Mailjet's [How to create a subaccount (or additional API key) documentation](https://documentation.mailjet.com/hc/en-us/articles/360042561974-How-to-create-a-subaccount-or-additional-API-Key) for detailed instructions on creating more API keys. Refer to [What are subaccounts and how does it help me?](https://documentation.mailjet.com/hc/en-us/articles/360042561854-What-are-subaccounts-and-how-does-it-help-me) page for more information on Mailjet subaccounts and when you might want to use one.\n\n## Using SMS Token\n\nTo configure this credential, you'll need:\n\n- An access **Token**: Generate a new token from Mailjet's [SMS Dashboard](https://app.mailjet.com/sms).\n",
+        "excerpt": "# Mailjet credentials  You can use these credentials to authenticate the following nodes:  - [Mailjet](../../app-nodes/n8n-nodes-base.mailjet/) - [Mailjet Trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)  ## Prerequisites  Create a [Mailjet](https://www.mailjet.com/) account.  ## Supported authentication methods  - Email API key: For use with Mailjet's Email API - SMS token: For use with Mailjet's SMS API  ## Related resources  Refer to [Mailjet's Email API documentation](https://dev...",
+        "sections": [
+          {
+            "title": "Mailjet credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Mailjet](../../app-nodes/n8n-nodes-base.mailjet/)\n- [Mailjet Trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "mailjet",
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using",
+          "email",
+          "token"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 2223,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "mailjet credentials # mailjet credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [mailjet](../../app-nodes/n8n-nodes-base.mailjet/)\n- [mailjet trigger](../../trigger-nodes/n8n-nodes-base.mailjettrigger/)\n\n## prerequisites\n\ncreate a [mailjet](https://www.mailjet.com/) account.\n\n## supported authentication methods\n\n- email api key: for use with mailjet's email api\n- sms token: for use with mailjet's sms api\n\n## related resources\n\nrefer to [mailjet's email api documentation](https://dev.mailjet.com/email/guides/) and [mailjet's sms api documentation](https://dev.mailjet.com/sms/reference/send-message/) for more information about each service.\n\n## using email api key\n\nto configure this credential, you'll need:\n\n- an **api key**: view and generate api keys in your mailjet [api key management](https://app.mailjet.com/signin) page.\n- a **secret key**: view your api secret keys in your mailjet [api key management](https://app.mailjet.com/signin) page.\n- *optional:* select whether to use **sandbox mode** for calls made using this credential. when turned on, all api calls use sandbox mode: the api will still validate the payloads but won't deliver the actual messages. this can be useful to troubleshoot any payload error messages without actually sending messages. refer to mailjet's [sandbox mode documentation](https://dev.mailjet.com/email/guides/send-api-v31/#sandbox-mode) for more information.\n\nfor this credential, you can use either:\n\n- mailjet's primary api key and secret key\n- a subaccount api key and secret key\n\nrefer to mailjet's [how to create a subaccount (or additional api key) documentation](https://documentation.mailjet.com/hc/en-us/articles/360042561974-how-to-create-a-subaccount-or-additional-api-key) for detailed instructions on creating more api keys. refer to [what are subaccounts and how does it help me?](https://documentation.mailjet.com/hc/en-us/articles/360042561854-what-are-subaccounts-and-how-does-it-help-me) page for more information on mailjet subaccounts and when you might want to use one.\n\n## using sms token\n\nto configure this credential, you'll need:\n\n- an access **token**: generate a new token from mailjet's [sms dashboard](https://app.mailjet.com/sms).\n mailjet credentials",
+        "importantTerms": [
+          "mailjet",
+          "https",
+          "email",
+          "documentation",
+          "nodes",
+          "this",
+          "credentials",
+          "token",
+          "refer",
+          "more",
+          "credential",
+          "secret",
+          "sandbox",
+          "mode",
+          "create",
+          "information",
+          "using",
+          "keys",
+          "your",
+          "page",
+          "messages",
+          "subaccount",
+          "subaccounts"
+        ]
+      }
+    },
     {
       "id": "page-0868",
       "title": "Matrix credentials",
@@ -81873,27 +81747,27 @@
     },
     {
       "id": "page-1119",
-      "title": "WooCommerce Trigger",
-      "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.woocommercetrigger/index.md",
-      "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.woocommercetrigger/index.md",
+      "title": "Wise Trigger",
+      "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.wisetrigger/index.md",
+      "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.wisetrigger/index.md",
       "category": "trigger-nodes",
       "subcategory": null,
-      "nodeName": "woocommercetrigger",
-      "nodeType": "n8n-nodes-base.woocommercetrigger",
+      "nodeName": "wisetrigger",
+      "nodeType": "n8n-nodes-base.wisetrigger",
       "content": {
-        "markdown": "# WooCommerce Trigger node\n\n[WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/woocommerce/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [WooCommerce Trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page.\n\n## Events\n\n- coupon.created\n- coupon.updated\n- coupon.deleted\n- customer.created\n- customer.updated\n- customer.deleted\n- order.created\n- order.updated\n- order.deleted\n- product.created\n- product.updated\n- product.deleted\n",
-        "excerpt": "# WooCommerce Trigger node  [WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress.  Credentials  You can find authentication information for this node [here](../../credentials/woocommerce/).  Examples and templates  For usage examples and templates to help you get started, refer to n8n's [WooCommerce Trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page.  ## Events  - coupon.created - coupon.updated - coupon.deleted - custom...",
+        "markdown": "# Wise Trigger node\n\n[Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/wise/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Wise Trigger integrations](https://n8n.io/integrations/wise-trigger/) page.\n\n## Events\n\n- Triggered every time a balance account is credited\n- Triggered every time a balance account is credited or debited\n- Triggered every time a transfer's list of active cases is updated\n- Triggered every time a transfer's status is updated\n",
+        "excerpt": "# Wise Trigger node  [Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.  Credentials  You can find authentication information for this node [here](../../credentials/wise/).  Examples and templates  For usage examples and templates to help you get started, refer to n8n's [Wise Trigger integrations](https://n8n.io/integrations/wise-trigger/) page.  ## Events  - Triggered...",
         "sections": [
           {
-            "title": "WooCommerce Trigger node",
+            "title": "Wise Trigger node",
             "level": 1,
-            "content": "[WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/woocommerce/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [WooCommerce Trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page."
+            "content": "[Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/wise/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Wise Trigger integrations](https://n8n.io/integrations/wise-trigger/) page."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "woocommerce",
+          "wise",
           "trigger",
           "node",
           "events"
@@ -81903,48 +81777,47 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 651,
+        "contentLength": 728,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "woocommerce trigger # woocommerce trigger node\n\n[woocommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for wordpress.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/woocommerce/).\n\nexamples and templates\n\nfor usage examples and templates to help you get started, refer to n8n's [woocommerce trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page.\n\n## events\n\n- coupon.created\n- coupon.updated\n- coupon.deleted\n- customer.created\n- customer.updated\n- customer.deleted\n- order.created\n- order.updated\n- order.deleted\n- product.created\n- product.updated\n- product.deleted\n woocommerce trigger node",
+        "fullText": "wise trigger # wise trigger node\n\n[wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/wise/).\n\nexamples and templates\n\nfor usage examples and templates to help you get started, refer to n8n's [wise trigger integrations](https://n8n.io/integrations/wise-trigger/) page.\n\n## events\n\n- triggered every time a balance account is credited\n- triggered every time a balance account is credited or debited\n- triggered every time a transfer's list of active cases is updated\n- triggered every time a transfer's status is updated\n wise trigger node",
         "importantTerms": [
-          "woocommerce",
+          "wise",
           "trigger",
-          "created",
-          "updated",
-          "deleted",
+          "triggered",
+          "every",
+          "time",
           "node",
-          "coupon",
-          "customer",
-          "order",
-          "product"
+          "transfer",
+          "money",
+          "account"
         ]
       }
     },
     {
       "id": "page-1120",
-      "title": "Wise Trigger",
-      "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.wisetrigger/index.md",
-      "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.wisetrigger/index.md",
+      "title": "WooCommerce Trigger",
+      "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.woocommercetrigger/index.md",
+      "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.woocommercetrigger/index.md",
       "category": "trigger-nodes",
       "subcategory": null,
-      "nodeName": "wisetrigger",
-      "nodeType": "n8n-nodes-base.wisetrigger",
+      "nodeName": "woocommercetrigger",
+      "nodeType": "n8n-nodes-base.woocommercetrigger",
       "content": {
-        "markdown": "# Wise Trigger node\n\n[Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/wise/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Wise Trigger integrations](https://n8n.io/integrations/wise-trigger/) page.\n\n## Events\n\n- Triggered every time a balance account is credited\n- Triggered every time a balance account is credited or debited\n- Triggered every time a transfer's list of active cases is updated\n- Triggered every time a transfer's status is updated\n",
-        "excerpt": "# Wise Trigger node  [Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.  Credentials  You can find authentication information for this node [here](../../credentials/wise/).  Examples and templates  For usage examples and templates to help you get started, refer to n8n's [Wise Trigger integrations](https://n8n.io/integrations/wise-trigger/) page.  ## Events  - Triggered...",
+        "markdown": "# WooCommerce Trigger node\n\n[WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/woocommerce/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [WooCommerce Trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page.\n\n## Events\n\n- coupon.created\n- coupon.updated\n- coupon.deleted\n- customer.created\n- customer.updated\n- customer.deleted\n- order.created\n- order.updated\n- order.deleted\n- product.created\n- product.updated\n- product.deleted\n",
+        "excerpt": "# WooCommerce Trigger node  [WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress.  Credentials  You can find authentication information for this node [here](../../credentials/woocommerce/).  Examples and templates  For usage examples and templates to help you get started, refer to n8n's [WooCommerce Trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page.  ## Events  - coupon.created - coupon.updated - coupon.deleted - custom...",
         "sections": [
           {
-            "title": "Wise Trigger node",
+            "title": "WooCommerce Trigger node",
             "level": 1,
-            "content": "[Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/wise/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Wise Trigger integrations](https://n8n.io/integrations/wise-trigger/) page."
+            "content": "[WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/woocommerce/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [WooCommerce Trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "wise",
+          "woocommerce",
           "trigger",
           "node",
           "events"
@@ -81954,21 +81827,22 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 728,
+        "contentLength": 651,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "wise trigger # wise trigger node\n\n[wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/wise/).\n\nexamples and templates\n\nfor usage examples and templates to help you get started, refer to n8n's [wise trigger integrations](https://n8n.io/integrations/wise-trigger/) page.\n\n## events\n\n- triggered every time a balance account is credited\n- triggered every time a balance account is credited or debited\n- triggered every time a transfer's list of active cases is updated\n- triggered every time a transfer's status is updated\n wise trigger node",
+        "fullText": "woocommerce trigger # woocommerce trigger node\n\n[woocommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for wordpress.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/woocommerce/).\n\nexamples and templates\n\nfor usage examples and templates to help you get started, refer to n8n's [woocommerce trigger integrations](https://n8n.io/integrations/woocommerce-trigger/) page.\n\n## events\n\n- coupon.created\n- coupon.updated\n- coupon.deleted\n- customer.created\n- customer.updated\n- customer.deleted\n- order.created\n- order.updated\n- order.deleted\n- product.created\n- product.updated\n- product.deleted\n woocommerce trigger node",
         "importantTerms": [
-          "wise",
+          "woocommerce",
           "trigger",
-          "triggered",
-          "every",
-          "time",
+          "created",
+          "updated",
+          "deleted",
           "node",
-          "transfer",
-          "money",
-          "account"
+          "coupon",
+          "customer",
+          "order",
+          "product"
         ]
       }
     },
@@ -92449,7 +92323,6 @@
         "page-0168",
         "page-0196",
         "page-0197",
-        "page-0202",
         "page-0203",
         "page-0207",
         "page-0208",
@@ -92861,8 +92734,8 @@
         "page-0499",
         "page-0500",
         "page-0501",
+        "page-0503",
         "page-0504",
-        "page-0505",
         "page-0511",
         "page-0514",
         "page-0515",
@@ -93308,7 +93181,6 @@
         "page-0161",
         "page-0166",
         "page-0196",
-        "page-0202",
         "page-0203",
         "page-0207",
         "page-0213",
@@ -93395,7 +93267,7 @@
         "page-0153",
         "page-0164",
         "page-0194",
-        "page-0614",
+        "page-0615",
         "page-0630",
         "page-0656",
         "page-0657",
@@ -93496,7 +93368,6 @@
       "directory": [
         "page-0002",
         "page-0196",
-        "page-0202",
         "page-0203",
         "page-0207",
         "page-1156",
@@ -93782,7 +93653,7 @@
         "page-0700",
         "page-0715",
         "page-0716",
-        "page-0785",
+        "page-0784",
         "page-0857",
         "page-0957",
         "page-1005",
@@ -93804,7 +93675,6 @@
         "page-0003",
         "page-0083",
         "page-0196",
-        "page-0202",
         "page-0207",
         "page-0208",
         "page-0496",
@@ -93822,7 +93692,6 @@
         "page-0196",
         "page-0197",
         "page-0198",
-        "page-0202",
         "page-0207",
         "page-0208",
         "page-0374",
@@ -93851,8 +93720,8 @@
         "page-0498",
         "page-0499",
         "page-0500",
+        "page-0503",
         "page-0504",
-        "page-0505",
         "page-0510",
         "page-0511",
         "page-0514",
@@ -94007,8 +93876,8 @@
         "page-0496",
         "page-0499",
         "page-0500",
-        "page-0505",
-        "page-0507",
+        "page-0504",
+        "page-0506",
         "page-0526",
         "page-0534",
         "page-0634",
@@ -94216,12 +94085,12 @@
         "page-0736",
         "page-0745",
         "page-0753",
-        "page-0763",
+        "page-0762",
         "page-0766",
         "page-0767",
         "page-0769",
         "page-0778",
-        "page-0787",
+        "page-0786",
         "page-0788",
         "page-0789",
         "page-0791",
@@ -94271,7 +94140,6 @@
       ],
       "default": [
         "page-0003",
-        "page-0202",
         "page-0203",
         "page-0207",
         "page-0219",
@@ -94309,7 +94177,6 @@
         "page-0196",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0203",
         "page-0205",
         "page-0207",
@@ -94317,8 +94184,8 @@
         "page-0209",
         "page-0224",
         "page-0431",
+        "page-0505",
         "page-0506",
-        "page-0507",
         "page-0527",
         "page-0536",
         "page-0647",
@@ -94624,7 +94491,7 @@
         "page-0861",
         "page-0862",
         "page-0863",
-        "page-0864",
+        "page-0865",
         "page-0866",
         "page-0867",
         "page-0868",
@@ -94797,7 +94664,7 @@
       "oauth": [
         "page-0003",
         "page-0166",
-        "page-0505",
+        "page-0504",
         "page-0778",
         "page-0935",
         "page-0952",
@@ -94911,7 +94778,6 @@
         "page-0159",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0205",
         "page-0207",
         "page-0544",
@@ -94990,12 +94856,11 @@
         "page-0093",
         "page-0134",
         "page-0155",
-        "page-0202",
         "page-0203",
         "page-0207",
         "page-0209",
+        "page-0504",
         "page-0505",
-        "page-0506",
         "page-0536",
         "page-0678",
         "page-1029",
@@ -95071,7 +94936,7 @@
         "page-0051",
         "page-0674",
         "page-0701",
-        "page-0785",
+        "page-0784",
         "page-1166",
         "page-1182",
         "page-1183",
@@ -95100,7 +94965,6 @@
         "page-0162",
         "page-0166",
         "page-0196",
-        "page-0202",
         "page-0203",
         "page-0204",
         "page-0207",
@@ -95257,7 +95121,7 @@
         "page-0493",
         "page-0495",
         "page-0496",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0516",
         "page-0521",
@@ -95389,7 +95253,7 @@
         "page-0557",
         "page-0558",
         "page-0559",
-        "page-0615",
+        "page-0614",
         "page-0627",
         "page-1205"
       ],
@@ -95481,7 +95345,7 @@
       "share": [
         "page-0005",
         "page-0148",
-        "page-0507",
+        "page-0506",
         "page-0508",
         "page-0898",
         "page-1202",
@@ -96432,7 +96296,7 @@
         "page-0557",
         "page-0558",
         "page-0559",
-        "page-0615",
+        "page-0614",
         "page-0627",
         "page-1205"
       ],
@@ -96833,7 +96697,6 @@
         "page-0171",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0205",
         "page-0206",
         "page-0207",
@@ -96892,7 +96755,7 @@
         "page-0208",
         "page-0517",
         "page-0518",
-        "page-0614",
+        "page-0615",
         "page-0666",
         "page-0887"
       ],
@@ -96917,7 +96780,6 @@
         "page-0007",
         "page-0013",
         "page-0196",
-        "page-0202",
         "page-0207",
         "page-0208",
         "page-1151",
@@ -96948,7 +96810,7 @@
       ],
       "move": [
         "page-0008",
-        "page-0507",
+        "page-0506",
         "page-0647",
         "page-1232"
       ],
@@ -97059,7 +96921,7 @@
         "page-0381",
         "page-0468",
         "page-0493",
-        "page-0507",
+        "page-0506",
         "page-0528",
         "page-0529",
         "page-0530",
@@ -97116,7 +96978,6 @@
         "page-0150",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0204",
         "page-0205",
         "page-0206",
@@ -97442,7 +97303,7 @@
         "page-0061",
         "page-0198",
         "page-0208",
-        "page-0503",
+        "page-0506",
         "page-0507",
         "page-0509",
         "page-0513",
@@ -97528,7 +97389,7 @@
         "page-0013",
         "page-0170",
         "page-0377",
-        "page-0506",
+        "page-0505",
         "page-0508",
         "page-0671",
         "page-1231"
@@ -97549,7 +97410,6 @@
         "page-0013",
         "page-0024",
         "page-0196",
-        "page-0202",
         "page-0207",
         "page-0208",
         "page-0664",
@@ -97590,7 +97450,6 @@
         "page-0013",
         "page-0158",
         "page-0187",
-        "page-0202",
         "page-0203",
         "page-0204",
         "page-0207",
@@ -97629,7 +97488,7 @@
         "page-0321",
         "page-0322",
         "page-0471",
-        "page-0505",
+        "page-0504",
         "page-0529",
         "page-0530",
         "page-0582",
@@ -97769,7 +97628,6 @@
       ],
       "volumes": [
         "page-0013",
-        "page-0202",
         "page-0546"
       ],
       "personal": [
@@ -98024,7 +97882,7 @@
         "page-0491",
         "page-0493",
         "page-0495",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0516",
         "page-0521",
@@ -98070,7 +97928,7 @@
         "page-0601",
         "page-0602",
         "page-0604",
-        "page-0607",
+        "page-0605",
         "page-0631",
         "page-0632",
         "page-0633",
@@ -98159,7 +98017,7 @@
         "page-0030",
         "page-0189",
         "page-0566",
-        "page-0614",
+        "page-0615",
         "page-0630",
         "page-0656",
         "page-0666",
@@ -98330,7 +98188,7 @@
         "page-0491",
         "page-0493",
         "page-0495",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0516",
         "page-0521",
@@ -98450,7 +98308,6 @@
         "page-0015",
         "page-0021",
         "page-0201",
-        "page-0202",
         "page-0207",
         "page-0208",
         "page-1021",
@@ -98474,7 +98331,6 @@
         "page-0166",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0203",
         "page-0204",
         "page-0205",
@@ -98486,7 +98342,7 @@
         "page-0491",
         "page-0497",
         "page-0498",
-        "page-0503",
+        "page-0506",
         "page-0507",
         "page-0508",
         "page-0509",
@@ -100025,7 +99881,7 @@
         "page-0493",
         "page-0495",
         "page-0501",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0514",
         "page-0516",
@@ -100085,9 +99941,9 @@
         "page-0600",
         "page-0601",
         "page-0603",
-        "page-0604",
         "page-0605",
         "page-0606",
+        "page-0607",
         "page-0608",
         "page-0609",
         "page-0610",
@@ -100265,11 +100121,11 @@
         "page-0748",
         "page-0753",
         "page-0759",
-        "page-0761",
-        "page-0763",
+        "page-0762",
+        "page-0765",
         "page-0776",
         "page-0778",
-        "page-0785",
+        "page-0784",
         "page-0788",
         "page-0789",
         "page-0797",
@@ -100358,14 +100214,14 @@
         "page-0746",
         "page-0753",
         "page-0757",
-        "page-0763",
-        "page-0765",
+        "page-0762",
+        "page-0764",
         "page-0766",
         "page-0767",
         "page-0769",
         "page-0770",
         "page-0778",
-        "page-0787",
+        "page-0786",
         "page-0788",
         "page-0789",
         "page-0791",
@@ -100386,7 +100242,7 @@
         "page-0849",
         "page-0850",
         "page-0859",
-        "page-0864",
+        "page-0867",
         "page-0868",
         "page-0869",
         "page-0871",
@@ -100548,9 +100404,8 @@
       ],
       "folders": [
         "page-0018",
-        "page-0202",
         "page-0207",
-        "page-0506",
+        "page-0505",
         "page-1205"
       ],
       "examples": [
@@ -100819,7 +100674,7 @@
         "page-0493",
         "page-0495",
         "page-0501",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0514",
         "page-0516",
@@ -100879,9 +100734,9 @@
         "page-0600",
         "page-0601",
         "page-0603",
-        "page-0604",
         "page-0605",
         "page-0606",
+        "page-0607",
         "page-0608",
         "page-0609",
         "page-0610",
@@ -101147,7 +101002,6 @@
         "page-0158",
         "page-0170",
         "page-0193",
-        "page-0202",
         "page-0203",
         "page-0208",
         "page-0221",
@@ -101350,7 +101204,6 @@
         "page-0076",
         "page-0078",
         "page-0090",
-        "page-0202",
         "page-0207",
         "page-0661",
         "page-0662",
@@ -101390,7 +101243,6 @@
         "page-0197",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0203",
         "page-0205",
         "page-0206",
@@ -101409,7 +101261,6 @@
         "page-0197",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0203",
         "page-0205",
         "page-0206",
@@ -101596,8 +101447,8 @@
         "page-0498",
         "page-0499",
         "page-0500",
+        "page-0503",
         "page-0504",
-        "page-0505",
         "page-0510",
         "page-0511",
         "page-0514",
@@ -101825,7 +101676,7 @@
       ],
       "search": [
         "page-0037",
-        "page-0506",
+        "page-0505",
         "page-0548",
         "page-0558",
         "page-0669",
@@ -102183,7 +102034,7 @@
         "page-0498",
         "page-0499",
         "page-0500",
-        "page-0503",
+        "page-0506",
         "page-0507",
         "page-0508",
         "page-0509",
@@ -102524,7 +102375,7 @@
         "page-0491",
         "page-0493",
         "page-0495",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0516",
         "page-0521",
@@ -102666,7 +102517,7 @@
         "page-0861",
         "page-0862",
         "page-0863",
-        "page-0864",
+        "page-0865",
         "page-0866",
         "page-0867",
         "page-0868",
@@ -102984,7 +102835,7 @@
         "page-0861",
         "page-0862",
         "page-0863",
-        "page-0864",
+        "page-0865",
         "page-0866",
         "page-0867",
         "page-0868",
@@ -103214,7 +103065,7 @@
         "page-0709",
         "page-0715",
         "page-0716",
-        "page-0785",
+        "page-0784",
         "page-0861",
         "page-1159",
         "page-1169",
@@ -103324,7 +103175,7 @@
       ],
       "recent": [
         "page-0059",
-        "page-0505"
+        "page-0504"
       ],
       "run)": [
         "page-0059"
@@ -103444,7 +103295,7 @@
         "page-0085",
         "page-0095",
         "page-0208",
-        "page-0505",
+        "page-0504",
         "page-1027",
         "page-1028",
         "page-1245",
@@ -103579,7 +103430,6 @@
       "navigate": [
         "page-0068",
         "page-0196",
-        "page-0202",
         "page-0207"
       ],
       "body": [
@@ -104010,7 +103860,7 @@
         "page-0759",
         "page-0760",
         "page-0761",
-        "page-0762",
+        "page-0763",
         "page-0764",
         "page-0765",
         "page-0766",
@@ -104030,9 +103880,9 @@
         "page-0781",
         "page-0782",
         "page-0783",
+        "page-0784",
         "page-0785",
         "page-0786",
-        "page-0787",
         "page-0788",
         "page-0790",
         "page-0791",
@@ -105314,7 +105164,7 @@
         "page-0498",
         "page-0499",
         "page-0500",
-        "page-0503",
+        "page-0507",
         "page-0509",
         "page-0534",
         "page-0548",
@@ -105456,7 +105306,7 @@
         "page-0208",
         "page-0368",
         "page-0496",
-        "page-0505",
+        "page-0504",
         "page-0542",
         "page-0561",
         "page-0569",
@@ -105484,7 +105334,6 @@
       "stop": [
         "page-0141",
         "page-0196",
-        "page-0202",
         "page-0207",
         "page-0208",
         "page-0593",
@@ -105604,7 +105453,7 @@
         "page-0652",
         "page-0683",
         "page-0863",
-        "page-0864",
+        "page-0867",
         "page-1034",
         "page-1035",
         "page-1036",
@@ -105748,7 +105597,7 @@
       ],
       "event": [
         "page-0153",
-        "page-0503",
+        "page-0507",
         "page-1142",
         "page-1144"
       ],
@@ -105811,7 +105660,6 @@
         "page-0161",
         "page-0166",
         "page-0196",
-        "page-0202",
         "page-0203",
         "page-0207",
         "page-0213"
@@ -105910,7 +105758,6 @@
       "container": [
         "page-0157",
         "page-0196",
-        "page-0202",
         "page-0207",
         "page-0515",
         "page-0632",
@@ -106328,7 +106175,6 @@
       ],
       "latest": [
         "page-0196",
-        "page-0202",
         "page-0207",
         "page-1151",
         "page-1152"
@@ -106347,12 +106193,10 @@
       ],
       "containing": [
         "page-0196",
-        "page-0202",
         "page-0207"
       ],
       "older": [
         "page-0196",
-        "page-0202",
         "page-0207"
       ],
       "stack": [
@@ -106400,7 +106244,7 @@
         "page-0499",
         "page-0500",
         "page-0502",
-        "page-0503",
+        "page-0505",
         "page-0506",
         "page-0507",
         "page-0508",
@@ -106520,7 +106364,6 @@
       "clone": [
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0205",
         "page-0207",
         "page-0664"
@@ -106528,7 +106371,6 @@
       "repository": [
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0205",
         "page-0207",
         "page-1204",
@@ -106543,7 +106385,7 @@
         "page-0519",
         "page-0520",
         "page-0522",
-        "page-0607",
+        "page-0604",
         "page-0921",
         "page-1097",
         "page-1205"
@@ -106587,28 +106429,6 @@
         "page-0201",
         "page-0205"
       ],
-      "digital": [
-        "page-0202"
-      ],
-      "ocean": [
-        "page-0202"
-      ],
-      "digitalocean": [
-        "page-0202",
-        "page-0942"
-      ],
-      "droplet": [
-        "page-0202"
-      ],
-      "ports": [
-        "page-0202",
-        "page-0206",
-        "page-0207"
-      ],
-      "caddy": [
-        "page-0202",
-        "page-0207"
-      ],
       "register": [
         "page-0203",
         "page-0739",
@@ -106803,9 +106623,16 @@
       "dockerfile": [
         "page-0206"
       ],
+      "ports": [
+        "page-0206",
+        "page-0207"
+      ],
       "hetzner": [
         "page-0207"
       ],
+      "caddy": [
+        "page-0207"
+      ],
       "openshift": [
         "page-0208"
       ],
@@ -106979,7 +106806,7 @@
         "page-0218",
         "page-0428",
         "page-0556",
-        "page-0604",
+        "page-0605",
         "page-0939",
         "page-1101",
         "page-1204"
@@ -107100,7 +106927,7 @@
       ],
       "copy": [
         "page-0208",
-        "page-0507",
+        "page-0506",
         "page-1170",
         "page-1215",
         "page-1242",
@@ -107423,7 +107250,7 @@
       ],
       "verified": [
         "page-0223",
-        "page-0505",
+        "page-0504",
         "page-1027",
         "page-1028",
         "page-1153",
@@ -107788,7 +107615,7 @@
         "page-0501",
         "page-0502",
         "page-0503",
-        "page-0504",
+        "page-0505",
         "page-0506",
         "page-0507",
         "page-0508",
@@ -108078,7 +107905,7 @@
         "page-0491",
         "page-0493",
         "page-0495",
-        "page-0504",
+        "page-0503",
         "page-0510",
         "page-0516",
         "page-0521",
@@ -108254,7 +108081,7 @@
       ],
       "webex": [
         "page-0273",
-        "page-0761",
+        "page-0765",
         "page-1053"
       ],
       "cisco": [
@@ -108262,26 +108089,26 @@
         "page-0758",
         "page-0759",
         "page-0760",
-        "page-0761",
+        "page-0765",
         "page-1053"
       ],
       "clearbit": [
         "page-0274",
-        "page-0762"
+        "page-0761"
       ],
       "clickup": [
         "page-0275",
-        "page-0763",
+        "page-0762",
         "page-1054"
       ],
       "clockify": [
         "page-0276",
-        "page-0764",
+        "page-0763",
         "page-1055"
       ],
       "cloudflare": [
         "page-0277",
-        "page-0765",
+        "page-0764",
         "page-1204"
       ],
       "cockpit": [
@@ -108342,11 +108169,11 @@
       ],
       "discourse": [
         "page-0292",
-        "page-0786"
+        "page-0785"
       ],
       "disqus": [
         "page-0293",
-        "page-0787"
+        "page-0786"
       ],
       "drift": [
         "page-0294",
@@ -108660,16 +108487,16 @@
       ],
       "mailjet": [
         "page-0364",
-        "page-0864",
+        "page-0867",
         "page-1086"
       ],
       "mandrill": [
         "page-0365",
-        "page-0866"
+        "page-0865"
       ],
       "marketstack": [
         "page-0366",
-        "page-0867"
+        "page-0866"
       ],
       "matrix": [
         "page-0367",
@@ -109200,12 +109027,12 @@
       "wise": [
         "page-0477",
         "page-1008",
-        "page-1120"
+        "page-1119"
       ],
       "woocommerce": [
         "page-0478",
         "page-1010",
-        "page-1119"
+        "page-1120"
       ],
       "wordpress": [
         "page-0479",
@@ -109284,7 +109111,7 @@
       "discord": [
         "page-0493",
         "page-0494",
-        "page-0785",
+        "page-0784",
         "page-1205"
       ],
       "embeds": [
@@ -109328,7 +109155,7 @@
       ],
       "unauthorized": [
         "page-0496",
-        "page-0505",
+        "page-0504",
         "page-1027",
         "page-1028",
         "page-1137",
@@ -109391,7 +109218,7 @@
       "calendar": [
         "page-0501",
         "page-0502",
-        "page-0503",
+        "page-0507",
         "page-1071"
       ],
       "availability": [
@@ -109399,10 +109226,10 @@
         "page-1205"
       ],
       "drive": [
+        "page-0503",
         "page-0504",
         "page-0505",
         "page-0506",
-        "page-0507",
         "page-0508",
         "page-0509",
         "page-1029",
@@ -109410,17 +109237,17 @@
         "page-1140"
       ],
       "hasn't": [
-        "page-0505",
+        "page-0504",
         "page-1027",
         "page-1028"
       ],
       "becoming": [
-        "page-0505",
+        "page-0504",
         "page-1027",
         "page-1028"
       ],
       "download": [
-        "page-0507",
+        "page-0506",
         "page-0652",
         "page-0663",
         "page-0689",
@@ -109428,7 +109255,7 @@
         "page-1196"
       ],
       "upload": [
-        "page-0507",
+        "page-0506",
         "page-0536",
         "page-0663",
         "page-0689"
@@ -110313,7 +110140,7 @@
         "page-0833"
       ],
       "xata": [
-        "page-0605",
+        "page-0606",
         "page-1015"
       ],
       "selector": [
@@ -111257,7 +111084,7 @@
         "page-0863"
       ],
       "malcore": [
-        "page-0865"
+        "page-0864"
       ],
       "(general)": [
         "page-0874"
@@ -111338,6 +111165,9 @@
       "future": [
         "page-0937"
       ],
+      "digitalocean": [
+        "page-0942"
+      ],
       "spaces": [
         "page-0942"
       ],
@@ -113189,7 +113019,6 @@
         "page-0199",
         "page-0200",
         "page-0201",
-        "page-0202",
         "page-0203",
         "page-0204",
         "page-0205",
@@ -114548,13 +114377,13 @@
       "googlecalendar": [
         "page-0501",
         "page-0502",
-        "page-0503"
+        "page-0507"
       ],
       "googledrive": [
+        "page-0503",
         "page-0504",
         "page-0505",
         "page-0506",
-        "page-0507",
         "page-0508",
         "page-0509"
       ],
@@ -115031,10 +114860,10 @@
       "whatsapptrigger": [
         "page-1118"
       ],
-      "woocommercetrigger": [
+      "wisetrigger": [
         "page-1119"
       ],
-      "wisetrigger": [
+      "woocommercetrigger": [
         "page-1120"
       ],
       "workabletrigger": [