@n8n-as-code/skills 1.7.1-next.7 → 1.8.0-next.18

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

@@ -1,8 +1,8 @@
 {
-  "generatedAt": "2026-04-07T11:58:18.910Z",
+  "generatedAt": "2026-04-07T21:26:26.421Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1261,
+  "totalPages": 1262,
   "statistics": {
     "byCategory": {
       "other": 517,
@@ -12,7 +12,7 @@
       "code": 20,
       "data": 38,
       "flow-logic": 8,
-      "hosting": 79,
+      "hosting": 80,
       "integrations": 306,
       "cluster-nodes": 101,
       "trigger-nodes": 107,
@@ -21,7 +21,7 @@
     },
     "withNodeNames": 471,
     "withUseCases": 39,
-    "withCodeExamples": 179
+    "withCodeExamples": 180
   },
   "categories": {
     "other": {
@@ -710,7 +710,7 @@
     },
     "hosting": {
       "description": "Self-hosting, deployment, and infrastructure",
-      "totalPages": 79,
+      "totalPages": 80,
       "pages": [
         "page-0150",
         "page-0151",
@@ -767,6 +767,7 @@
         "page-0202",
         "page-0203",
         "page-0204",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208",
@@ -17272,13 +17273,13 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Hosting n8n on Google Kubernetes Engine\n\nGoogle Cloud offers several options suitable for hosting n8n, including Cloud Run (optimized for running containers), Compute Engine (VMs), and Kubernetes Engine (containers running with Kubernetes).\n\nThis guide uses the Google Kubernetes Engine (GKE) as the hosting option. If you want to use Cloud Run, refer to [these instructions](../google-cloud-run/).\n\nMost of the steps in this guide use the Google Cloud UI, but you can also use the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/) instead to undertake all the steps.\n\n## Prerequisites\n\n- The [gcloud command line tool](https://cloud.google.com/sdk/gcloud/)\n- The [gke-gcloud-auth-plugin](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke) (install the gcloud CLI first)\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.15.0 Current `beta`: 2.16.0\n\n## Create project\n\nGCP encourages you to create projects to logically organize resources and configuration. Create a new project for your n8n deployment from your Google Cloud Console: select the project dropdown menu and then the **NEW PROJECT** button. Then select the newly created project. As you follow the other steps in this guide, make sure you have the correct project selected.\n\n## Enable the Kubernetes Engine API\n\nGKE isn't enabled by default. Search for \"Kubernetes\" in the top search bar and select \"Kubernetes Engine\" from the results.\n\nSelect **ENABLE** to enable the Kubernetes Engine API for this project.\n\n## Create a cluster\n\nFrom the [GKE service page](https://console.cloud.google.com/kubernetes/list/overview), select **Clusters** > **CREATE**. Make sure you select the \"Standard\" cluster option, n8n doesn't work with an \"Autopilot\" cluster. You can leave the cluster configuration on defaults unless there's anything specifically you need to change, such as location.\n\n## Set Kubectl context\n\nThe rest of the steps in this guide require you to set the GCP instance as the Kubectl context. You can find the connection details for a cluster instance by opening its details page and selecting **CONNECT**. The displayed code snippet shows a connection string for the gcloud CLI tool. Paste and run the code snippet in the gcloud CLI to change your local Kubernetes settings to use the new gcloud 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) locally. The following steps explain the file configuration and how to add your information.\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### Create a volume for persistent storage\n\nTo maintain data between pod restarts, the Postgres deployment needs a persistent volume. Running Postgres on GCP requires a specific Kubernetes Storage Class. You can read [this guide](https://cloud.google.com/architecture/deploying-highly-available-postgresql-with-gke) for specifics, but the `storage.yaml` manifest creates it for you. You may want to change the regions to create the storage in under the `allowedTopologies` > `matchedLabelExpressions` > `values` key. By default, they're set to `us-central`.\n\n```\n…\nallowedTopologies:\n  - matchLabelExpressions:\n      - key: failure-domain.beta.kubernetes.io/zone\n        values:\n          - us-central1-b\n          - us-central1-c\n```\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` and `postgres-deployment.yaml` files:\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 & Ingress** menu item of the cluster you want to use under the **Endpoints** column.\n\nGKE and IP addresses\n\n[Read this GKE tutorial](https://cloud.google.com/kubernetes-engine/docs/tutorials/configuring-domain-name-static-ip#configuring_your_domain_name_records) for more details on how reserved IP addresses work with GKE and Kubernetes resources.\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/).\nated \\\n    --port=5678 \\\n    --memory=2Gi \\\n    --no-cpu-throttling \\\n    --set-env-vars=\"N8N_PORT=5678,N8N_PROTOCOL=https,N8N_ENDPOINT_HEALTH=health,DB_TYPE=postgresdb,DB_POSTGRESDB_DATABASE=n8n,DB_POSTGRESDB_USER=n8n-user,DB_POSTGRESDB_HOST=/cloudsql/$PROJECT_ID:$REGION:n8n-db,DB_POSTGRESDB_PORT=5432,DB_POSTGRESDB_SCHEMA=public,GENERIC_TIMEZONE=UTC,QUEUE_HEALTH_CHECK_ACTIVE=true\" \\\n    --set-secrets=\"DB_POSTGRESDB_PASSWORD=n8n-db-password:latest,N8N_ENCRYPTION_KEY=n8n-encryption-key:latest\" \\\n    --add-cloudsql-instances=$PROJECT_ID:$REGION:n8n-db \\\n    --service-account=n8n-service-account@$PROJECT_ID.iam.gserviceaccount.com\n```\n\nOnce the deployment finishes, open another tab to navigate to the Service URL. You should see the n8n login screen.\n\n## Troubleshooting\n\nIf you see a \"Cannot GET /\" screen this usually indicates that n8n is still starting up. You can refresh the page and it should eventually load.\n\n## (Optional) Enabling Google Workspace services as n8n tools\n\nIf you want to use Google Workspace services (Gmail, Calendar, Drive, etc.) as tools in n8n, it's recommended to setup OAuth to access these services.\n\nFirst ensure the respective APIs you want are enabled:\n\n```\n## Enable whichever APIs you need\n## Note: If you want Sheets/Docs, it's not enough to just enable Drive; these services each have their own API\ngcloud services enable gmail.googleapis.com\ngcloud services enable drive.googleapis.com\ngcloud services enable sheets.googleapis.com\ngcloud services enable docs.googleapis.com\ngcloud services enable calendar-json.googleapis.com\n```\n\nRe-deploy n8n on Cloud Run with the necessary OAuth callback URLs as environment variables:\n\n```\nexport SERVICE_URL=\"your-n8n-service-URL\"\n## e.g. https://n8n-12345678.us-west1.run.app\n\ngcloud run services update n8n \\\n    --region=$REGION \\\n    --update-env-vars=\"N8N_HOST=$(echo $SERVICE_URL | sed 's/https:\\/\\///'),WEBHOOK_URL=$SERVICE_URL,N8N_EDITOR_BASE_URL=$SERVICE_URL\"\n```\n\nLastly, you must setup OAuth for these services. Visit `https://console.cloud.google.com/auth` and follow these steps:\n\n1. Click \"Get Started\" if this button shows (when you have not yet setup OAuth in this Cloud project).\n1. For \"App Information\", enter whichever \"App Name\" and \"User Support Email\" you prefer.\n1. For \"Audience\", select \"Internal\" if you intend to only enable access to your user(s) within this same Google Workspace. Otherwise, you can select \"External\".\n1. Enter \"Contact Information\".\n1. If you selected \"External\", then click \"Audience\" and add any test users you need to grant access.\n1. Click \"Clients\" > \"Create client\", select \"Web application\" for \"Application type\", enter your n8n service URL into \"Authorized JavaScript origins\", and \"/rest/oauth2-credential/callback\" into \"Authorized redirect URIs\" where your YOUR-N8N-URL is also the n8n service URL (e.g. `https://n8n-12345678.us-west1.run.app/rest/oauth2-credential/callback`). Make sure you download the created client's JSON file since it contains the client secret which you will not be able to see later in the Console.\n1. Click \"Data Access\" and add the scopes you want n8n to have access for (e.g. to access Google Sheets, you need `https://googleapis.com/auth/drive.file` and `https://googleapis.com/auth/spreadsheets`)\n1. Now you should be able to use these workspace services. You can test if it works by logging into n8n, add a Tool for the respective service and add its credentials using the information in the OAuth client JSON file from step 6.\n",
-        "excerpt": "# Hosting n8n on Google Kubernetes Engine  Google Cloud offers several options suitable for hosting n8n, including Cloud Run (optimized for running containers), Compute Engine (VMs), and Kubernetes Engine (containers running with Kubernetes).  This guide uses the Google Kubernetes Engine (GKE) as the hosting option. If you want to use Cloud Run, refer to [these instructions](../google-cloud-run/).  Most of the steps in this guide use the Google Cloud UI, but you can also use the [gcloud command...",
+        "markdown": "# Hosting n8n on Google Cloud Run\n\nThis hosting guide shows you how to self-host n8n on Google Cloud Run, a serverless container runtime. If you're just getting started with n8n and don't need a production-grade deployment, you can go with the \"easy mode\" option below for deployment. Otherwise, if you intend to use this n8n deployment at-scale, refer to the \"durable mode\" instructions further down.\n\nYou can also enable access via OAuth to Google Workspace, such as Gmail and Drive, to use these services as n8n workflow tools. Instructions for granting n8n access to these services are at the end of of this documentation.\n\nIf you want to deploy to Google Kubernetes Engine (GKE) instead, you can refer to [these instructions](../google-kubernetes-engine/).\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.15.0 Current `beta`: 2.16.0\n\n## Before you begin: get a Google Cloud project\n\nIf you have not yet created a Google Cloud project, [do this first](https://developers.google.com/workspace/guides/create-project) (and ensure you have billing enabled on the project; even if your Cloud Run service runs for free you must have billing activated to deploy). Otherwise, navigate to the project where you want to deploy n8n.\n\n## Easy mode\n\nThis is the fastest way to deploy n8n on Cloud Run. For this deployment, n8n's data is in-memory so this is only recommended for demo purposes. **Anytime this Cloud Run service scales to zero or is redeployed, the n8n data will be lost.** Refer to the durable mode instructions below if you need a production-grade deployment.\n\nIf you have not yet created a Google Cloud project, [do this first](https://developers.google.com/workspace/guides/create-project) (and ensure you have billing enabled on the project; even if your Cloud Run service will run for free you must have billing enabled to activated to deploy). Otherwise, navigate to the project where you want to deploy n8n.\n\nOpen the Cloud Shell Terminal (on the Google Cloud console, either type \"G\" then \"S\" or click on the terminal icon on the upper right).\n\nOnce your session is open, you may need to run this command first to login (and follow the steps it asks you to complete):\n\n```\ngcloud auth login\n```\n\nYou can also explicitly enable the Cloud Run API (even if you don't do this, it will ask if you want this enabled when you deploy):\n\n```\ngcloud services enable run.googleapis.com\n```\n\nRequired: Custom health check endpoint\n\nGoogle Cloud Run reserves `/healthz` for its own health checks. Since n8n uses this path by default, it can conflict and cause connection issues in the workflow canvas. To fix this, set the `N8N_ENDPOINT_HEALTH` environment variable to a custom path (included in the deployment commands below).\n\nTo deploy n8n:\n\n```\ngcloud run deploy n8n \\\n    --image=n8nio/n8n \\\n    --region=us-west1 \\\n    --allow-unauthenticated \\\n    --port=5678 \\\n    --no-cpu-throttling \\\n    --memory=2Gi \\\n    --set-env-vars=\"N8N_ENDPOINT_HEALTH=health\"\n```\n\n(you can specify whichever region you prefer, instead of \"us-west1\")\n\nOnce the deployment finishes, open another tab to navigate to the Service URL. n8n may still be loading and you will see a \"n8n is starting up. Please wait\" message, but shortly thereafter you should see the n8n login screen.\n\nOptional: If you want to keep this n8n service running for as long as possible to avoid data loss, you can also set manual scale to 1 to prevent it from autoscaling to 0.\n\n```\ngcloud run deploy n8n \\\n    --image=n8nio/n8n \\\n    --region=us-west1 \\\n    --allow-unauthenticated \\\n    --port=5678 \\\n    --no-cpu-throttling \\\n    --memory=2Gi \\\n    --scaling=1 \\\n    --set-env-vars=\"N8N_ENDPOINT_HEALTH=health\"\n```\n\nThis does not prevent data loss completely, such as whenever the Cloud Run service is re-deployed/updated. If you want truly persistant data, you should refer to the instructions below for how to attach a database.\n\n## Durable mode\n\nThe following instructions are intended for a more durable, production-grade deployment of n8n on Cloud Run. It includes resources such as a database for persistance and secret manager for sensitive data.\n\nIf you want to deploy the following setup via Terraform, refer to this [example](https://github.com/ryanpei/n8n-hosting/tree/main/google-cloud-run) which deploys the same setup as the following (without the OAuth setup for Google Workspace tools).\n\n## Enable APIs and set env vars\n\nOpen the Cloud Shell Terminal (on the Google Cloud console, either type \"G\" then \"S\" or click on the terminal icon on the upper right) and run these commands in the terminal session:\n\n```\n## You may need to login first\ngcloud auth login\n\ngcloud services enable run.googleapis.com\ngcloud services enable sqladmin.googleapis.com\ngcloud services enable secretmanager.googleapis.com\n```\n\nYou'll also want to set some environment variables for the remainder of these instructions:\n\n```\nexport PROJECT_ID=your-project\nexport REGION=region-where-you-want-this-deployed\n```\n\n## Setup your Postgres database\n\nRun this command to create the Postgres DB instance (it will take a few minutes to complete; also ensure you update the root-password field with your own desired password):\n\n```\ngcloud sql instances create n8n-db \\\n    --database-version=POSTGRES_13 \\\n    --tier=db-f1-micro \\\n    --region=$REGION \\\n    --root-password=\"change-this-password\" \\\n    --storage-size=10GB \\\n    --availability-type=ZONAL \\\n    --no-backup \\\n    --storage-type=HDD\n```\n\nOnce complete, you can add the database that n8n will use:\n\n```\ngcloud sql databases create n8n --instance=n8n-db\n```\n\nCreate the DB user for n8n (change the password value, of course):\n\n```\ngcloud sql users create n8n-user \\\n    --instance=n8n-db \\\n    --password=\"change-this-password\"\n```\n\nYou can save the password you set for this n8n-user to a file for the next step of saving the password in Secret Manager. Be sure to delete this file later.\n\n## Store sensitive data in Secret Manager\n\nWhile not required, it's absolutely recommended to store your sensitive data in Secrets Manager.\n\nCreate a secret for the database password (replace \"/your/password/file\" with the file you created above for the n8n-user password):\n\n```\ngcloud secrets create n8n-db-password \\\n    --data-file=/your/password/file \\\n    --replication-policy=\"automatic\"\n```\n\nCreate an encryption key (you can use your own, this example generates a random one):\n\n```\nopenssl rand -base64 -out my-encryption-key 42\n```\n\nCreate a secret for this encryption key (replace \"my-encryption-key\" if you are supplying your own):\n\n```\ngcloud secrets create n8n-encryption-key \\\n    --data-file=my-encryption-key \\\n    --replication-policy=\"automatic\"\n```\n\nNow you can delete my-encryption-key and the database password files you created. These values are now securely stored in Secret Manager.\n\n## Create a service account for Cloud Run\n\nYou want this Cloud Run service to be restricted to access only the resources it needs. The following commands create the service account and adds the permissions necessary to access secrets and the database:\n\n```\ngcloud iam service-accounts create n8n-service-account \\\n    --display-name=\"n8n Service Account\"\n\ngcloud secrets add-iam-policy-binding n8n-db-password \\\n    --member=\"serviceAccount:n8n-service-account@$PROJECT_ID.iam.gserviceaccount.com\" \\\n    --role=\"roles/secretmanager.secretAccessor\"\n\ngcloud secrets add-iam-policy-binding n8n-encryption-key \\\n    --member=\"serviceAccount:n8n-service-account@$PROJECT_ID.iam.gserviceaccount.com\" \\\n    --role=\"roles/secretmanager.secretAccessor\"\n\ngcloud projects add-iam-policy-binding $PROJECT_ID \\\n    --member=\"serviceAccount:n8n-service-account@$PROJECT_ID.iam.gserviceaccount.com\" \\\n    --role=\"roles/cloudsql.client\"\n```\n\n## Deploy the Cloud Run service\n\nNow you can deploy your n8n service:\n\n```\ngcloud run deploy n8n \\\n    --image=n8nio/n8n:latest \\\n    --command=\"/bin/sh\" \\\n    --args=\"-c,sleep 5;n8n start\" \\\n    --region=$REGION \\\n    --allow-unauthenticated \\\n    --port=5678 \\\n    --memory=2Gi \\\n    --no-cpu-throttling \\\n    --set-env-vars=\"N8N_PORT=5678,N8N_PROTOCOL=https,N8N_ENDPOINT_HEALTH=health,DB_TYPE=postgresdb,DB_POSTGRESDB_DATABASE=n8n,DB_POSTGRESDB_USER=n8n-user,DB_POSTGRESDB_HOST=/cloudsql/$PROJECT_ID:$REGION:n8n-db,DB_POSTGRESDB_PORT=5432,DB_POSTGRESDB_SCHEMA=public,GENERIC_TIMEZONE=UTC,QUEUE_HEALTH_CHECK_ACTIVE=true\" \\\n    --set-secrets=\"DB_POSTGRESDB_PASSWORD=n8n-db-password:latest,N8N_ENCRYPTION_KEY=n8n-encryption-key:latest\" \\\n    --add-cloudsql-instances=$PROJECT_ID:$REGION:n8n-db \\\n    --service-account=n8n-service-account@$PROJECT_ID.iam.gserviceaccount.com\n```\n\nOnce the deployment finishes, open another tab to navigate to the Service URL. You should see the n8n login screen.\n\n## Troubleshooting\n\nIf you see a \"Cannot GET /\" screen this usually indicates that n8n is still starting up. You can refresh the page and it should eventually load.\n\n## (Optional) Enabling Google Workspace services as n8n tools\n\nIf you want to use Google Workspace services (Gmail, Calendar, Drive, etc.) as tools in n8n, it's recommended to setup OAuth to access these services.\n\nFirst ensure the respective APIs you want are enabled:\n\n```\n## Enable whichever APIs you need\n## Note: If you want Sheets/Docs, it's not enough to just enable Drive; these services each have their own API\ngcloud services enable gmail.googleapis.com\ngcloud services enable drive.googleapis.com\ngcloud services enable sheets.googleapis.com\ngcloud services enable docs.googleapis.com\ngcloud services enable calendar-json.googleapis.com\n```\n\nRe-deploy n8n on Cloud Run with the necessary OAuth callback URLs as environment variables:\n\n```\nexport SERVICE_URL=\"your-n8n-service-URL\"\n## e.g. https://n8n-12345678.us-west1.run.app\n\ngcloud run services update n8n \\\n    --region=$REGION \\\n    --update-env-vars=\"N8N_HOST=$(echo $SERVICE_URL | sed 's/https:\\/\\///'),WEBHOOK_URL=$SERVICE_URL,N8N_EDITOR_BASE_URL=$SERVICE_URL\"\n```\n\nLastly, you must setup OAuth for these services. Visit `https://console.cloud.google.com/auth` and follow these steps:\n\n1. Click \"Get Started\" if this button shows (when you have not yet setup OAuth in this Cloud project).\n1. For \"App Information\", enter whichever \"App Name\" and \"User Support Email\" you prefer.\n1. For \"Audience\", select \"Internal\" if you intend to only enable access to your user(s) within this same Google Workspace. Otherwise, you can select \"External\".\n1. Enter \"Contact Information\".\n1. If you selected \"External\", then click \"Audience\" and add any test users you need to grant access.\n1. Click \"Clients\" > \"Create client\", select \"Web application\" for \"Application type\", enter your n8n service URL into \"Authorized JavaScript origins\", and \"/rest/oauth2-credential/callback\" into \"Authorized redirect URIs\" where your YOUR-N8N-URL is also the n8n service URL (e.g. `https://n8n-12345678.us-west1.run.app/rest/oauth2-credential/callback`). Make sure you download the created client's JSON file since it contains the client secret which you will not be able to see later in the Console.\n1. Click \"Data Access\" and add the scopes you want n8n to have access for (e.g. to access Google Sheets, you need `https://googleapis.com/auth/drive.file` and `https://googleapis.com/auth/spreadsheets`)\n1. Now you should be able to use these workspace services. You can test if it works by logging into n8n, add a Tool for the respective service and add its credentials using the information in the OAuth client JSON file from step 6.\n",
+        "excerpt": "# Hosting n8n on Google Cloud Run  This hosting guide shows you how to self-host n8n on Google Cloud Run, a serverless container runtime. If you're just getting started with n8n and don't need a production-grade deployment, you can go with the \"easy mode\" option below for deployment. Otherwise, if you intend to use this n8n deployment at-scale, refer to the \"durable mode\" instructions further down.  You can also enable access via OAuth to Google Workspace, such as Gmail and Drive, to use these s...",
         "sections": [
           {
-            "title": "Hosting n8n on Google Kubernetes Engine",
+            "title": "Hosting n8n on Google Cloud Run",
             "level": 1,
-            "content": "Google Cloud offers several options suitable for hosting n8n, including Cloud Run (optimized for running containers), Compute Engine (VMs), and Kubernetes Engine (containers running with Kubernetes).\n\nThis guide uses the Google Kubernetes Engine (GKE) as the hosting option. If you want to use Cloud Run, refer to [these instructions](../google-cloud-run/).\n\nMost of the steps in this guide use the Google Cloud UI, but you can also use the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/) instead to undertake all the steps."
+            "content": "This hosting guide shows you how to self-host n8n on Google Cloud Run, a serverless container runtime. If you're just getting started with n8n and don't need a production-grade deployment, you can go with the \"easy mode\" option below for deployment. Otherwise, if you intend to use this n8n deployment at-scale, refer to the \"durable mode\" instructions further down.\n\nYou can also enable access via OAuth to Google Workspace, such as Gmail and Drive, to use these services as n8n workflow tools. Instructions for granting n8n access to these services are at the end of of this documentation.\n\nIf you want to deploy to Google Kubernetes Engine (GKE) instead, you can refer to [these instructions](../google-kubernetes-engine/).\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-hos"
           }
         ]
       },
@@ -17336,65 +17337,182 @@
         ],
         "useCases": [],
         "operations": [],
-        "codeExamples": 10,
+        "codeExamples": 16,
         "complexity": "intermediate",
-        "readingTime": "8 min",
-        "contentLength": 12158,
+        "readingTime": "9 min",
+        "contentLength": 12168,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "google cloud run # hosting n8n on google kubernetes engine\n\ngoogle cloud offers several options suitable for hosting n8n, including cloud run (optimized for running containers), compute engine (vms), and kubernetes engine (containers running with kubernetes).\n\nthis guide uses the google kubernetes engine (gke) as the hosting option. if you want to use cloud run, refer to [these instructions](../google-cloud-run/).\n\nmost of the steps in this guide use the google cloud ui, but you can also use the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/) instead to undertake all the steps.\n\n## prerequisites\n\n- the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/)\n- the [gke-gcloud-auth-plugin](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke) (install the gcloud cli first)\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.15.0 current `beta`: 2.16.0\n\n## create project\n\ngcp encourages you to create projects to logically organize resources and configuration. create a new project for your n8n deployment from your google cloud console: select the project dropdown menu and then the **new project** button. then select the newly created project. as you follow the other steps in this guide, make sure you have the correct project selected.\n\n## enable the kubernetes engine api\n\ngke isn't enabled by default. search for \"kubernetes\" in the top search bar and select \"kubernetes engine\" from the results.\n\nselect **enable** to enable the kubernetes engine api for this project.\n\n## create a cluster\n\nfrom the [gke service page](https://console.cloud.google.com/kubernetes/list/overview), select **clusters** > **create**. make sure you select the \"standard\" cluster option, n8n doesn't work with an \"autopilot\" cluster. you can leave the cluster configuration on defaults unless there's anything specifically you need to change, such as location.\n\n## set kubectl context\n\nthe rest of the steps in this guide require you to set the gcp instance as the kubectl context. you can find the connection details for a cluster instance by opening its details page and selecting **connect**. the displayed code snippet shows a connection string for the gcloud cli tool. paste and run the code snippet in the gcloud cli to change your local kubernetes settings to use the new gcloud 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) locally. the following steps explain the file configuration and how to add your information.\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### create a volume for persistent storage\n\nto maintain data between pod restarts, the postgres deployment needs a persistent volume. running postgres on gcp requires a specific kubernetes storage class. you can read [this guide](https://cloud.google.com/architecture/deploying-highly-available-postgresql-with-gke) for specifics, but the `storage.yaml` manifest creates it for you. you may want to change the regions to create the storage in under the `allowedtopologies` > `matchedlabelexpressions` > `values` key. by default, they're set to `us-central`.\n\n```\n…\nallowedtopologies:\n  - matchlabelexpressions:\n      - key: failure-domain.beta.kubernetes.io/zone\n        values:\n          - us-central1-b\n          - us-central1-c\n```\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` and `postgres-deployment.yaml` files:\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 & ingress** menu item of the cluster you want to use under the **endpoints** column.\n\ngke and ip addresses\n\n[read this gke tutorial](https://cloud.google.com/kubernetes-engine/docs/tutorials/configuring-domain-name-static-ip#configuring_your_domain_name_records) for more details on how reserved ip addresses work with gke and kubernetes resources.\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/).\nated \\\n    --port=5678 \\\n    --memory=2gi \\\n    --no-cpu-throttling \\\n    --set-env-vars=\"n8n_port=5678,n8n_protocol=https,n8n_endpoint_health=health,db_type=postgresdb,db_postgresdb_database=n8n,db_postgresdb_user=n8n-user,db_postgresdb_host=/cloudsql/$project_id:$region:n8n-db,db_postgresdb_port=5432,db_postgresdb_schema=public,generic_timezone=utc,queue_health_check_active=true\" \\\n    --set-secrets=\"db_postgresdb_password=n8n-db-password:latest,n8n_encryption_key=n8n-encryption-key:latest\" \\\n    --add-cloudsql-instances=$project_id:$region:n8n-db \\\n    --service-account=n8n-service-account@$project_id.iam.gserviceaccount.com\n```\n\nonce the deployment finishes, open another tab to navigate to the service url. you should see the n8n login screen.\n\n## troubleshooting\n\nif you see a \"cannot get /\" screen this usually indicates that n8n is still starting up. you can refresh the page and it should eventually load.\n\n## (optional) enabling google workspace services as n8n tools\n\nif you want to use google workspace services (gmail, calendar, drive, etc.) as tools in n8n, it's recommended to setup oauth to access these services.\n\nfirst ensure the respective apis you want are enabled:\n\n```\n## enable whichever apis you need\n## note: if you want sheets/docs, it's not enough to just enable drive; these services each have",
+        "fullText": "google cloud run # hosting n8n on google cloud run\n\nthis hosting guide shows you how to self-host n8n on google cloud run, a serverless container runtime. if you're just getting started with n8n and don't need a production-grade deployment, you can go with the \"easy mode\" option below for deployment. otherwise, if you intend to use this n8n deployment at-scale, refer to the \"durable mode\" instructions further down.\n\nyou can also enable access via oauth to google workspace, such as gmail and drive, to use these services as n8n workflow tools. instructions for granting n8n access to these services are at the end of of this documentation.\n\nif you want to deploy to google kubernetes engine (gke) instead, you can refer to [these instructions](../google-kubernetes-engine/).\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.15.0 current `beta`: 2.16.0\n\n## before you begin: get a google cloud project\n\nif you have not yet created a google cloud project, [do this first](https://developers.google.com/workspace/guides/create-project) (and ensure you have billing enabled on the project; even if your cloud run service runs for free you must have billing activated to deploy). otherwise, navigate to the project where you want to deploy n8n.\n\n## easy mode\n\nthis is the fastest way to deploy n8n on cloud run. for this deployment, n8n's data is in-memory so this is only recommended for demo purposes. **anytime this cloud run service scales to zero or is redeployed, the n8n data will be lost.** refer to the durable mode instructions below if you need a production-grade deployment.\n\nif you have not yet created a google cloud project, [do this first](https://developers.google.com/workspace/guides/create-project) (and ensure you have billing enabled on the project; even if your cloud run service will run for free you must have billing enabled to activated to deploy). otherwise, navigate to the project where you want to deploy n8n.\n\nopen the cloud shell terminal (on the google cloud console, either type \"g\" then \"s\" or click on the terminal icon on the upper right).\n\nonce your session is open, you may need to run this command first to login (and follow the steps it asks you to complete):\n\n```\ngcloud auth login\n```\n\nyou can also explicitly enable the cloud run api (even if you don't do this, it will ask if you want this enabled when you deploy):\n\n```\ngcloud services enable run.googleapis.com\n```\n\nrequired: custom health check endpoint\n\ngoogle cloud run reserves `/healthz` for its own health checks. since n8n uses this path by default, it can conflict and cause connection issues in the workflow canvas. to fix this, set the `n8n_endpoint_health` environment variable to a custom path (included in the deployment commands below).\n\nto deploy n8n:\n\n```\ngcloud run deploy n8n \\\n    --image=n8nio/n8n \\\n    --region=us-west1 \\\n    --allow-unauthenticated \\\n    --port=5678 \\\n    --no-cpu-throttling \\\n    --memory=2gi \\\n    --set-env-vars=\"n8n_endpoint_health=health\"\n```\n\n(you can specify whichever region you prefer, instead of \"us-west1\")\n\nonce the deployment finishes, open another tab to navigate to the service url. n8n may still be loading and you will see a \"n8n is starting up. please wait\" message, but shortly thereafter you should see the n8n login screen.\n\noptional: if you want to keep this n8n service running for as long as possible to avoid data loss, you can also set manual scale to 1 to prevent it from autoscaling to 0.\n\n```\ngcloud run deploy n8n \\\n    --image=n8nio/n8n \\\n    --region=us-west1 \\\n    --allow-unauthenticated \\\n    --port=5678 \\\n    --no-cpu-throttling \\\n    --memory=2gi \\\n    --scaling=1 \\\n    --set-env-vars=\"n8n_endpoint_health=health\"\n```\n\nthis does not prevent data loss completely, such as whenever the cloud run service is re-deployed/updated. if you want truly persistant data, you should refer to the instructions below for how to attach a database.\n\n## durable mode\n\nthe following instructions are intended for a more durable, production-grade deployment of n8n on cloud run. it includes resources such as a database for persistance and secret manager for sensitive data.\n\nif you want to deploy the following setup via terraform, refer to this [example](https://github.com/ryanpei/n8n-hosting/tree/main/google-cloud-run) which deploys the same setup as the following (without the oauth setup for google workspace tools).\n\n## enable apis and set env vars\n\nopen the cloud shell terminal (on the google cloud console, either type \"g\" then \"s\" or click on the terminal icon on the upper right) and run these commands in the terminal session:\n\n```\n## you may need to login first\ngcloud auth login\n\ngcloud services enable run.googleapis.com\ngcloud services enable sqladmin.googleapis.com\ngcloud services enable secretmanager.googleapis.com\n```\n\nyou'll also want to set some environment variables for the remainder of these instructions:\n\n```\nexport project_id=your-project\nexport region=region-where-you-want-this-deployed\n```\n\n## setup your postgres database\n\nrun this command to create the postgres db instance (it will take a few minutes to complete; also ensure you update the root-password field with your own desired password):\n\n```\ngcloud sql instances create n8n-db \\\n    --database-version=postgres_13 \\\n    --tier=db-f1-micro \\\n    --region=$region \\\n    --root-password=\"change-this-password\" \\\n    --storage-size=10gb \\\n    --availability-type=zonal \\\n    --no-backup \\\n    --storage-type=hdd\n```\n\nonce complete, you can add the database that n8n will use:\n\n```\ngcloud sql databases create n8n --instance=n8n-db\n```\n\ncreate the db user for n8n (change the password value, of course):\n\n```\ngcloud sql users create n8n-user \\\n    --instance=n8n-db \\\n    --password=\"change-this-password\"\n```\n\nyou can save the password you set for this n8n-user to a file for the next step of saving the password in secret manager. be sure to delete this file later.\n\n## store sensitive data in secret manager\n\nwhile not required, it's absolutely recommended to store your sensitive data in secrets manager.\n\ncreate a secret for the database password (replace \"/your/password/file\" with the file you created above for the n8n-user password):\n\n```\ngcloud secrets create n8n-db-password \\\n    --data-file=/your/password/file \\\n    --replication-policy=\"automatic\"\n```\n\ncreate an encryption key (you can use your own, this example generates a random one):\n\n```\nopenssl rand -base64 -out my-encryption-key 42\n```\n\ncreate a secret for this encryption key (replace \"my-encryption-key\" if you are supplying your own):\n\n```\ngcloud secrets create n8n-encryption-key \\\n    --data-file=my-encryption-key \\\n    --replication-policy=\"automatic\"\n```\n\nnow you can delete my-encryption-key and the database password files you created. these values are now securely stored in secret manager.\n\n## create a service account for cloud run\n\nyou want this cloud run service to be restricted to access only the resources it needs. the following commands create the service account and adds the permissions necessary to access secrets and the database:\n\n```\ngcloud iam service-accounts create n8n-service-account \\\n    --display-name=\"n8n service account\"\n\ngcloud secrets add-iam-policy-binding n8n-db-password \\\n    --member=\"serviceaccount:n8n-service-account@$project_id.iam.gserviceaccount.com\" \\\n    --role=\"roles/secretmanager.secretaccessor\"\n\ngcloud secrets add-iam-policy-binding n8n-encryption-key \\\n    --member=\"serviceaccount:n8n-service-account@$project_id.iam.gserviceaccount.com\" \\\n    --role=\"roles/secretmanager.secretaccessor\"\n\ngcloud projects add-iam-policy-binding $project_id \\\n    --member=\"serviceaccount:n8n-service-account@$project_id.iam.gserviceaccount.com\" \\\n    --role=\"roles/cloudsql.client\"\n```\n\n## deploy the cloud run service\n\nnow you can deploy your n8n service:\n\n```\ngcloud run deploy n8n \\\n    --image=n8nio/n8n:latest \\\n    --command=\"/bin/sh\" \\\n    --args=\"-c,sleep 5;n8n start\" \\\n    --region=$region \\\n    --allow-unauthenticated \\\n    --port=5678 \\\n    --memory=2gi \\\n    --no-cpu-throttling \\\n    --set-env-vars=\"n8n_port=5678,n8n_protocol=https,n8n_endpoint_health=health,db_type=postgresdb,db_postgresdb_database=n8n,db_postgresdb_user=n8n-user,db_postgresdb_host=/cloudsql/$project_id:$region:n8n-db,db_postgresdb_port=5432,db_postgresdb_schema=public,generic_timezone=utc,queue_health_check_active=true\" \\\n    --set-secrets=\"db_postgresdb_password=n8n-db-password:latest,n8n_encryption_key=n8n-encryption-key:latest\" \\\n    --add-cloudsql-instances=$project_id:$region:n8n-db \\\n    --service-account=n8n-service-account@$project_id.iam.gserviceaccount.com\n```\n\nonce the deployment finishes, open another tab to navigate to the service url. you should see the n8n login screen.\n\n## troubleshooting\n\nif you see a \"cannot get /\" screen this usually indicates that n8n is still starting up. you can refresh the page and it should eventually load.\n\n## (optional) enabling google workspace services as n8n tools\n\nif you want to use google workspace services (gmail, calendar, drive, etc.) as tools in n8n, it's recommended to setup oauth to access these services.\n\nfirst ensure the respective apis you want are enabled:\n\n```\n## enable whichever apis you need\n## note: if you want sheets/docs, it's not enough to just enable drive; these services",
         "importantTerms": [
-          "kubernetes",
-          "google",
-          "cloud",
-          "https",
           "this",
+          "cloud",
+          "service",
           "gcloud",
+          "google",
           "services",
-          "yaml",
-          "with",
-          "resources",
           "your",
-          "service",
-          "postgres",
+          "password",
+          "create",
+          "enable",
+          "deploy",
+          "want",
+          "region",
+          "data",
+          "https",
+          "these",
+          "project",
+          "googleapis",
+          "access",
+          "file",
           "deployment",
+          "have",
+          "encryption",
+          "account",
+          "workspace",
+          "database",
+          "hosting",
+          "need",
+          "instructions",
+          "oauth",
+          "will",
+          "secret",
+          "setup",
+          "user",
+          "secrets",
+          "also",
+          "click",
+          "login",
+          "with",
+          "mode",
+          "refer",
+          "drive",
+          "created",
+          "first",
+          "enabled",
+          "open",
+          "terminal",
+          "type",
+          "auth",
+          "health"
+        ]
+      }
+    },
+    {
+      "id": "page-0205",
+      "title": "Google Kubernetes Engine",
+      "url": "https://docs.n8n.io/hosting/installation/server-setups/google-kubernetes-engine/index.md",
+      "urlPath": "hosting/installation/server-setups/google-kubernetes-engine/index.md",
+      "category": "hosting",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Hosting n8n on Google Kubernetes Engine\n\nGoogle Cloud offers several options suitable for hosting n8n, including Cloud Run (optimized for running containers), Compute Engine (VMs), and Kubernetes Engine (containers running with Kubernetes).\n\nThis guide uses the Google Kubernetes Engine (GKE) as the hosting option. If you want to use Cloud Run, refer to [these instructions](../google-cloud-run/).\n\nMost of the steps in this guide use the Google Cloud UI, but you can also use the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/) instead to undertake all the steps.\n\n## Prerequisites\n\n- The [gcloud command line tool](https://cloud.google.com/sdk/gcloud/)\n- The [gke-gcloud-auth-plugin](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke) (install the gcloud CLI first)\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.15.0 Current `beta`: 2.16.0\n\n## Create project\n\nGCP encourages you to create projects to logically organize resources and configuration. Create a new project for your n8n deployment from your Google Cloud Console: select the project dropdown menu and then the **NEW PROJECT** button. Then select the newly created project. As you follow the other steps in this guide, make sure you have the correct project selected.\n\n## Enable the Kubernetes Engine API\n\nGKE isn't enabled by default. Search for \"Kubernetes\" in the top search bar and select \"Kubernetes Engine\" from the results.\n\nSelect **ENABLE** to enable the Kubernetes Engine API for this project.\n\n## Create a cluster\n\nFrom the [GKE service page](https://console.cloud.google.com/kubernetes/list/overview), select **Clusters** > **CREATE**. Make sure you select the \"Standard\" cluster option, n8n doesn't work with an \"Autopilot\" cluster. You can leave the cluster configuration on defaults unless there's anything specifically you need to change, such as location.\n\n## Set Kubectl context\n\nThe rest of the steps in this guide require you to set the GCP instance as the Kubectl context. You can find the connection details for a cluster instance by opening its details page and selecting **CONNECT**. The displayed code snippet shows a connection string for the gcloud CLI tool. Paste and run the code snippet in the gcloud CLI to change your local Kubernetes settings to use the new gcloud 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) locally. The following steps explain the file configuration and how to add your information.\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### Create a volume for persistent storage\n\nTo maintain data between pod restarts, the Postgres deployment needs a persistent volume. Running Postgres on GCP requires a specific Kubernetes Storage Class. You can read [this guide](https://cloud.google.com/architecture/deploying-highly-available-postgresql-with-gke) for specifics, but the `storage.yaml` manifest creates it for you. You may want to change the regions to create the storage in under the `allowedTopologies` > `matchedLabelExpressions` > `values` key. By default, they're set to `us-central`.\n\n```\n…\nallowedTopologies:\n  - matchLabelExpressions:\n      - key: failure-domain.beta.kubernetes.io/zone\n        values:\n          - us-central1-b\n          - us-central1-c\n```\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` and `postgres-deployment.yaml` files:\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 & Ingress** menu item of the cluster you want to use under the **Endpoints** column.\n\nGKE and IP addresses\n\n[Read this GKE tutorial](https://cloud.google.com/kubernetes-engine/docs/tutorials/configuring-domain-name-static-ip#configuring_your_domain_name_records) for more details on how reserved IP addresses work with GKE and Kubernetes resources.\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 Google Kubernetes Engine  Google Cloud offers several options suitable for hosting n8n, including Cloud Run (optimized for running containers), Compute Engine (VMs), and Kubernetes Engine (containers running with Kubernetes).  This guide uses the Google Kubernetes Engine (GKE) as the hosting option. If you want to use Cloud Run, refer to [these instructions](../google-cloud-run/).  Most of the steps in this guide use the Google Cloud UI, but you can also use the [gcloud command...",
+        "sections": [
+          {
+            "title": "Hosting n8n on Google Kubernetes Engine",
+            "level": 1,
+            "content": "Google Cloud offers several options suitable for hosting n8n, including Cloud Run (optimized for running containers), Compute Engine (VMs), and Kubernetes Engine (containers running with Kubernetes).\n\nThis guide uses the Google Kubernetes Engine (GKE) as the hosting option. If you want to use Cloud Run, refer to [these instructions](../google-cloud-run/).\n\nMost of the steps in this guide use the Google Cloud UI, but you can also use the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/) instead to undertake all the steps."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "google",
+          "kubernetes",
+          "engine",
+          "hosting",
+          "prerequisites",
           "create",
+          "project",
           "enable",
+          "cluster",
+          "kubectl",
+          "context",
+          "clone",
+          "configuration",
+          "repository",
+          "configure",
+          "postgres",
+          "volume",
+          "persistent",
+          "storage",
           "environment",
           "variables",
-          "hosting",
           "file",
+          "resources",
+          "optional:",
+          "deployments",
+          "services",
+          "send",
+          "delete",
+          "next",
+          "steps"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 8,
+        "complexity": "intermediate",
+        "readingTime": "6 min",
+        "contentLength": 8654,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "google kubernetes engine # hosting n8n on google kubernetes engine\n\ngoogle cloud offers several options suitable for hosting n8n, including cloud run (optimized for running containers), compute engine (vms), and kubernetes engine (containers running with kubernetes).\n\nthis guide uses the google kubernetes engine (gke) as the hosting option. if you want to use cloud run, refer to [these instructions](../google-cloud-run/).\n\nmost of the steps in this guide use the google cloud ui, but you can also use the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/) instead to undertake all the steps.\n\n## prerequisites\n\n- the [gcloud command line tool](https://cloud.google.com/sdk/gcloud/)\n- the [gke-gcloud-auth-plugin](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke) (install the gcloud cli first)\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.15.0 current `beta`: 2.16.0\n\n## create project\n\ngcp encourages you to create projects to logically organize resources and configuration. create a new project for your n8n deployment from your google cloud console: select the project dropdown menu and then the **new project** button. then select the newly created project. as you follow the other steps in this guide, make sure you have the correct project selected.\n\n## enable the kubernetes engine api\n\ngke isn't enabled by default. search for \"kubernetes\" in the top search bar and select \"kubernetes engine\" from the results.\n\nselect **enable** to enable the kubernetes engine api for this project.\n\n## create a cluster\n\nfrom the [gke service page](https://console.cloud.google.com/kubernetes/list/overview), select **clusters** > **create**. make sure you select the \"standard\" cluster option, n8n doesn't work with an \"autopilot\" cluster. you can leave the cluster configuration on defaults unless there's anything specifically you need to change, such as location.\n\n## set kubectl context\n\nthe rest of the steps in this guide require you to set the gcp instance as the kubectl context. you can find the connection details for a cluster instance by opening its details page and selecting **connect**. the displayed code snippet shows a connection string for the gcloud cli tool. paste and run the code snippet in the gcloud cli to change your local kubernetes settings to use the new gcloud 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) locally. the following steps explain the file configuration and how to add your information.\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### create a volume for persistent storage\n\nto maintain data between pod restarts, the postgres deployment needs a persistent volume. running postgres on gcp requires a specific kubernetes storage class. you can read [this guide](https://cloud.google.com/architecture/deploying-highly-available-postgresql-with-gke) for specifics, but the `storage.yaml` manifest creates it for you. you may want to change the regions to create the storage in under the `allowedtopologies` > `matchedlabelexpressions` > `values` key. by default, they're set to `us-central`.\n\n```\n…\nallowedtopologies:\n  - matchlabelexpressions:\n      - key: failure-domain.beta.kubernetes.io/zone\n        values:\n          - us-central1-b\n          - us-central1-c\n```\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` and `postgres-deployment.yaml` files:\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 & ingress** menu item of the cluster you want to use under the **endpoints** column.\n\ngke and ip addresses\n\n[read this gke tutorial](https://cloud.google.com/kubernetes-engine/docs/tutorials/configuring-domain-name-static-ip#configuring_your_domain_name_records) for more details on how reserved ip addresses work with gke and kubernetes resources.\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 google kubernetes engine",
+        "importantTerms": [
+          "kubernetes",
+          "cloud",
+          "google",
+          "yaml",
+          "this",
+          "resources",
+          "postgres",
+          "with",
+          "https",
+          "deployment",
           "engine",
-          "these",
+          "hosting",
+          "create",
+          "environment",
+          "variables",
+          "gcloud",
           "configuration",
-          "select",
           "cluster",
-          "want",
-          "project",
+          "your",
           "containers",
-          "steps",
           "command",
-          "application",
-          "from",
+          "project",
           "following",
-          "using",
-          "googleapis",
+          "file",
           "guide",
+          "steps",
           "kubectl",
-          "need",
+          "from",
+          "select",
+          "service",
           "change",
           "storage",
           "manifest",
           "values",
+          "using",
           "manifests",
-          "access",
           "running",
-          "auth",
+          "application",
           "beta",
           "details",
           "volumes",
-          "define"
+          "define",
+          "want",
+          "these",
+          "configuring",
+          "scaling",
+          "clone",
+          "files",
+          "needs",
+          "send"
         ]
       }
     },
@@ -40127,7 +40245,7 @@
       "nodeName": "supabase",
       "nodeType": "n8n-nodes-base.supabase",
       "content": {
-        "markdown": "# Supabase node\n\nUse the Supabase node to automate work in Supabase, and integrate Supabase with other applications. n8n has built-in support for a wide range of Supabase features, including creating, deleting, and getting rows.\n\nOn this page, you'll find a list of operations the Supabase node supports and links to more resources.\n\nCredentials\n\nRefer to [Supabase credentials](../../credentials/supabase/) for guidance on setting up authentication.\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## Operations\n\n- Row\n  - Create a new row\n  - Delete a row\n  - Get a row\n  - Get all rows\n  - Update a row\n\n## Using custom schemas\n\nBy default, the Supabase node only fetches the `public` schema. To fetch [custom schemas](https://supabase.com/docs/guides/api/using-custom-schemas), enable **Use Custom Schema**.\n\nIn the new **Schema** field, provide the custom schema the Supabase node should use.\n\n## Templates and examples\n\n**AI Agent To Chat With Files In Supabase Storage**\n\nby Mark Shcherbakov\n\n[View template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**Autonomous AI crawler**\n\nby Oskar\n\n[View template details](https://n8n.io/workflows/2315-autonomous-ai-crawler/)\n\n**🤖 Create a Documentation Expert Bot with RAG, Gemini, and Supabase**\n\nby Lucas Peyrin\n\n[View template details](https://n8n.io/workflows/5993-create-a-documentation-expert-bot-with-rag-gemini-and-supabase/)\n\n[Browse Supabase integration templates](https://n8n.io/integrations/supabase/), or [search all templates](https://n8n.io/workflows/)\n\n## What to do if your operation isn't supported\n\nIf this node doesn't support the operation you want to do, you can use the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's API.\n\nYou can use the credential you created for this service in the HTTP Request node:\n\n1. In the HTTP Request node, select **Authentication** > **Predefined Credential Type**.\n1. Select the service you want to connect to.\n1. Select your credential.\n\nRefer to [Custom API operations](../../../custom-operations/) for more information.\n\n## Common issues\n\nFor common errors or issues and suggested resolution steps, refer to [Common issues](common-issues/).\n",
+        "markdown": "# Supabase node\n\nUse the Supabase node to automate work in Supabase, and integrate Supabase with other applications. n8n has built-in support for a wide range of Supabase features, including creating, deleting, and getting rows.\n\nOn this page, you'll find a list of operations the Supabase node supports and links to more resources.\n\nCredentials\n\nRefer to [Supabase credentials](../../credentials/supabase/) for guidance on setting up authentication.\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## Operations\n\n- Row\n  - Create a new row\n  - Delete a row\n  - Get a row\n  - Get all rows\n  - Update a row\n\n## Using custom schemas\n\nBy default, the Supabase node only fetches the `public` schema. To fetch [custom schemas](https://supabase.com/docs/guides/api/using-custom-schemas), enable **Use Custom Schema**.\n\nIn the new **Schema** field, provide the custom schema the Supabase node should use.\n\n## Templates and examples\n\n**AI Agent To Chat With Files In Supabase Storage**\n\nby Mark Shcherbakov\n\n[View template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**Autonomous AI crawler**\n\nby Oskar\n\n[View template details](https://n8n.io/workflows/2315-autonomous-ai-crawler/)\n\n**Automate sales cold calling pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n[Browse Supabase integration templates](https://n8n.io/integrations/supabase/), or [search all templates](https://n8n.io/workflows/)\n\n## What to do if your operation isn't supported\n\nIf this node doesn't support the operation you want to do, you can use the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's API.\n\nYou can use the credential you created for this service in the HTTP Request node:\n\n1. In the HTTP Request node, select **Authentication** > **Predefined Credential Type**.\n1. Select the service you want to connect to.\n1. Select your credential.\n\nRefer to [Custom API operations](../../../custom-operations/) for more information.\n\n## Common issues\n\nFor common errors or issues and suggested resolution steps, refer to [Common issues](common-issues/).\n",
         "excerpt": "# Supabase node  Use the Supabase node to automate work in Supabase, and integrate Supabase with other applications. n8n has built-in support for a wide range of Supabase features, including creating, deleting, and getting rows.  On this page, you'll find a list of operations the Supabase node supports and links to more resources.  Credentials  Refer to [Supabase credentials](../../credentials/supabase/) for guidance on setting up authentication.  This node can be used as an AI tool  This node c...",
         "sections": [
           {
@@ -40163,11 +40281,11 @@
         "codeExamples": 0,
         "complexity": "intermediate",
         "readingTime": "2 min",
-        "contentLength": 2511,
+        "contentLength": 2522,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "supabase # supabase node\n\nuse the supabase node to automate work in supabase, and integrate supabase with other applications. n8n has built-in support for a wide range of supabase features, including creating, deleting, and getting rows.\n\non this page, you'll find a list of operations the supabase node supports and links to more resources.\n\ncredentials\n\nrefer to [supabase credentials](../../credentials/supabase/) for guidance on setting up authentication.\n\nthis node can be used as an ai tool\n\nthis node can be used to enhance the capabilities of an ai agent. when used in this way, many parameters can be set automatically, or with information directed by ai - find out more in the [ai tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## operations\n\n- row\n  - create a new row\n  - delete a row\n  - get a row\n  - get all rows\n  - update a row\n\n## using custom schemas\n\nby default, the supabase node only fetches the `public` schema. to fetch [custom schemas](https://supabase.com/docs/guides/api/using-custom-schemas), enable **use custom schema**.\n\nin the new **schema** field, provide the custom schema the supabase node should use.\n\n## templates and examples\n\n**ai agent to chat with files in supabase storage**\n\nby mark shcherbakov\n\n[view template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**autonomous ai crawler**\n\nby oskar\n\n[view template details](https://n8n.io/workflows/2315-autonomous-ai-crawler/)\n\n**🤖 create a documentation expert bot with rag, gemini, and supabase**\n\nby lucas peyrin\n\n[view template details](https://n8n.io/workflows/5993-create-a-documentation-expert-bot-with-rag-gemini-and-supabase/)\n\n[browse supabase integration templates](https://n8n.io/integrations/supabase/), or [search all templates](https://n8n.io/workflows/)\n\n## what to do if your operation isn't supported\n\nif this node doesn't support the operation you want to do, you can use the [http request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's api.\n\nyou can use the credential you created for this service in the http request node:\n\n1. in the http request node, select **authentication** > **predefined credential type**.\n1. select the service you want to connect to.\n1. select your credential.\n\nrefer to [custom api operations](../../../custom-operations/) for more information.\n\n## common issues\n\nfor common errors or issues and suggested resolution steps, refer to [common issues](common-issues/).\n supabase node",
+        "fullText": "supabase # supabase node\n\nuse the supabase node to automate work in supabase, and integrate supabase with other applications. n8n has built-in support for a wide range of supabase features, including creating, deleting, and getting rows.\n\non this page, you'll find a list of operations the supabase node supports and links to more resources.\n\ncredentials\n\nrefer to [supabase credentials](../../credentials/supabase/) for guidance on setting up authentication.\n\nthis node can be used as an ai tool\n\nthis node can be used to enhance the capabilities of an ai agent. when used in this way, many parameters can be set automatically, or with information directed by ai - find out more in the [ai tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## operations\n\n- row\n  - create a new row\n  - delete a row\n  - get a row\n  - get all rows\n  - update a row\n\n## using custom schemas\n\nby default, the supabase node only fetches the `public` schema. to fetch [custom schemas](https://supabase.com/docs/guides/api/using-custom-schemas), enable **use custom schema**.\n\nin the new **schema** field, provide the custom schema the supabase node should use.\n\n## templates and examples\n\n**ai agent to chat with files in supabase storage**\n\nby mark shcherbakov\n\n[view template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**autonomous ai crawler**\n\nby oskar\n\n[view template details](https://n8n.io/workflows/2315-autonomous-ai-crawler/)\n\n**automate sales cold calling pipeline with apify, gpt-4o, and whatsapp**\n\nby khairul muhtadin\n\n[view template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n[browse supabase integration templates](https://n8n.io/integrations/supabase/), or [search all templates](https://n8n.io/workflows/)\n\n## what to do if your operation isn't supported\n\nif this node doesn't support the operation you want to do, you can use the [http request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's api.\n\nyou can use the credential you created for this service in the http request node:\n\n1. in the http request node, select **authentication** > **predefined credential type**.\n1. select the service you want to connect to.\n1. select your credential.\n\nrefer to [custom api operations](../../../custom-operations/) for more information.\n\n## common issues\n\nfor common errors or issues and suggested resolution steps, refer to [common issues](common-issues/).\n supabase node",
         "importantTerms": [
           "supabase",
           "node",
@@ -40180,14 +40298,13 @@
           "workflows",
           "common",
           "issues",
+          "automate",
           "more",
           "credentials",
           "refer",
           "used",
           "agent",
-          "documentation",
           "using",
-          "create",
           "schemas",
           "templates",
           "view",
@@ -43582,7 +43699,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Supabase Vector Store node\n\nUse the Supabase Vector Store to interact with your Supabase database as vector store. You can insert documents into a vector database, get many documents from a vector database, and retrieve documents to provide them to a retriever connected to a chain.\n\nUse the Supabase Vector Store to interact with your Supabase database as [vector store](../../../../../glossary/#ai-vector-store). You can insert documents into a vector database, get documents from a vector database, retrieve documents to provide them to a retriever connected to a [chain](../../../../../glossary/#ai-chain), or connect it directly to an [agent](../../../../../glossary/#ai-agent) to use as a [tool](../../../../../glossary/#ai-tool). You can also update an item in a vector store by its ID.\n\nOn this page, you'll find the node parameters for the Supabase node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/supabase/).\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\nSupabase provides a [quickstart for setting up your vector store](https://supabase.com/docs/guides/ai/langchain?database-method=sql). If you use settings other than the defaults in the quickstart, this may affect parameter settings in n8n. Make sure you understand what you're doing.\n\n## Node usage patterns\n\nYou can use the Supabase Vector Store node in the following patterns.\n\n### Use as a regular node to insert, update, and retrieve documents\n\nYou can use the Supabase Vector Store as a regular node to insert, update, or get documents. This pattern places the Supabase Vector Store in the regular connection flow without using an agent.\n\nYou can see an example of this in scenario 1 of [this template](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/).\n\n### Connect directly to an AI agent as a tool\n\nYou can connect the Supabase Vector Store node directly to the tool connector of an [AI agent](../n8n-nodes-langchain.agent/) to use a vector store as a resource when answering queries.\n\nHere, the connection would be: AI agent (tools connector) -> Supabase Vector Store node.\n\n### Use a retriever to fetch documents\n\nYou can use the [Vector Store Retriever](../../sub-nodes/n8n-nodes-langchain.retrievervectorstore/) node with the Supabase Vector Store node to fetch documents from the Supabase Vector Store node. This is often used with the [Question and Answer Chain](../n8n-nodes-langchain.chainretrievalqa/) node to fetch documents from the vector store that match the given chat input.\n\nAn [example of the connection flow](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/) (the example uses Pinecone, but the pattern in the same) would be: Question and Answer Chain (Retriever connector) -> Vector Store Retriever (Vector Store connector) -> Supabase Vector Store.\n\n### Use the Vector Store Question Answer Tool to answer questions\n\nAnother pattern uses the [Vector Store Question Answer Tool](../../sub-nodes/n8n-nodes-langchain.toolvectorstore/) to summarize results and answer questions from the Supabase Vector Store node. Rather than connecting the Supabase Vector Store directly as a tool, this pattern uses a tool specifically designed to summarizes data in the vector store.\n\nThe [connections flow](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/) in this case would look like this: AI agent (tools connector) -> Vector Store Question Answer Tool (Vector Store connector) -> Supabase Vector store.\n\n## Node parameters\n\n### Operation Mode\n\nThis Vector Store node has five modes: **Get Many**, **Insert Documents**, **Retrieve Documents (As Vector Store for Chain/Tool)**, **Retrieve Documents (As Tool for AI Agent)**, and **Update Documents**. The mode you select determines the operations you can perform with the node and what inputs and outputs are available.\n\n#### Get Many\n\nIn this mode, you can retrieve multiple documents from your vector database by providing a prompt. The prompt will be embedded and used for similarity search. The node will return the documents that are most similar to the prompt with their similarity score. This is useful if you want to retrieve a list of similar documents and pass them to an agent as additional context.\n\n#### Insert Documents\n\nUse Insert Documents mode to insert new documents into your vector database.\n\n#### Retrieve Documents (As Vector Store for Chain/Tool)\n\nUse Retrieve Documents (As Vector Store for Chain/Tool) mode with a vector-store retriever to retrieve documents from a vector database and provide them to the retriever connected to a chain. In this mode you must connect the node to a retriever node or root node.\n\n#### Retrieve Documents (As Tool for AI Agent)\n\nUse Retrieve Documents (As Tool for AI Agent) mode to use the vector store as a tool resource when answering queries. When formulating responses, the agent uses the vector store when the vector store name and description match the question details.\n\n#### Update Documents\n\nUse Update Documents mode to update documents in a vector database by ID. Fill in the **ID** with the ID of the embedding entry to update.\n\n### Rerank Results\n\nEnables [reranking](../../../../../glossary/#ai-reranking). If you enable this option, you must connect a reranking node to the vector store. That node will then rerank the results for queries. You can use this option with the `Get Many`, `Retrieve Documents (As Vector Store for Chain/Tool)` and `Retrieve Documents (As Tool for AI Agent)` modes.\n\n### Get Many parameters\n\n- **Table Name**: Enter the Supabase table to use.\n- **Prompt**: Enter the search query.\n- **Limit**: Enter how many results to retrieve from the vector store. For example, set this to `10` to get the ten best results.\n\n### Insert Documents parameters\n\n- **Table Name**: Enter the Supabase table to use.\n\n### Retrieve Documents (As Vector Store for Chain/Tool) parameters\n\n- **Table Name**: Enter the Supabase table to use.\n\n### Retrieve Documents (As Tool for AI Agent) parameters\n\n- **Name**: The name of the vector store.\n- **Description**: Explain to the LLM what this tool does. A good, specific description allows LLMs to produce expected results more often.\n- **Table Name**: Enter the Supabase table to use.\n- **Limit**: Enter how many results to retrieve from the vector store. For example, set this to `10` to get the ten best results.\n\n### Update Documents\n\n- **Table Name**: Enter the Supabase table to use.\n- **ID**: The ID of an embedding entry.\n\nParameters for **Update Documents**\n\n- ID\n\n## Node options\n\n### Query Name\n\nThe name of the matching function you set up in Supabase. If you follow the [Supabase quickstart](https://supabase.com/docs/guides/ai/langchain?database-method=sql), this will be `match_documents`.\n\n### Metadata Filter\n\nAvailable in **Get Many** mode. When searching for data, use this to match with metadata associated with the document.\n\nThis is an `AND` query. If you specify more than one metadata filter field, all of them must match.\n\nWhen inserting data, the metadata is set using the document loader. Refer to [Default Data Loader](../../sub-nodes/n8n-nodes-langchain.documentdefaultdataloader/) for more information on loading documents.\n\n## Templates and examples\n\n**AI Agent To Chat With Files In Supabase Storage**\n\nby Mark Shcherbakov\n\n[View template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**🤖 Create a Documentation Expert Bot with RAG, Gemini, and Supabase**\n\nby Lucas Peyrin\n\n[View template details](https://n8n.io/workflows/5993-create-a-documentation-expert-bot-with-rag-gemini-and-supabase/)\n\n**Supabase Insertion & Upsertion & Retrieval**\n\nby Ria\n\n[View template details](https://n8n.io/workflows/2395-supabase-insertion-and-upsertion-and-retrieval/)\n\n[Browse Supabase Vector Store integration templates](https://n8n.io/integrations/supabase-vector-store/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChain's Supabase documentation](https://js.langchain.com/docs/integrations/vectorstores/supabase/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "markdown": "# Supabase Vector Store node\n\nUse the Supabase Vector Store to interact with your Supabase database as vector store. You can insert documents into a vector database, get many documents from a vector database, and retrieve documents to provide them to a retriever connected to a chain.\n\nUse the Supabase Vector Store to interact with your Supabase database as [vector store](../../../../../glossary/#ai-vector-store). You can insert documents into a vector database, get documents from a vector database, retrieve documents to provide them to a retriever connected to a [chain](../../../../../glossary/#ai-chain), or connect it directly to an [agent](../../../../../glossary/#ai-agent) to use as a [tool](../../../../../glossary/#ai-tool). You can also update an item in a vector store by its ID.\n\nOn this page, you'll find the node parameters for the Supabase node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/supabase/).\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\nSupabase provides a [quickstart for setting up your vector store](https://supabase.com/docs/guides/ai/langchain?database-method=sql). If you use settings other than the defaults in the quickstart, this may affect parameter settings in n8n. Make sure you understand what you're doing.\n\n## Node usage patterns\n\nYou can use the Supabase Vector Store node in the following patterns.\n\n### Use as a regular node to insert, update, and retrieve documents\n\nYou can use the Supabase Vector Store as a regular node to insert, update, or get documents. This pattern places the Supabase Vector Store in the regular connection flow without using an agent.\n\nYou can see an example of this in scenario 1 of [this template](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/).\n\n### Connect directly to an AI agent as a tool\n\nYou can connect the Supabase Vector Store node directly to the tool connector of an [AI agent](../n8n-nodes-langchain.agent/) to use a vector store as a resource when answering queries.\n\nHere, the connection would be: AI agent (tools connector) -> Supabase Vector Store node.\n\n### Use a retriever to fetch documents\n\nYou can use the [Vector Store Retriever](../../sub-nodes/n8n-nodes-langchain.retrievervectorstore/) node with the Supabase Vector Store node to fetch documents from the Supabase Vector Store node. This is often used with the [Question and Answer Chain](../n8n-nodes-langchain.chainretrievalqa/) node to fetch documents from the vector store that match the given chat input.\n\nAn [example of the connection flow](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/) (the example uses Pinecone, but the pattern in the same) would be: Question and Answer Chain (Retriever connector) -> Vector Store Retriever (Vector Store connector) -> Supabase Vector Store.\n\n### Use the Vector Store Question Answer Tool to answer questions\n\nAnother pattern uses the [Vector Store Question Answer Tool](../../sub-nodes/n8n-nodes-langchain.toolvectorstore/) to summarize results and answer questions from the Supabase Vector Store node. Rather than connecting the Supabase Vector Store directly as a tool, this pattern uses a tool specifically designed to summarizes data in the vector store.\n\nThe [connections flow](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/) in this case would look like this: AI agent (tools connector) -> Vector Store Question Answer Tool (Vector Store connector) -> Supabase Vector store.\n\n## Node parameters\n\n### Operation Mode\n\nThis Vector Store node has five modes: **Get Many**, **Insert Documents**, **Retrieve Documents (As Vector Store for Chain/Tool)**, **Retrieve Documents (As Tool for AI Agent)**, and **Update Documents**. The mode you select determines the operations you can perform with the node and what inputs and outputs are available.\n\n#### Get Many\n\nIn this mode, you can retrieve multiple documents from your vector database by providing a prompt. The prompt will be embedded and used for similarity search. The node will return the documents that are most similar to the prompt with their similarity score. This is useful if you want to retrieve a list of similar documents and pass them to an agent as additional context.\n\n#### Insert Documents\n\nUse Insert Documents mode to insert new documents into your vector database.\n\n#### Retrieve Documents (As Vector Store for Chain/Tool)\n\nUse Retrieve Documents (As Vector Store for Chain/Tool) mode with a vector-store retriever to retrieve documents from a vector database and provide them to the retriever connected to a chain. In this mode you must connect the node to a retriever node or root node.\n\n#### Retrieve Documents (As Tool for AI Agent)\n\nUse Retrieve Documents (As Tool for AI Agent) mode to use the vector store as a tool resource when answering queries. When formulating responses, the agent uses the vector store when the vector store name and description match the question details.\n\n#### Update Documents\n\nUse Update Documents mode to update documents in a vector database by ID. Fill in the **ID** with the ID of the embedding entry to update.\n\n### Rerank Results\n\nEnables [reranking](../../../../../glossary/#ai-reranking). If you enable this option, you must connect a reranking node to the vector store. That node will then rerank the results for queries. You can use this option with the `Get Many`, `Retrieve Documents (As Vector Store for Chain/Tool)` and `Retrieve Documents (As Tool for AI Agent)` modes.\n\n### Get Many parameters\n\n- **Table Name**: Enter the Supabase table to use.\n- **Prompt**: Enter the search query.\n- **Limit**: Enter how many results to retrieve from the vector store. For example, set this to `10` to get the ten best results.\n\n### Insert Documents parameters\n\n- **Table Name**: Enter the Supabase table to use.\n\n### Retrieve Documents (As Vector Store for Chain/Tool) parameters\n\n- **Table Name**: Enter the Supabase table to use.\n\n### Retrieve Documents (As Tool for AI Agent) parameters\n\n- **Name**: The name of the vector store.\n- **Description**: Explain to the LLM what this tool does. A good, specific description allows LLMs to produce expected results more often.\n- **Table Name**: Enter the Supabase table to use.\n- **Limit**: Enter how many results to retrieve from the vector store. For example, set this to `10` to get the ten best results.\n\n### Update Documents\n\n- **Table Name**: Enter the Supabase table to use.\n- **ID**: The ID of an embedding entry.\n\nParameters for **Update Documents**\n\n- ID\n\n## Node options\n\n### Query Name\n\nThe name of the matching function you set up in Supabase. If you follow the [Supabase quickstart](https://supabase.com/docs/guides/ai/langchain?database-method=sql), this will be `match_documents`.\n\n### Metadata Filter\n\nAvailable in **Get Many** mode. When searching for data, use this to match with metadata associated with the document.\n\nThis is an `AND` query. If you specify more than one metadata filter field, all of them must match.\n\nWhen inserting data, the metadata is set using the document loader. Refer to [Default Data Loader](../../sub-nodes/n8n-nodes-langchain.documentdefaultdataloader/) for more information on loading documents.\n\n## Templates and examples\n\n**AI Agent To Chat With Files In Supabase Storage**\n\nby Mark Shcherbakov\n\n[View template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**Automate sales cold calling pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**🤖 Create a Documentation Expert Bot with RAG, Gemini, and Supabase**\n\nby Lucas Peyrin\n\n[View template details](https://n8n.io/workflows/5993-create-a-documentation-expert-bot-with-rag-gemini-and-supabase/)\n\n[Browse Supabase Vector Store integration templates](https://n8n.io/integrations/supabase-vector-store/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChain's Supabase documentation](https://js.langchain.com/docs/integrations/vectorstores/supabase/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
         "excerpt": "# Supabase Vector Store node  Use the Supabase Vector Store to interact with your Supabase database as vector store. You can insert documents into a vector database, get many documents from a vector database, and retrieve documents to provide them to a retriever connected to a chain.  Use the Supabase Vector Store to interact with your Supabase database as [vector store](../../../../../glossary/#ai-vector-store). You can insert documents into a vector database, get documents from a vector databa...",
         "sections": [
           {
@@ -43641,11 +43758,11 @@
         "codeExamples": 0,
         "complexity": "intermediate",
         "readingTime": "7 min",
-        "contentLength": 8860,
+        "contentLength": 8921,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "supabase vector store # supabase vector store node\n\nuse the supabase vector store to interact with your supabase database as vector store. you can insert documents into a vector database, get many documents from a vector database, and retrieve documents to provide them to a retriever connected to a chain.\n\nuse the supabase vector store to interact with your supabase database as [vector store](../../../../../glossary/#ai-vector-store). you can insert documents into a vector database, get documents from a vector database, retrieve documents to provide them to a retriever connected to a [chain](../../../../../glossary/#ai-chain), or connect it directly to an [agent](../../../../../glossary/#ai-agent) to use as a [tool](../../../../../glossary/#ai-tool). you can also update an item in a vector store by its id.\n\non this page, you'll find the node parameters for the supabase node, and links to more resources.\n\ncredentials\n\nyou can find authentication information for this node [here](../../../credentials/supabase/).\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\nsupabase provides a [quickstart for setting up your vector store](https://supabase.com/docs/guides/ai/langchain?database-method=sql). if you use settings other than the defaults in the quickstart, this may affect parameter settings in n8n. make sure you understand what you're doing.\n\n## node usage patterns\n\nyou can use the supabase vector store node in the following patterns.\n\n### use as a regular node to insert, update, and retrieve documents\n\nyou can use the supabase vector store as a regular node to insert, update, or get documents. this pattern places the supabase vector store in the regular connection flow without using an agent.\n\nyou can see an example of this in scenario 1 of [this template](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/).\n\n### connect directly to an ai agent as a tool\n\nyou can connect the supabase vector store node directly to the tool connector of an [ai agent](../n8n-nodes-langchain.agent/) to use a vector store as a resource when answering queries.\n\nhere, the connection would be: ai agent (tools connector) -> supabase vector store node.\n\n### use a retriever to fetch documents\n\nyou can use the [vector store retriever](../../sub-nodes/n8n-nodes-langchain.retrievervectorstore/) node with the supabase vector store node to fetch documents from the supabase vector store node. this is often used with the [question and answer chain](../n8n-nodes-langchain.chainretrievalqa/) node to fetch documents from the vector store that match the given chat input.\n\nan [example of the connection flow](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/) (the example uses pinecone, but the pattern in the same) would be: question and answer chain (retriever connector) -> vector store retriever (vector store connector) -> supabase vector store.\n\n### use the vector store question answer tool to answer questions\n\nanother pattern uses the [vector store question answer tool](../../sub-nodes/n8n-nodes-langchain.toolvectorstore/) to summarize results and answer questions from the supabase vector store node. rather than connecting the supabase vector store directly as a tool, this pattern uses a tool specifically designed to summarizes data in the vector store.\n\nthe [connections flow](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/) in this case would look like this: ai agent (tools connector) -> vector store question answer tool (vector store connector) -> supabase vector store.\n\n## node parameters\n\n### operation mode\n\nthis vector store node has five modes: **get many**, **insert documents**, **retrieve documents (as vector store for chain/tool)**, **retrieve documents (as tool for ai agent)**, and **update documents**. the mode you select determines the operations you can perform with the node and what inputs and outputs are available.\n\n#### get many\n\nin this mode, you can retrieve multiple documents from your vector database by providing a prompt. the prompt will be embedded and used for similarity search. the node will return the documents that are most similar to the prompt with their similarity score. this is useful if you want to retrieve a list of similar documents and pass them to an agent as additional context.\n\n#### insert documents\n\nuse insert documents mode to insert new documents into your vector database.\n\n#### retrieve documents (as vector store for chain/tool)\n\nuse retrieve documents (as vector store for chain/tool) mode with a vector-store retriever to retrieve documents from a vector database and provide them to the retriever connected to a chain. in this mode you must connect the node to a retriever node or root node.\n\n#### retrieve documents (as tool for ai agent)\n\nuse retrieve documents (as tool for ai agent) mode to use the vector store as a tool resource when answering queries. when formulating responses, the agent uses the vector store when the vector store name and description match the question details.\n\n#### update documents\n\nuse update documents mode to update documents in a vector database by id. fill in the **id** with the id of the embedding entry to update.\n\n### rerank results\n\nenables [reranking](../../../../../glossary/#ai-reranking). if you enable this option, you must connect a reranking node to the vector store. that node will then rerank the results for queries. you can use this option with the `get many`, `retrieve documents (as vector store for chain/tool)` and `retrieve documents (as tool for ai agent)` modes.\n\n### get many parameters\n\n- **table name**: enter the supabase table to use.\n- **prompt**: enter the search query.\n- **limit**: enter how many results to retrieve from the vector store. for example, set this to `10` to get the ten best results.\n\n### insert documents parameters\n\n- **table name**: enter the supabase table to use.\n\n### retrieve documents (as vector store for chain/tool) parameters\n\n- **table name**: enter the supabase table to use.\n\n### retrieve documents (as tool for ai agent) parameters\n\n- **name**: the name of the vector store.\n- **description**: explain to the llm what this tool does. a good, specific description allows llms to produce expected results more often.\n- **table name**: enter the supabase table to use.\n- **limit**: enter how many results to retrieve from the vector store. for example, set this to `10` to get the ten best results.\n\n### update documents\n\n- **table name**: enter the supabase table to use.\n- **id**: the id of an embedding entry.\n\nparameters for **update documents**\n\n- id\n\n## node options\n\n### query name\n\nthe name of the matching function you set up in supabase. if you follow the [supabase quickstart](https://supabase.com/docs/guides/ai/langchain?database-method=sql), this will be `match_documents`.\n\n### metadata filter\n\navailable in **get many** mode. when searching for data, use this to match with metadata associated with the document.\n\nthis is an `and` query. if you specify more than one metadata filter field, all of them must match.\n\nwhen inserting data, the metadata is set using the document loader. refer to [default data loader](../../sub-nodes/n8n-nodes-langchain.documentdefaultdataloader/) for more information on loading documents.\n\n## templates and examples\n\n**ai agent to chat with files in supabase storage**\n\nby mark shcherbakov\n\n[view template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**🤖 create a documentation expert bot with rag, gemini, and supabase**\n\nby lucas peyrin\n\n[view template details](https://n8n.io/workflows/5993-create-a-documentation-expert-bot-with-rag-gemini-and-supabase/)\n\n**supabase insertion & upsertion & retrieval**\n\nby ria\n\n[view template details](https://n8n.io/workflows/2395-supabase-insertion-and-upsertion-and-retrieval/)\n\n[browse supabase vector store integration templates](https://n8n.io/integrations/supabase-vector-store/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nrefer to [langchain's supabase documentation](https://js.langchain.com/docs/integrations/vectorstores/supabase/) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n supabase vector store node",
+        "fullText": "supabase vector store # supabase vector store node\n\nuse the supabase vector store to interact with your supabase database as vector store. you can insert documents into a vector database, get many documents from a vector database, and retrieve documents to provide them to a retriever connected to a chain.\n\nuse the supabase vector store to interact with your supabase database as [vector store](../../../../../glossary/#ai-vector-store). you can insert documents into a vector database, get documents from a vector database, retrieve documents to provide them to a retriever connected to a [chain](../../../../../glossary/#ai-chain), or connect it directly to an [agent](../../../../../glossary/#ai-agent) to use as a [tool](../../../../../glossary/#ai-tool). you can also update an item in a vector store by its id.\n\non this page, you'll find the node parameters for the supabase node, and links to more resources.\n\ncredentials\n\nyou can find authentication information for this node [here](../../../credentials/supabase/).\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\nsupabase provides a [quickstart for setting up your vector store](https://supabase.com/docs/guides/ai/langchain?database-method=sql). if you use settings other than the defaults in the quickstart, this may affect parameter settings in n8n. make sure you understand what you're doing.\n\n## node usage patterns\n\nyou can use the supabase vector store node in the following patterns.\n\n### use as a regular node to insert, update, and retrieve documents\n\nyou can use the supabase vector store as a regular node to insert, update, or get documents. this pattern places the supabase vector store in the regular connection flow without using an agent.\n\nyou can see an example of this in scenario 1 of [this template](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/).\n\n### connect directly to an ai agent as a tool\n\nyou can connect the supabase vector store node directly to the tool connector of an [ai agent](../n8n-nodes-langchain.agent/) to use a vector store as a resource when answering queries.\n\nhere, the connection would be: ai agent (tools connector) -> supabase vector store node.\n\n### use a retriever to fetch documents\n\nyou can use the [vector store retriever](../../sub-nodes/n8n-nodes-langchain.retrievervectorstore/) node with the supabase vector store node to fetch documents from the supabase vector store node. this is often used with the [question and answer chain](../n8n-nodes-langchain.chainretrievalqa/) node to fetch documents from the vector store that match the given chat input.\n\nan [example of the connection flow](https://n8n.io/workflows/1960-ask-questions-about-a-pdf-using-ai/) (the example uses pinecone, but the pattern in the same) would be: question and answer chain (retriever connector) -> vector store retriever (vector store connector) -> supabase vector store.\n\n### use the vector store question answer tool to answer questions\n\nanother pattern uses the [vector store question answer tool](../../sub-nodes/n8n-nodes-langchain.toolvectorstore/) to summarize results and answer questions from the supabase vector store node. rather than connecting the supabase vector store directly as a tool, this pattern uses a tool specifically designed to summarizes data in the vector store.\n\nthe [connections flow](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/) in this case would look like this: ai agent (tools connector) -> vector store question answer tool (vector store connector) -> supabase vector store.\n\n## node parameters\n\n### operation mode\n\nthis vector store node has five modes: **get many**, **insert documents**, **retrieve documents (as vector store for chain/tool)**, **retrieve documents (as tool for ai agent)**, and **update documents**. the mode you select determines the operations you can perform with the node and what inputs and outputs are available.\n\n#### get many\n\nin this mode, you can retrieve multiple documents from your vector database by providing a prompt. the prompt will be embedded and used for similarity search. the node will return the documents that are most similar to the prompt with their similarity score. this is useful if you want to retrieve a list of similar documents and pass them to an agent as additional context.\n\n#### insert documents\n\nuse insert documents mode to insert new documents into your vector database.\n\n#### retrieve documents (as vector store for chain/tool)\n\nuse retrieve documents (as vector store for chain/tool) mode with a vector-store retriever to retrieve documents from a vector database and provide them to the retriever connected to a chain. in this mode you must connect the node to a retriever node or root node.\n\n#### retrieve documents (as tool for ai agent)\n\nuse retrieve documents (as tool for ai agent) mode to use the vector store as a tool resource when answering queries. when formulating responses, the agent uses the vector store when the vector store name and description match the question details.\n\n#### update documents\n\nuse update documents mode to update documents in a vector database by id. fill in the **id** with the id of the embedding entry to update.\n\n### rerank results\n\nenables [reranking](../../../../../glossary/#ai-reranking). if you enable this option, you must connect a reranking node to the vector store. that node will then rerank the results for queries. you can use this option with the `get many`, `retrieve documents (as vector store for chain/tool)` and `retrieve documents (as tool for ai agent)` modes.\n\n### get many parameters\n\n- **table name**: enter the supabase table to use.\n- **prompt**: enter the search query.\n- **limit**: enter how many results to retrieve from the vector store. for example, set this to `10` to get the ten best results.\n\n### insert documents parameters\n\n- **table name**: enter the supabase table to use.\n\n### retrieve documents (as vector store for chain/tool) parameters\n\n- **table name**: enter the supabase table to use.\n\n### retrieve documents (as tool for ai agent) parameters\n\n- **name**: the name of the vector store.\n- **description**: explain to the llm what this tool does. a good, specific description allows llms to produce expected results more often.\n- **table name**: enter the supabase table to use.\n- **limit**: enter how many results to retrieve from the vector store. for example, set this to `10` to get the ten best results.\n\n### update documents\n\n- **table name**: enter the supabase table to use.\n- **id**: the id of an embedding entry.\n\nparameters for **update documents**\n\n- id\n\n## node options\n\n### query name\n\nthe name of the matching function you set up in supabase. if you follow the [supabase quickstart](https://supabase.com/docs/guides/ai/langchain?database-method=sql), this will be `match_documents`.\n\n### metadata filter\n\navailable in **get many** mode. when searching for data, use this to match with metadata associated with the document.\n\nthis is an `and` query. if you specify more than one metadata filter field, all of them must match.\n\nwhen inserting data, the metadata is set using the document loader. refer to [default data loader](../../sub-nodes/n8n-nodes-langchain.documentdefaultdataloader/) for more information on loading documents.\n\n## templates and examples\n\n**ai agent to chat with files in supabase storage**\n\nby mark shcherbakov\n\n[view template details](https://n8n.io/workflows/2621-ai-agent-to-chat-with-files-in-supabase-storage/)\n\n**automate sales cold calling pipeline with apify, gpt-4o, and whatsapp**\n\nby khairul muhtadin\n\n[view template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**🤖 create a documentation expert bot with rag, gemini, and supabase**\n\nby lucas peyrin\n\n[view template details](https://n8n.io/workflows/5993-create-a-documentation-expert-bot-with-rag-gemini-and-supabase/)\n\n[browse supabase vector store integration templates](https://n8n.io/integrations/supabase-vector-store/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nrefer to [langchain's supabase documentation](https://js.langchain.com/docs/integrations/vectorstores/supabase/) for more information about the service.\n\nview n8n's [advanced ai](../../../../../advanced-ai/) documentation.\n supabase vector store node",
         "importantTerms": [
           "vector",
           "store",
@@ -43654,9 +43771,9 @@
           "node",
           "this",
           "tool",
+          "with",
           "agent",
           "retrieve",
-          "with",
           "name",
           "nodes",
           "database",
@@ -45272,7 +45389,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Embeddings Cohere node\n\nUse the Embeddings Cohere node to generate [embeddings](../../../../../glossary/#ai-embedding) for a given text.\n\nOn this page, you'll find the node parameters for the Embeddings Cohere node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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- **Model**: Select the model to use to generate the embedding. Choose from:\n  - **Embed-English-v2.0(4096 Dimensions)**\n  - **Embed-English-Light-v2.0(1024 Dimensions)**\n  - **Embed-Multilingual-v2.0(768 Dimensions)**\n\nLearn more about available models in [Cohere's models documentation](https://docs.cohere.com/docs/models).\n\n## Templates and examples\n\n**Automate Sales Cold Calling Pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Build a Document QA System with RAG using Milvus, Cohere, and OpenAI for Google Drive**\n\nby Aitor | 1Node\n\n[View template details](https://n8n.io/workflows/3848-build-a-document-qa-system-with-rag-using-milvus-cohere-and-openai-for-google-drive/)\n\n[Browse Embeddings Cohere integration templates](https://n8n.io/integrations/embeddings-cohere/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [Langchain's Cohere embeddings documentation](https://js.langchain.com/docs/integrations/text_embedding/cohere/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "markdown": "# Embeddings Cohere node\n\nUse the Embeddings Cohere node to generate [embeddings](../../../../../glossary/#ai-embedding) for a given text.\n\nOn this page, you'll find the node parameters for the Embeddings Cohere node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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- **Model**: Select the model to use to generate the embedding. Choose from:\n  - **Embed-English-v2.0(4096 Dimensions)**\n  - **Embed-English-Light-v2.0(1024 Dimensions)**\n  - **Embed-Multilingual-v2.0(768 Dimensions)**\n\nLearn more about available models in [Cohere's models documentation](https://docs.cohere.com/docs/models).\n\n## Templates and examples\n\n**Automate sales cold calling pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Build a Document QA System with RAG using Milvus, Cohere, and OpenAI for Google Drive**\n\nby Aitor | 1Node\n\n[View template details](https://n8n.io/workflows/3848-build-a-document-qa-system-with-rag-using-milvus-cohere-and-openai-for-google-drive/)\n\n[Browse Embeddings Cohere integration templates](https://n8n.io/integrations/embeddings-cohere/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [Langchain's Cohere embeddings documentation](https://js.langchain.com/docs/integrations/text_embedding/cohere/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
         "excerpt": "# Embeddings Cohere node  Use the Embeddings Cohere node to generate [embeddings](../../../../../glossary/#ai-embedding) for a given text.  On this page, you'll find the node parameters for the Embeddings Cohere node, and links to more resources.  Credentials  You can find authentication information for this node [here](../../../credentials/cohere/).  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items using an expression.  Most nodes, in...",
         "sections": [
           {
@@ -46125,7 +46242,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Cohere Chat Model node\n\nUse the Cohere Chat Model node to access Cohere's large language models for conversational AI and text generation tasks.\n\nOn this page, you'll find the node parameters for the Cohere Chat Model node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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- **Model**: Select the model which will generate the completion. n8n dynamically loads available models from the Cohere API. Learn more in the [Cohere model documentation](https://docs.cohere.com/v2/docs/models#command).\n\n## Node options\n\n- **Sampling Temperature**: Use this option to control the randomness of the sampling process. A higher temperature creates more diverse sampling, but increases the risk of hallucinations.\n- **Max Retries**: Enter the maximum number of times to retry a request.\n\n## Templates and examples\n\n**Automate Sales Cold Calling Pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Build a Document QA System with RAG using Milvus, Cohere, and OpenAI for Google Drive**\n\nby Aitor | 1Node\n\n[View template details](https://n8n.io/workflows/3848-build-a-document-qa-system-with-rag-using-milvus-cohere-and-openai-for-google-drive/)\n\n[Browse Cohere Chat Model integration templates](https://n8n.io/integrations/cohere-chat-model/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [Cohere's API documentation](https://docs.cohere.com/v2/reference/about) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "markdown": "# Cohere Chat Model node\n\nUse the Cohere Chat Model node to access Cohere's large language models for conversational AI and text generation tasks.\n\nOn this page, you'll find the node parameters for the Cohere Chat Model node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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- **Model**: Select the model which will generate the completion. n8n dynamically loads available models from the Cohere API. Learn more in the [Cohere model documentation](https://docs.cohere.com/v2/docs/models#command).\n\n## Node options\n\n- **Sampling Temperature**: Use this option to control the randomness of the sampling process. A higher temperature creates more diverse sampling, but increases the risk of hallucinations.\n- **Max Retries**: Enter the maximum number of times to retry a request.\n\n## Templates and examples\n\n**Automate sales cold calling pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Build a Document QA System with RAG using Milvus, Cohere, and OpenAI for Google Drive**\n\nby Aitor | 1Node\n\n[View template details](https://n8n.io/workflows/3848-build-a-document-qa-system-with-rag-using-milvus-cohere-and-openai-for-google-drive/)\n\n[Browse Cohere Chat Model integration templates](https://n8n.io/integrations/cohere-chat-model/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [Cohere's API documentation](https://docs.cohere.com/v2/reference/about) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
         "excerpt": "# Cohere Chat Model node  Use the Cohere Chat Model node to access Cohere's large language models for conversational AI and text generation tasks.  On this page, you'll find the node parameters for the Cohere Chat Model node, and links to more resources.  Credentials  You can find authentication information for this node [here](../../../credentials/cohere/).  Parameter resolution in sub-nodes  Sub-nodes behave differently to other nodes when processing multiple items using an expression.  Most n...",
         "sections": [
           {
@@ -46982,7 +47099,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Cohere Model node\n\nUse the Cohere Model node to use Cohere's models.\n\nOn this page, you'll find the node parameters for the Cohere Model node, and links to more resources.\n\nThis node lacks tools support, so it won't work with the [AI Agent](../../root-nodes/n8n-nodes-langchain.agent/) node. Instead, connect it with the [Basic LLM Chain](../../root-nodes/n8n-nodes-langchain.chainllm/) node.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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 Options\n\n- **Maximum Number of Tokens**: Enter the maximum number of tokens used, which sets the completion length.\n- **Sampling Temperature**: Use this option to control the randomness of the sampling process. A higher temperature creates more diverse sampling, but increases the risk of hallucinations.\n\n## Templates and examples\n\n**Automate Sales Cold Calling Pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Build a Document QA System with RAG using Milvus, Cohere, and OpenAI for Google Drive**\n\nby Aitor | 1Node\n\n[View template details](https://n8n.io/workflows/3848-build-a-document-qa-system-with-rag-using-milvus-cohere-and-openai-for-google-drive/)\n\n[Browse Cohere Model integration templates](https://n8n.io/integrations/cohere-model/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChains's Cohere documentation](https://js.langchain.com/docs/integrations/llms/cohere/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "markdown": "# Cohere Model node\n\nUse the Cohere Model node to use Cohere's models.\n\nOn this page, you'll find the node parameters for the Cohere Model node, and links to more resources.\n\nThis node lacks tools support, so it won't work with the [AI Agent](../../root-nodes/n8n-nodes-langchain.agent/) node. Instead, connect it with the [Basic LLM Chain](../../root-nodes/n8n-nodes-langchain.chainllm/) node.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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 Options\n\n- **Maximum Number of Tokens**: Enter the maximum number of tokens used, which sets the completion length.\n- **Sampling Temperature**: Use this option to control the randomness of the sampling process. A higher temperature creates more diverse sampling, but increases the risk of hallucinations.\n\n## Templates and examples\n\n**Automate sales cold calling pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Build a Document QA System with RAG using Milvus, Cohere, and OpenAI for Google Drive**\n\nby Aitor | 1Node\n\n[View template details](https://n8n.io/workflows/3848-build-a-document-qa-system-with-rag-using-milvus-cohere-and-openai-for-google-drive/)\n\n[Browse Cohere Model integration templates](https://n8n.io/integrations/cohere-model/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nRefer to [LangChains's Cohere documentation](https://js.langchain.com/docs/integrations/llms/cohere/) for more information about the service.\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
         "excerpt": "# Cohere Model node  Use the Cohere Model node to use Cohere's models.  On this page, you'll find the node parameters for the Cohere Model node, and links to more resources.  This node lacks tools support, so it won't work with the [AI Agent](../../root-nodes/n8n-nodes-langchain.agent/) node. Instead, connect it with the [Basic LLM Chain](../../root-nodes/n8n-nodes-langchain.chainllm/) node.  Credentials  You can find authentication information for this node [here](../../../credentials/cohere/)....",
         "sections": [
           {
@@ -47921,7 +48038,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Reranker Cohere\n\nThe Reranker Cohere node allows you to [rerank](../../../../../glossary/#ai-reranking) the resulting chunks from a [vector store](../../../../../glossary/#ai-vector-store). You can connect this node to a vector store.\n\nThe reranker reorders the list of documents retrieved from a vector store for a given query in order of descending relevance.\n\nOn this page, you'll find the node parameters for the Reranker Cohere node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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### Model\n\nChoose the reranking model to use. You can find out more about the available models in [Cohere's model documentation](https://docs.cohere.com/docs/models#rerank).\n\n## Templates and examples\n\n**Automate Sales Cold Calling Pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Chat with Google Drive documents using OpenAI and Pinecone RAG search**\n\nby Pinecone\n\n[View template details](https://n8n.io/workflows/11870-chat-with-google-drive-documents-using-openai-and-pinecone-rag-search/)\n\n[Browse Reranker Cohere integration templates](https://n8n.io/integrations/reranker-cohere/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
+        "markdown": "# Reranker Cohere\n\nThe Reranker Cohere node allows you to [rerank](../../../../../glossary/#ai-reranking) the resulting chunks from a [vector store](../../../../../glossary/#ai-vector-store). You can connect this node to a vector store.\n\nThe reranker reorders the list of documents retrieved from a vector store for a given query in order of descending relevance.\n\nOn this page, you'll find the node parameters for the Reranker Cohere node, and links to more resources.\n\nCredentials\n\nYou can find authentication information for this node [here](../../../credentials/cohere/).\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### Model\n\nChoose the reranking model to use. You can find out more about the available models in [Cohere's model documentation](https://docs.cohere.com/docs/models#rerank).\n\n## Templates and examples\n\n**Automate sales cold calling pipeline with Apify, GPT-4o, and WhatsApp**\n\nby Khairul Muhtadin\n\n[View template details](https://n8n.io/workflows/5449-automate-sales-cold-calling-pipeline-with-apify-gpt-4o-and-whatsapp/)\n\n**Create a Multi-Modal Telegram Support Bot with GPT-4 and Supabase RAG**\n\nby Ezema Kingsley Chibuzo\n\n[View template details](https://n8n.io/workflows/5589-create-a-multi-modal-telegram-support-bot-with-gpt-4-and-supabase-rag/)\n\n**Chat with Google Drive documents using OpenAI and Pinecone RAG search**\n\nby Pinecone\n\n[View template details](https://n8n.io/workflows/11870-chat-with-google-drive-documents-using-openai-and-pinecone-rag-search/)\n\n[Browse Reranker Cohere integration templates](https://n8n.io/integrations/reranker-cohere/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nView n8n's [Advanced AI](../../../../../advanced-ai/) documentation.\n",
         "excerpt": "# Reranker Cohere  The Reranker Cohere node allows you to [rerank](../../../../../glossary/#ai-reranking) the resulting chunks from a [vector store](../../../../../glossary/#ai-vector-store). You can connect this node to a vector store.  The reranker reorders the list of documents retrieved from a vector store for a given query in order of descending relevance.  On this page, you'll find the node parameters for the Reranker Cohere node, and links to more resources.  Credentials  You can find aut...",
         "sections": [
           {
@@ -55183,13 +55300,13 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Chat node\n\nUse the Chat node with the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. This enables human-in-the-loop (HITL) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. The Chat node also works as a tool for AI Agents.\n\nAll features work with both embedded and hosted chat interfaces.\n\nChat Trigger node\n\nThe Chat node requires a [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, with the [Response Mode](../n8n-nodes-langchain.chattrigger/#response-mode) set to 'Using Response Nodes'.\n\nPrevious version\n\nIn previous versions, this node was called \"Respond to Chat\" and used a single \"Wait for User Reply\" toggle. The functionality has been reorganized into two distinct actions with additional response types.\n\n## Node parameters\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\nHuman-in-the-loop for AI tool calls\n\nThis node can be used as a human review step for AI Agent tool calls. When configured this way, the AI Agent will pause and request human approval through this service before executing tools that require oversight. Learn more in [Human-in-the-loop for AI tool calls](../../../../advanced-ai/human-in-the-loop-tools/).\n\nConfigure this node using the following parameters.\n\n### Operation\n\nThe Chat node supports the following operations:\n\n- **Send Message**: Send a message to the chat. The workflow execution continues immediately after sending.\n- **Send and Wait for Response**: Send a message to the chat and wait for a response from the user. This operation pauses the workflow execution until the user submits a response.\n\nChoosing **Send and Wait for Response** activates additional parameters and options as discussed in [waiting for a response](#waiting-for-a-response).\n\n### Message\n\nThe message to send to the chat. This parameter is available for both operations.\n\n## Node options\n\nUse these **Options** to further refine the node's behavior.\n\n### Add Memory Input Connection\n\nChoose whether you want to commit the messages from the Chat node to a connected memory. Using a shared memory between an agent or chain [root node](../../cluster-nodes/root-nodes/) and the Chat node attaches the same session key to these messages and lets you capture the full message history.\n\n## Waiting for a response\n\nBy choosing the **Send and Wait for Response** operation, you can send a message and pause the workflow execution until a person responds. This enables multi-turn conversations and approval workflows within a single execution.\n\n### Response Type\n\nYou can choose between the following types of responses:\n\n- **Free Text**: Users can type any response in the chat. This is the same behavior as the previous \"Wait for User Reply\" option.\n- **Approval**: Users can approve or disapprove using inline buttons in the message. You can also optionally allow users to type custom responses.\n\nDifferent parameters and options are available depending on which type you choose.\n\n### Free Text parameters and options\n\nWhen using the Free Text response type, the user can type any message as their response.\n\n**Use cases:**\n\n- Open-ended questions\n- Collecting detailed feedback\n- Requesting specific information\n\n**Options:** * **Limit Wait Time**: Whether the workflow automatically resumes execution after a specified time limit. This can be an interval or a specific wall time.\n\n### Approval parameters and options\n\nWhen using the Approval response type, the message displays inline buttons that users can click to approve or disapprove. This response type follows the same pattern as other human-in-the-loop (HITL) nodes in n8n.\n\n**Use cases:**\n\n- Simple yes/no decisions\n- Approval workflows\n- Confirmations\n\nWhen using the Approval response type, the following parameters are available:\n\n- **Type of Approval**: Whether to present only an approval button or both approval and disapproval buttons.\n\n  - **Approve Only**: Displays a single approval button\n  - **Approve and Disapprove**: Displays both buttons (default)\n\n- **Approve Button Label**: The text to display on the approval button. Default: `Approve`\n\n- **Disapprove Button Label**: The text to display on the disapproval button (only shown when Type of Approval is \"Approve and Disapprove\"). Default: `Disapprove`\n\n- **Block User Input**: Whether to prevent users from typing custom messages (enabled) or allow them to type responses (disabled, default).\n\n  - When **disabled** (default): Users can click buttons or type a custom message. Typed messages are treated as disapproval with a custom message.\n  - When **enabled**: Users can only interact using the buttons.\n\nThe Approval response type also offers the following option:\n\n- **Limit Wait Time**: Whether the workflow automatically resumes execution after a specified time limit. This can be an interval or a specific wall time.\n\n## Related resources\n\nView n8n's [Advanced AI](../../../../advanced-ai/) documentation.\n\nRefer to the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node documentation for information about setting up the chat interface.\n\n## Templates and examples\n\n**AI agent chat**\n\nby n8n Team\n\n[View template details](https://n8n.io/workflows/1954-ai-agent-chat/)\n\n**Building Your First WhatsApp Chatbot**\n\nby Jimleuk\n\n[View template details](https://n8n.io/workflows/2465-building-your-first-whatsapp-chatbot/)\n\n**Scrape and summarize webpages with AI**\n\nby n8n Team\n\n[View template details](https://n8n.io/workflows/1951-scrape-and-summarize-webpages-with-ai/)\n\n[Browse Chat integration templates](https://n8n.io/integrations/chat/), or [search all templates](https://n8n.io/workflows/)\n\n## Common issues\n\n- The Chat node doesn't work when used as a tool of a subagent.\n- The Chat node doesn't work when used in a subworkflow. This includes usage in a subworkflow that's being used as a tool for an AI Agent.\n- Make sure the Chat Trigger node's Response Mode is set to \"Using Response Nodes\" for the Chat node to function properly.\n\nFor common questions or issues with the Chat Trigger node, refer to [Common Chat Trigger Node Issues](../n8n-nodes-langchain.chattrigger/common-issues/).\n",
-        "excerpt": "# Chat node  Use the Chat node with the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. This enables human-in-the-loop (HITL) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. The Chat node also works as a tool for AI Agents.  All features work with both embedded and hosted chat interfaces.  Chat Trigger node  The Chat node requires a [Chat Trigger](../n8n-n...",
+        "markdown": "# Chat node\n\nUse the Chat node with the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. This enables human-in-the-loop (HITL) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. The Chat node also works as a tool for AI Agents.\n\nChat Trigger node\n\nThe Chat node requires a [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, with the [Response Mode](../n8n-nodes-langchain.chattrigger/#response-mode) set to 'Using Response Nodes'.\n\nEmbedded mode not supported\n\nThe Chat node isn't supported when the Chat Trigger node is set to **Embedded** mode. In Embedded mode, use the [Respond to Webhook](../n8n-nodes-base.respondtowebhook/) node instead.\n\nPrevious version\n\nIn previous versions, this node was called \"Respond to Chat\" and used a single \"Wait for User Reply\" toggle. The functionality has been reorganized into two distinct actions with additional response types.\n\n## Node parameters\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\nHuman-in-the-loop for AI tool calls\n\nThis node can be used as a human review step for AI Agent tool calls. When configured this way, the AI Agent will pause and request human approval through this service before executing tools that require oversight. Learn more in [Human-in-the-loop for AI tool calls](../../../../advanced-ai/human-in-the-loop-tools/).\n\nConfigure this node using the following parameters.\n\n### Operation\n\nThe Chat node supports the following operations:\n\n- **Send Message**: Send a message to the chat. The workflow execution continues immediately after sending.\n- **Send and Wait for Response**: Send a message to the chat and wait for a response from the user. This operation pauses the workflow execution until the user submits a response.\n\nChoosing **Send and Wait for Response** activates additional parameters and options as discussed in [waiting for a response](#waiting-for-a-response).\n\n### Message\n\nThe message to send to the chat. This parameter is available for both operations.\n\n## Node options\n\nUse these **Options** to further refine the node's behavior.\n\n### Add Memory Input Connection\n\nChoose whether you want to commit the messages from the Chat node to a connected memory. Using a shared memory between an agent or chain [root node](../../cluster-nodes/root-nodes/) and the Chat node attaches the same session key to these messages and lets you capture the full message history.\n\n## Waiting for a response\n\nBy choosing the **Send and Wait for Response** operation, you can send a message and pause the workflow execution until a person responds. This enables multi-turn conversations and approval workflows within a single execution.\n\n### Response Type\n\nYou can choose between the following types of responses:\n\n- **Free Text**: Users can type any response in the chat. This is the same behavior as the previous \"Wait for User Reply\" option.\n- **Approval**: Users can approve or disapprove using inline buttons in the message. You can also optionally allow users to type custom responses.\n\nDifferent parameters and options are available depending on which type you choose.\n\n### Free Text parameters and options\n\nWhen using the Free Text response type, the user can type any message as their response.\n\n**Use cases:**\n\n- Open-ended questions\n- Collecting detailed feedback\n- Requesting specific information\n\n**Options:** * **Limit Wait Time**: Whether the workflow automatically resumes execution after a specified time limit. This can be an interval or a specific wall time.\n\n### Approval parameters and options\n\nWhen using the Approval response type, the message displays inline buttons that users can click to approve or disapprove. This response type follows the same pattern as other human-in-the-loop (HITL) nodes in n8n.\n\n**Use cases:**\n\n- Simple yes/no decisions\n- Approval workflows\n- Confirmations\n\nWhen using the Approval response type, the following parameters are available:\n\n- **Type of Approval**: Whether to present only an approval button or both approval and disapproval buttons.\n\n  - **Approve Only**: Displays a single approval button\n  - **Approve and Disapprove**: Displays both buttons (default)\n\n- **Approve Button Label**: The text to display on the approval button. Default: `Approve`\n\n- **Disapprove Button Label**: The text to display on the disapproval button (only shown when Type of Approval is \"Approve and Disapprove\"). Default: `Disapprove`\n\n- **Block User Input**: Whether to prevent users from typing custom messages (enabled) or allow them to type responses (disabled, default).\n\n  - When **disabled** (default): Users can click buttons or type a custom message. Typed messages are treated as disapproval with a custom message.\n  - When **enabled**: Users can only interact using the buttons.\n\nThe Approval response type also offers the following option:\n\n- **Limit Wait Time**: Whether the workflow automatically resumes execution after a specified time limit. This can be an interval or a specific wall time.\n\n## Related resources\n\nView n8n's [Advanced AI](../../../../advanced-ai/) documentation.\n\nRefer to the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node documentation for information about setting up the chat interface.\n\n## Templates and examples\n\n**AI agent chat**\n\nby n8n Team\n\n[View template details](https://n8n.io/workflows/1954-ai-agent-chat/)\n\n**Building Your First WhatsApp Chatbot**\n\nby Jimleuk\n\n[View template details](https://n8n.io/workflows/2465-building-your-first-whatsapp-chatbot/)\n\n**Scrape and summarize webpages with AI**\n\nby n8n Team\n\n[View template details](https://n8n.io/workflows/1951-scrape-and-summarize-webpages-with-ai/)\n\n[Browse Chat integration templates](https://n8n.io/integrations/chat/), or [search all templates](https://n8n.io/workflows/)\n\n## Common issues\n\n- The Chat node isn't supported when the Chat Trigger node's **Mode** is set to **Embedded**. In Embedded mode, the Chat Trigger node only offers **Respond to Webhook** as a response mode. Use the [Respond to Webhook](../n8n-nodes-base.respondtowebhook/) node instead.\n- The Chat node doesn't work when used as a tool of a subagent.\n- The Chat node doesn't work when used in a subworkflow. This includes usage in a subworkflow that's being used as a tool for an AI Agent.\n- Make sure the Chat Trigger node's Response Mode is set to \"Using Response Nodes\" for the Chat node to function properly.\n\nFor common questions or issues with the Chat Trigger node, refer to [Common Chat Trigger Node Issues](../n8n-nodes-langchain.chattrigger/common-issues/).\n",
+        "excerpt": "# Chat node  Use the Chat node with the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. This enables human-in-the-loop (HITL) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. The Chat node also works as a tool for AI Agents.  Chat Trigger node  The Chat node requires a [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, w...",
         "sections": [
           {
             "title": "Chat node",
             "level": 1,
-            "content": "Use the Chat node with the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. This enables human-in-the-loop (HITL) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. The Chat node also works as a tool for AI Agents.\n\nAll features work with both embedded and hosted chat interfaces.\n\nChat Trigger node\n\nThe Chat node requires a [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, with the [Response Mode](../n8n-nodes-langchain.chattrigger/#response-mode) set to 'Using Response Nodes'.\n\nPrevious version\n\nIn previous versions, this node was called \"Respond to Chat\" and used a single \"Wait for User Reply\" toggle. The functionality has been reorganized into two distinct actions with additional response types."
+            "content": "Use the Chat node with the [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. This enables human-in-the-loop (HITL) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. The Chat node also works as a tool for AI Agents.\n\nChat Trigger node\n\nThe Chat node requires a [Chat Trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, with the [Response Mode](../n8n-nodes-langchain.chattrigger/#response-mode) set to 'Using Response Nodes'.\n\nEmbedded mode not supported\n\nThe Chat node isn't supported when the Chat Trigger node is set to **Embedded** mode. In Embedded mode, use the [Respond to Webhook](../n8n-nodes-base.respondtowebhook/) node instead.\n\nPrevious version\n\nIn previous versions, this node was called \"Respond to Chat\" and used a single \"Wait for User Reply\" toggle. The functionality has been reorganized into two distinct actions "
           }
         ]
       },
@@ -55224,11 +55341,11 @@
         "codeExamples": 0,
         "complexity": "intermediate",
         "readingTime": "5 min",
-        "contentLength": 6510,
+        "contentLength": 6927,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "chat # chat node\n\nuse the chat node with the [chat trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. this enables human-in-the-loop (hitl) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. the chat node also works as a tool for ai agents.\n\nall features work with both embedded and hosted chat interfaces.\n\nchat trigger node\n\nthe chat node requires a [chat trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, with the [response mode](../n8n-nodes-langchain.chattrigger/#response-mode) set to 'using response nodes'.\n\nprevious version\n\nin previous versions, this node was called \"respond to chat\" and used a single \"wait for user reply\" toggle. the functionality has been reorganized into two distinct actions with additional response types.\n\n## node parameters\n\nthis node can be used as an ai tool\n\nthis node can be used to enhance the capabilities of an ai agent. when used in this way, many parameters can be set automatically, or with information directed by ai - find out more in the [ai tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\nhuman-in-the-loop for ai tool calls\n\nthis node can be used as a human review step for ai agent tool calls. when configured this way, the ai agent will pause and request human approval through this service before executing tools that require oversight. learn more in [human-in-the-loop for ai tool calls](../../../../advanced-ai/human-in-the-loop-tools/).\n\nconfigure this node using the following parameters.\n\n### operation\n\nthe chat node supports the following operations:\n\n- **send message**: send a message to the chat. the workflow execution continues immediately after sending.\n- **send and wait for response**: send a message to the chat and wait for a response from the user. this operation pauses the workflow execution until the user submits a response.\n\nchoosing **send and wait for response** activates additional parameters and options as discussed in [waiting for a response](#waiting-for-a-response).\n\n### message\n\nthe message to send to the chat. this parameter is available for both operations.\n\n## node options\n\nuse these **options** to further refine the node's behavior.\n\n### add memory input connection\n\nchoose whether you want to commit the messages from the chat node to a connected memory. using a shared memory between an agent or chain [root node](../../cluster-nodes/root-nodes/) and the chat node attaches the same session key to these messages and lets you capture the full message history.\n\n## waiting for a response\n\nby choosing the **send and wait for response** operation, you can send a message and pause the workflow execution until a person responds. this enables multi-turn conversations and approval workflows within a single execution.\n\n### response type\n\nyou can choose between the following types of responses:\n\n- **free text**: users can type any response in the chat. this is the same behavior as the previous \"wait for user reply\" option.\n- **approval**: users can approve or disapprove using inline buttons in the message. you can also optionally allow users to type custom responses.\n\ndifferent parameters and options are available depending on which type you choose.\n\n### free text parameters and options\n\nwhen using the free text response type, the user can type any message as their response.\n\n**use cases:**\n\n- open-ended questions\n- collecting detailed feedback\n- requesting specific information\n\n**options:** * **limit wait time**: whether the workflow automatically resumes execution after a specified time limit. this can be an interval or a specific wall time.\n\n### approval parameters and options\n\nwhen using the approval response type, the message displays inline buttons that users can click to approve or disapprove. this response type follows the same pattern as other human-in-the-loop (hitl) nodes in n8n.\n\n**use cases:**\n\n- simple yes/no decisions\n- approval workflows\n- confirmations\n\nwhen using the approval response type, the following parameters are available:\n\n- **type of approval**: whether to present only an approval button or both approval and disapproval buttons.\n\n  - **approve only**: displays a single approval button\n  - **approve and disapprove**: displays both buttons (default)\n\n- **approve button label**: the text to display on the approval button. default: `approve`\n\n- **disapprove button label**: the text to display on the disapproval button (only shown when type of approval is \"approve and disapprove\"). default: `disapprove`\n\n- **block user input**: whether to prevent users from typing custom messages (enabled) or allow them to type responses (disabled, default).\n\n  - when **disabled** (default): users can click buttons or type a custom message. typed messages are treated as disapproval with a custom message.\n  - when **enabled**: users can only interact using the buttons.\n\nthe approval response type also offers the following option:\n\n- **limit wait time**: whether the workflow automatically resumes execution after a specified time limit. this can be an interval or a specific wall time.\n\n## related resources\n\nview n8n's [advanced ai](../../../../advanced-ai/) documentation.\n\nrefer to the [chat trigger](../n8n-nodes-langchain.chattrigger/) node documentation for information about setting up the chat interface.\n\n## templates and examples\n\n**ai agent chat**\n\nby n8n team\n\n[view template details](https://n8n.io/workflows/1954-ai-agent-chat/)\n\n**building your first whatsapp chatbot**\n\nby jimleuk\n\n[view template details](https://n8n.io/workflows/2465-building-your-first-whatsapp-chatbot/)\n\n**scrape and summarize webpages with ai**\n\nby n8n team\n\n[view template details](https://n8n.io/workflows/1951-scrape-and-summarize-webpages-with-ai/)\n\n[browse chat integration templates](https://n8n.io/integrations/chat/), or [search all templates](https://n8n.io/workflows/)\n\n## common issues\n\n- the chat node doesn't work when used as a tool of a subagent.\n- the chat node doesn't work when used in a subworkflow. this includes usage in a subworkflow that's being used as a tool for an ai agent.\n- make sure the chat trigger node's response mode is set to \"using response nodes\" for the chat node to function properly.\n\nfor common questions or issues with the chat trigger node, refer to [common chat trigger node issues](../n8n-nodes-langchain.chattrigger/common-issues/).\n chat node",
+        "fullText": "chat # chat node\n\nuse the chat node with the [chat trigger](../n8n-nodes-langchain.chattrigger/) node to send messages into the chat and optionally wait for responses from users. this enables human-in-the-loop (hitl) use cases in chat workflows, allowing you to have multiple chat interactions within a single execution. the chat node also works as a tool for ai agents.\n\nchat trigger node\n\nthe chat node requires a [chat trigger](../n8n-nodes-langchain.chattrigger/) node to be present in the workflow, with the [response mode](../n8n-nodes-langchain.chattrigger/#response-mode) set to 'using response nodes'.\n\nembedded mode not supported\n\nthe chat node isn't supported when the chat trigger node is set to **embedded** mode. in embedded mode, use the [respond to webhook](../n8n-nodes-base.respondtowebhook/) node instead.\n\nprevious version\n\nin previous versions, this node was called \"respond to chat\" and used a single \"wait for user reply\" toggle. the functionality has been reorganized into two distinct actions with additional response types.\n\n## node parameters\n\nthis node can be used as an ai tool\n\nthis node can be used to enhance the capabilities of an ai agent. when used in this way, many parameters can be set automatically, or with information directed by ai - find out more in the [ai tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\nhuman-in-the-loop for ai tool calls\n\nthis node can be used as a human review step for ai agent tool calls. when configured this way, the ai agent will pause and request human approval through this service before executing tools that require oversight. learn more in [human-in-the-loop for ai tool calls](../../../../advanced-ai/human-in-the-loop-tools/).\n\nconfigure this node using the following parameters.\n\n### operation\n\nthe chat node supports the following operations:\n\n- **send message**: send a message to the chat. the workflow execution continues immediately after sending.\n- **send and wait for response**: send a message to the chat and wait for a response from the user. this operation pauses the workflow execution until the user submits a response.\n\nchoosing **send and wait for response** activates additional parameters and options as discussed in [waiting for a response](#waiting-for-a-response).\n\n### message\n\nthe message to send to the chat. this parameter is available for both operations.\n\n## node options\n\nuse these **options** to further refine the node's behavior.\n\n### add memory input connection\n\nchoose whether you want to commit the messages from the chat node to a connected memory. using a shared memory between an agent or chain [root node](../../cluster-nodes/root-nodes/) and the chat node attaches the same session key to these messages and lets you capture the full message history.\n\n## waiting for a response\n\nby choosing the **send and wait for response** operation, you can send a message and pause the workflow execution until a person responds. this enables multi-turn conversations and approval workflows within a single execution.\n\n### response type\n\nyou can choose between the following types of responses:\n\n- **free text**: users can type any response in the chat. this is the same behavior as the previous \"wait for user reply\" option.\n- **approval**: users can approve or disapprove using inline buttons in the message. you can also optionally allow users to type custom responses.\n\ndifferent parameters and options are available depending on which type you choose.\n\n### free text parameters and options\n\nwhen using the free text response type, the user can type any message as their response.\n\n**use cases:**\n\n- open-ended questions\n- collecting detailed feedback\n- requesting specific information\n\n**options:** * **limit wait time**: whether the workflow automatically resumes execution after a specified time limit. this can be an interval or a specific wall time.\n\n### approval parameters and options\n\nwhen using the approval response type, the message displays inline buttons that users can click to approve or disapprove. this response type follows the same pattern as other human-in-the-loop (hitl) nodes in n8n.\n\n**use cases:**\n\n- simple yes/no decisions\n- approval workflows\n- confirmations\n\nwhen using the approval response type, the following parameters are available:\n\n- **type of approval**: whether to present only an approval button or both approval and disapproval buttons.\n\n  - **approve only**: displays a single approval button\n  - **approve and disapprove**: displays both buttons (default)\n\n- **approve button label**: the text to display on the approval button. default: `approve`\n\n- **disapprove button label**: the text to display on the disapproval button (only shown when type of approval is \"approve and disapprove\"). default: `disapprove`\n\n- **block user input**: whether to prevent users from typing custom messages (enabled) or allow them to type responses (disabled, default).\n\n  - when **disabled** (default): users can click buttons or type a custom message. typed messages are treated as disapproval with a custom message.\n  - when **enabled**: users can only interact using the buttons.\n\nthe approval response type also offers the following option:\n\n- **limit wait time**: whether the workflow automatically resumes execution after a specified time limit. this can be an interval or a specific wall time.\n\n## related resources\n\nview n8n's [advanced ai](../../../../advanced-ai/) documentation.\n\nrefer to the [chat trigger](../n8n-nodes-langchain.chattrigger/) node documentation for information about setting up the chat interface.\n\n## templates and examples\n\n**ai agent chat**\n\nby n8n team\n\n[view template details](https://n8n.io/workflows/1954-ai-agent-chat/)\n\n**building your first whatsapp chatbot**\n\nby jimleuk\n\n[view template details](https://n8n.io/workflows/2465-building-your-first-whatsapp-chatbot/)\n\n**scrape and summarize webpages with ai**\n\nby n8n team\n\n[view template details](https://n8n.io/workflows/1951-scrape-and-summarize-webpages-with-ai/)\n\n[browse chat integration templates](https://n8n.io/integrations/chat/), or [search all templates](https://n8n.io/workflows/)\n\n## common issues\n\n- the chat node isn't supported when the chat trigger node's **mode** is set to **embedded**. in embedded mode, the chat trigger node only offers **respond to webhook** as a response mode. use the [respond to webhook](../n8n-nodes-base.respondtowebhook/) node instead.\n- the chat node doesn't work when used as a tool of a subagent.\n- the chat node doesn't work when used in a subworkflow. this includes usage in a subworkflow that's being used as a tool for an ai agent.\n- make sure the chat trigger node's response mode is set to \"using response nodes\" for the chat node to function properly.\n\nfor common questions or issues with the chat trigger node, refer to [common chat trigger node issues](../n8n-nodes-langchain.chattrigger/common-issues/).\n chat node",
         "importantTerms": [
           "chat",
           "node",
@@ -55236,18 +55353,19 @@
           "this",
           "approval",
           "type",
-          "message",
           "nodes",
-          "using",
           "when",
-          "with",
+          "message",
+          "trigger",
+          "using",
           "send",
           "wait",
+          "mode",
           "parameters",
+          "with",
           "users",
           "tool",
           "used",
-          "trigger",
           "human",
           "workflows",
           "execution",
@@ -55264,22 +55382,21 @@
           "chattrigger",
           "messages",
           "loop",
+          "embedded",
           "following",
           "whether",
           "text",
+          "only",
           "default",
           "https",
           "responses",
           "from",
           "single",
-          "both",
+          "respond",
           "advanced",
           "custom",
           "limit",
-          "only",
-          "view",
-          "common",
-          "issues"
+          "view"
         ]
       }
     },
@@ -66508,32 +66625,29 @@
     },
     {
       "id": "page-0865",
-      "title": "Mandrill credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/mandrill/index.md",
-      "urlPath": "integrations/builtin/credentials/mandrill/index.md",
+      "title": "Malcore credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/malcore/index.md",
+      "urlPath": "integrations/builtin/credentials/malcore/index.md",
       "category": "other",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Mandrill credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Mandrill](../../app-nodes/n8n-nodes-base.mandrill/)\n\n## Prerequisites\n\n- Create a Mailchimp [Transactional email account](https://mailchimp.com/features/transactional-email-infrastructure/)\n- Log in to [Mandrill](https://mandrillapp.com/login/) with your Mailchimp account.\n\nIf you already have a Mailchimp account with a Standard plan or higher, enable [Transactional Emails](https://mailchimp.com/help/add-or-remove-transactional-email) within that account to use Mandrill.\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [Mailchimp's Transactional API documentation](https://mailchimp.com/developer/transactional/api/) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: Generate an API key from the Mandrill [Settings](https://mandrillapp.com/settings). Refer to Mailchimp's [Generate your API key documentation](https://mailchimp.com/developer/transactional/guides/quick-start/#generate-your-api-key) for more detailed instructions.\n",
-        "excerpt": "# Mandrill credentials  You can use these credentials to authenticate the following nodes:  - [Mandrill](../../app-nodes/n8n-nodes-base.mandrill/)  ## Prerequisites  - Create a Mailchimp [Transactional email account](https://mailchimp.com/features/transactional-email-infrastructure/) - Log in to [Mandrill](https://mandrillapp.com/login/) with your Mailchimp account.  If you already have a Mailchimp account with a Standard plan or higher, enable [Transactional Emails](https://mailchimp.com/help/a...",
+        "markdown": "# Malcore credentials\n\nYou can use these credentials to authenticate when using the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [Custom API call](../../../custom-operations/).\n\n## Prerequisites\n\nCreate a [Malcore](https://app.malcore.io/register) account.\n\n## Related resources\n\nRefer to [Malcore's API documentation](https://malcore.readme.io/reference/) for more information about authenticating with the service.\n\nThis is a credential-only node. Refer to [Custom API operations](../../../custom-operations/) to learn more. View [example workflows and related content](https://n8n.io/integrations/malcore/) on n8n's website.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: Get an API Key from your **Account > API**.\n\nRefer to [Using the Malcore API](https://support.malcore.io/hc/en-au/articles/17711707070617-Using-the-Malcore-API) for more information.\n",
+        "excerpt": "# Malcore credentials  You can use these credentials to authenticate when using the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [Custom API call](../../../custom-operations/).  ## Prerequisites  Create a [Malcore](https://app.malcore.io/register) account.  ## Related resources  Refer to [Malcore's API documentation](https://malcore.readme.io/reference/) for more information about authenticating with the service.  This is a credential-only node. Refer to [Custom AP...",
         "sections": [
           {
-            "title": "Mandrill credentials",
+            "title": "Malcore credentials",
             "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Mandrill](../../app-nodes/n8n-nodes-base.mandrill/)"
+            "content": "You can use these credentials to authenticate when using the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [Custom API call](../../../custom-operations/)."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "mandrill",
+          "malcore",
           "credentials",
           "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
           "related",
           "resources",
           "using"
@@ -66543,50 +66657,51 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 1134,
+        "contentLength": 923,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "mandrill credentials # mandrill credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [mandrill](../../app-nodes/n8n-nodes-base.mandrill/)\n\n## prerequisites\n\n- create a mailchimp [transactional email account](https://mailchimp.com/features/transactional-email-infrastructure/)\n- log in to [mandrill](https://mandrillapp.com/login/) with your mailchimp account.\n\nif you already have a mailchimp account with a standard plan or higher, enable [transactional emails](https://mailchimp.com/help/add-or-remove-transactional-email) within that account to use mandrill.\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [mailchimp's transactional api documentation](https://mailchimp.com/developer/transactional/api/) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- an **api key**: generate an api key from the mandrill [settings](https://mandrillapp.com/settings). refer to mailchimp's [generate your api key documentation](https://mailchimp.com/developer/transactional/guides/quick-start/#generate-your-api-key) for more detailed instructions.\n mandrill credentials",
+        "fullText": "malcore credentials # malcore credentials\n\nyou can use these credentials to authenticate when using the [http request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [custom api call](../../../custom-operations/).\n\n## prerequisites\n\ncreate a [malcore](https://app.malcore.io/register) account.\n\n## related resources\n\nrefer to [malcore's api documentation](https://malcore.readme.io/reference/) for more information about authenticating with the service.\n\nthis is a credential-only node. refer to [custom api operations](../../../custom-operations/) to learn more. view [example workflows and related content](https://n8n.io/integrations/malcore/) on n8n's website.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- an **api key**: get an api key from your **account > api**.\n\nrefer to [using the malcore api](https://support.malcore.io/hc/en-au/articles/17711707070617-using-the-malcore-api) for more information.\n malcore credentials",
         "importantTerms": [
-          "mailchimp",
-          "mandrill",
-          "transactional",
-          "https",
+          "malcore",
           "credentials",
-          "account",
-          "nodes",
-          "email",
-          "your",
-          "generate"
+          "using",
+          "custom",
+          "https",
+          "operations",
+          "refer",
+          "more"
         ]
       }
     },
     {
       "id": "page-0866",
-      "title": "Malcore credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/malcore/index.md",
-      "urlPath": "integrations/builtin/credentials/malcore/index.md",
+      "title": "Mandrill credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/mandrill/index.md",
+      "urlPath": "integrations/builtin/credentials/mandrill/index.md",
       "category": "other",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Malcore credentials\n\nYou can use these credentials to authenticate when using the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [Custom API call](../../../custom-operations/).\n\n## Prerequisites\n\nCreate a [Malcore](https://app.malcore.io/register) account.\n\n## Related resources\n\nRefer to [Malcore's API documentation](https://malcore.readme.io/reference/) for more information about authenticating with the service.\n\nThis is a credential-only node. Refer to [Custom API operations](../../../custom-operations/) to learn more. View [example workflows and related content](https://n8n.io/integrations/malcore/) on n8n's website.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: Get an API Key from your **Account > API**.\n\nRefer to [Using the Malcore API](https://support.malcore.io/hc/en-au/articles/17711707070617-Using-the-Malcore-API) for more information.\n",
-        "excerpt": "# Malcore credentials  You can use these credentials to authenticate when using the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [Custom API call](../../../custom-operations/).  ## Prerequisites  Create a [Malcore](https://app.malcore.io/register) account.  ## Related resources  Refer to [Malcore's API documentation](https://malcore.readme.io/reference/) for more information about authenticating with the service.  This is a credential-only node. Refer to [Custom AP...",
+        "markdown": "# Mandrill credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Mandrill](../../app-nodes/n8n-nodes-base.mandrill/)\n\n## Prerequisites\n\n- Create a Mailchimp [Transactional email account](https://mailchimp.com/features/transactional-email-infrastructure/)\n- Log in to [Mandrill](https://mandrillapp.com/login/) with your Mailchimp account.\n\nIf you already have a Mailchimp account with a Standard plan or higher, enable [Transactional Emails](https://mailchimp.com/help/add-or-remove-transactional-email) within that account to use Mandrill.\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [Mailchimp's Transactional API documentation](https://mailchimp.com/developer/transactional/api/) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: Generate an API key from the Mandrill [Settings](https://mandrillapp.com/settings). Refer to Mailchimp's [Generate your API key documentation](https://mailchimp.com/developer/transactional/guides/quick-start/#generate-your-api-key) for more detailed instructions.\n",
+        "excerpt": "# Mandrill credentials  You can use these credentials to authenticate the following nodes:  - [Mandrill](../../app-nodes/n8n-nodes-base.mandrill/)  ## Prerequisites  - Create a Mailchimp [Transactional email account](https://mailchimp.com/features/transactional-email-infrastructure/) - Log in to [Mandrill](https://mandrillapp.com/login/) with your Mailchimp account.  If you already have a Mailchimp account with a Standard plan or higher, enable [Transactional Emails](https://mailchimp.com/help/a...",
         "sections": [
           {
-            "title": "Malcore credentials",
+            "title": "Mandrill credentials",
             "level": 1,
-            "content": "You can use these credentials to authenticate when using the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [Custom API call](../../../custom-operations/)."
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Mandrill](../../app-nodes/n8n-nodes-base.mandrill/)"
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "malcore",
+          "mandrill",
           "credentials",
           "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
           "related",
           "resources",
           "using"
@@ -66596,20 +66711,22 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 923,
+        "contentLength": 1134,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "malcore credentials # malcore credentials\n\nyou can use these credentials to authenticate when using the [http request node](../../core-nodes/n8n-nodes-base.httprequest/) to make a [custom api call](../../../custom-operations/).\n\n## prerequisites\n\ncreate a [malcore](https://app.malcore.io/register) account.\n\n## related resources\n\nrefer to [malcore's api documentation](https://malcore.readme.io/reference/) for more information about authenticating with the service.\n\nthis is a credential-only node. refer to [custom api operations](../../../custom-operations/) to learn more. view [example workflows and related content](https://n8n.io/integrations/malcore/) on n8n's website.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- an **api key**: get an api key from your **account > api**.\n\nrefer to [using the malcore api](https://support.malcore.io/hc/en-au/articles/17711707070617-using-the-malcore-api) for more information.\n malcore credentials",
+        "fullText": "mandrill credentials # mandrill credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [mandrill](../../app-nodes/n8n-nodes-base.mandrill/)\n\n## prerequisites\n\n- create a mailchimp [transactional email account](https://mailchimp.com/features/transactional-email-infrastructure/)\n- log in to [mandrill](https://mandrillapp.com/login/) with your mailchimp account.\n\nif you already have a mailchimp account with a standard plan or higher, enable [transactional emails](https://mailchimp.com/help/add-or-remove-transactional-email) within that account to use mandrill.\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [mailchimp's transactional api documentation](https://mailchimp.com/developer/transactional/api/) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- an **api key**: generate an api key from the mandrill [settings](https://mandrillapp.com/settings). refer to mailchimp's [generate your api key documentation](https://mailchimp.com/developer/transactional/guides/quick-start/#generate-your-api-key) for more detailed instructions.\n mandrill credentials",
         "importantTerms": [
-          "malcore",
-          "credentials",
-          "using",
-          "custom",
+          "mailchimp",
+          "mandrill",
+          "transactional",
           "https",
-          "operations",
-          "refer",
-          "more"
+          "credentials",
+          "account",
+          "nodes",
+          "email",
+          "your",
+          "generate"
         ]
       }
     },
@@ -71398,6 +71515,65 @@
     },
     {
       "id": "page-0941",
+      "title": "Rundeck credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/rundeck/index.md",
+      "urlPath": "integrations/builtin/credentials/rundeck/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Rundeck credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Rundeck](../../app-nodes/n8n-nodes-base.rundeck/)\n\n## Prerequisites\n\nCreate a user account on a [Rundeck](https://www.rundeck.com/) server.\n\n## Supported authentication methods\n\n- API token\n\n## Related resources\n\nRefer to [Rundeck's API documentation](https://docs.rundeck.com/docs/api/) for more information about the service.\n\n## Using API token\n\nTo configure this credential, you'll need:\n\n- Your **URL**: Enter the base URL of your Rundeck server, for example `http://myserver:4440`. Refer to [URLs](https://docs.rundeck.com/docs/api/#urls) for more information.\n- A user API **Token**: To generate a user API token, go to your **Profile > User API Tokens**. Refer to [User API tokens](https://docs.rundeck.com/docs/manual/10-user.html#user-api-tokens) for more information.\n",
+        "excerpt": "# Rundeck credentials  You can use these credentials to authenticate the following nodes:  - [Rundeck](../../app-nodes/n8n-nodes-base.rundeck/)  ## Prerequisites  Create a user account on a [Rundeck](https://www.rundeck.com/) server.  ## Supported authentication methods  - API token  ## Related resources  Refer to [Rundeck's API documentation](https://docs.rundeck.com/docs/api/) for more information about the service.  ## Using API token  To configure this credential, you'll need:  - Your **URL*...",
+        "sections": [
+          {
+            "title": "Rundeck credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Rundeck](../../app-nodes/n8n-nodes-base.rundeck/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "rundeck",
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using",
+          "token"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 873,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "rundeck credentials # rundeck credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [rundeck](../../app-nodes/n8n-nodes-base.rundeck/)\n\n## prerequisites\n\ncreate a user account on a [rundeck](https://www.rundeck.com/) server.\n\n## supported authentication methods\n\n- api token\n\n## related resources\n\nrefer to [rundeck's api documentation](https://docs.rundeck.com/docs/api/) for more information about the service.\n\n## using api token\n\nto configure this credential, you'll need:\n\n- your **url**: enter the base url of your rundeck server, for example `http://myserver:4440`. refer to [urls](https://docs.rundeck.com/docs/api/#urls) for more information.\n- a user api **token**: to generate a user api token, go to your **profile > user api tokens**. refer to [user api tokens](https://docs.rundeck.com/docs/manual/10-user.html#user-api-tokens) for more information.\n rundeck credentials",
+        "importantTerms": [
+          "rundeck",
+          "user",
+          "docs",
+          "credentials",
+          "https",
+          "token",
+          "nodes",
+          "refer",
+          "more",
+          "information",
+          "your",
+          "tokens"
+        ]
+      }
+    },
+    {
+      "id": "page-0942",
       "title": "S3 credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/s3/index.md",
       "urlPath": "integrations/builtin/credentials/s3/index.md",
@@ -71496,7 +71672,7 @@
       }
     },
     {
-      "id": "page-0942",
+      "id": "page-0943",
       "title": "Salesforce credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/salesforce/index.md",
       "urlPath": "integrations/builtin/credentials/salesforce/index.md",
@@ -71605,65 +71781,6 @@
         ]
       }
     },
-    {
-      "id": "page-0943",
-      "title": "Rundeck credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/rundeck/index.md",
-      "urlPath": "integrations/builtin/credentials/rundeck/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Rundeck credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Rundeck](../../app-nodes/n8n-nodes-base.rundeck/)\n\n## Prerequisites\n\nCreate a user account on a [Rundeck](https://www.rundeck.com/) server.\n\n## Supported authentication methods\n\n- API token\n\n## Related resources\n\nRefer to [Rundeck's API documentation](https://docs.rundeck.com/docs/api/) for more information about the service.\n\n## Using API token\n\nTo configure this credential, you'll need:\n\n- Your **URL**: Enter the base URL of your Rundeck server, for example `http://myserver:4440`. Refer to [URLs](https://docs.rundeck.com/docs/api/#urls) for more information.\n- A user API **Token**: To generate a user API token, go to your **Profile > User API Tokens**. Refer to [User API tokens](https://docs.rundeck.com/docs/manual/10-user.html#user-api-tokens) for more information.\n",
-        "excerpt": "# Rundeck credentials  You can use these credentials to authenticate the following nodes:  - [Rundeck](../../app-nodes/n8n-nodes-base.rundeck/)  ## Prerequisites  Create a user account on a [Rundeck](https://www.rundeck.com/) server.  ## Supported authentication methods  - API token  ## Related resources  Refer to [Rundeck's API documentation](https://docs.rundeck.com/docs/api/) for more information about the service.  ## Using API token  To configure this credential, you'll need:  - Your **URL*...",
-        "sections": [
-          {
-            "title": "Rundeck credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Rundeck](../../app-nodes/n8n-nodes-base.rundeck/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "rundeck",
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using",
-          "token"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 873,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "rundeck credentials # rundeck credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [rundeck](../../app-nodes/n8n-nodes-base.rundeck/)\n\n## prerequisites\n\ncreate a user account on a [rundeck](https://www.rundeck.com/) server.\n\n## supported authentication methods\n\n- api token\n\n## related resources\n\nrefer to [rundeck's api documentation](https://docs.rundeck.com/docs/api/) for more information about the service.\n\n## using api token\n\nto configure this credential, you'll need:\n\n- your **url**: enter the base url of your rundeck server, for example `http://myserver:4440`. refer to [urls](https://docs.rundeck.com/docs/api/#urls) for more information.\n- a user api **token**: to generate a user api token, go to your **profile > user api tokens**. refer to [user api tokens](https://docs.rundeck.com/docs/manual/10-user.html#user-api-tokens) for more information.\n rundeck credentials",
-        "importantTerms": [
-          "rundeck",
-          "user",
-          "docs",
-          "credentials",
-          "https",
-          "token",
-          "nodes",
-          "refer",
-          "more",
-          "information",
-          "your",
-          "tokens"
-        ]
-      }
-    },
     {
       "id": "page-0944",
       "title": "Salesmate credentials",
@@ -93808,7 +93925,7 @@
         "page-0874",
         "page-0877",
         "page-0934",
-        "page-0942",
+        "page-0943",
         "page-0955",
         "page-0958",
         "page-1062",
@@ -93866,7 +93983,7 @@
         "page-0686",
         "page-0694",
         "page-0703",
-        "page-0942",
+        "page-0943",
         "page-1147",
         "page-1202",
         "page-1214",
@@ -93909,7 +94026,7 @@
         "page-0710",
         "page-0712",
         "page-0719",
-        "page-0942",
+        "page-0943",
         "page-1151",
         "page-1152",
         "page-1191",
@@ -94006,6 +94123,7 @@
         "page-0200",
         "page-0201",
         "page-0204",
+        "page-0205",
         "page-0208",
         "page-0227",
         "page-1205"
@@ -94066,6 +94184,7 @@
         "page-0195",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0206",
         "page-0208",
         "page-0813",
@@ -94197,6 +94316,7 @@
         "page-0201",
         "page-0202",
         "page-0203",
+        "page-0205",
         "page-0207",
         "page-0208",
         "page-0209",
@@ -94228,6 +94348,7 @@
         "page-0167",
         "page-0168",
         "page-0204",
+        "page-0205",
         "page-0210",
         "page-0211",
         "page-0213",
@@ -94509,7 +94630,7 @@
         "page-0862",
         "page-0863",
         "page-0864",
-        "page-0865",
+        "page-0866",
         "page-0867",
         "page-0868",
         "page-0869",
@@ -94796,6 +94917,7 @@
         "page-0200",
         "page-0201",
         "page-0202",
+        "page-0205",
         "page-0207",
         "page-0544",
         "page-0548",
@@ -94922,7 +95044,7 @@
         "page-0221",
         "page-0374",
         "page-0701",
-        "page-0942",
+        "page-0943",
         "page-1171",
         "page-1205",
         "page-1232"
@@ -96117,7 +96239,7 @@
         "page-0700",
         "page-0863",
         "page-0898",
-        "page-0942",
+        "page-0943",
         "page-1149",
         "page-1152",
         "page-1170",
@@ -96152,6 +96274,7 @@
         "page-0013",
         "page-0153",
         "page-0204",
+        "page-0205",
         "page-0206",
         "page-0208",
         "page-0348",
@@ -96333,6 +96456,7 @@
         "page-0166",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0208",
         "page-0232",
         "page-0540"
@@ -96715,6 +96839,7 @@
         "page-0200",
         "page-0201",
         "page-0202",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208",
@@ -96998,6 +97123,7 @@
         "page-0201",
         "page-0202",
         "page-0204",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208"
@@ -97068,6 +97194,7 @@
         "page-0195",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0206",
         "page-0208",
         "page-0701",
@@ -97516,7 +97643,7 @@
         "page-0796",
         "page-0843",
         "page-0884",
-        "page-0942",
+        "page-0943",
         "page-0987",
         "page-0997",
         "page-1003",
@@ -98231,6 +98358,7 @@
       "context": [
         "page-0015",
         "page-0201",
+        "page-0205",
         "page-0570",
         "page-1189",
         "page-1205"
@@ -98354,6 +98482,7 @@
         "page-0202",
         "page-0203",
         "page-0204",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208",
@@ -98380,7 +98509,7 @@
         "page-0778",
         "page-0799",
         "page-0800",
-        "page-0942",
+        "page-0943",
         "page-0968",
         "page-1011",
         "page-1027",
@@ -99095,6 +99224,7 @@
         "page-0067",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0219",
         "page-0220",
         "page-0227",
@@ -100181,7 +100311,7 @@
         "page-0925",
         "page-0933",
         "page-0938",
-        "page-0942",
+        "page-0943",
         "page-0954",
         "page-0955",
         "page-0958",
@@ -100217,7 +100347,7 @@
         "page-0874",
         "page-0877",
         "page-0913",
-        "page-0942",
+        "page-0943",
         "page-1027",
         "page-1028",
         "page-1205"
@@ -100283,7 +100413,7 @@
         "page-0924",
         "page-0937",
         "page-0940",
-        "page-0943",
+        "page-0941",
         "page-0944",
         "page-0952",
         "page-0955",
@@ -100875,6 +101005,7 @@
         "page-0030",
         "page-0166",
         "page-0204",
+        "page-0205",
         "page-0313",
         "page-0314",
         "page-0315",
@@ -101266,6 +101397,7 @@
         "page-0201",
         "page-0202",
         "page-0203",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208",
@@ -101284,6 +101416,7 @@
         "page-0201",
         "page-0202",
         "page-0203",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208",
@@ -101532,7 +101665,7 @@
         "page-0799",
         "page-0874",
         "page-0877",
-        "page-0942",
+        "page-0943",
         "page-0955",
         "page-0958",
         "page-0960",
@@ -102050,6 +102183,7 @@
         "page-0061",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0497",
         "page-0498",
         "page-0499",
@@ -102538,7 +102672,7 @@
         "page-0862",
         "page-0863",
         "page-0864",
-        "page-0865",
+        "page-0866",
         "page-0867",
         "page-0868",
         "page-0869",
@@ -102856,7 +102990,7 @@
         "page-0862",
         "page-0863",
         "page-0864",
-        "page-0865",
+        "page-0866",
         "page-0867",
         "page-0868",
         "page-0869",
@@ -103842,6 +103976,7 @@
         "page-0196",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0208",
         "page-0223",
         "page-0548",
@@ -104026,7 +104161,7 @@
         "page-0938",
         "page-0940",
         "page-0941",
-        "page-0943",
+        "page-0942",
         "page-0944",
         "page-0946",
         "page-0947",
@@ -104288,7 +104423,7 @@
         "page-0099",
         "page-0665",
         "page-0759",
-        "page-0941"
+        "page-0942"
       ],
       "versus": [
         "page-0099",
@@ -105738,6 +105873,7 @@
         "page-0200",
         "page-0201",
         "page-0203",
+        "page-0205",
         "page-0799",
         "page-1207"
       ],
@@ -105933,6 +106069,7 @@
         "page-0166",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0208"
       ],
       "plain": [
@@ -106147,6 +106284,7 @@
         "page-0180",
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0208",
         "page-0214",
         "page-0260",
@@ -106389,6 +106527,7 @@
         "page-0200",
         "page-0201",
         "page-0202",
+        "page-0205",
         "page-0207",
         "page-0664"
       ],
@@ -106396,6 +106535,7 @@
         "page-0200",
         "page-0201",
         "page-0202",
+        "page-0205",
         "page-0207",
         "page-1204",
         "page-1207",
@@ -106405,6 +106545,7 @@
         "page-0200",
         "page-0201",
         "page-0204",
+        "page-0205",
         "page-0519",
         "page-0520",
         "page-0522",
@@ -106416,20 +106557,24 @@
       "volume": [
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0207"
       ],
       "persistent": [
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0550"
       ],
       "deployments": [
         "page-0200",
-        "page-0201"
+        "page-0201",
+        "page-0205"
       ],
       "send": [
         "page-0200",
         "page-0201",
+        "page-0205",
         "page-0415",
         "page-0499",
         "page-0526",
@@ -106445,7 +106590,8 @@
         "page-1216"
       ],
       "kubectl": [
-        "page-0201"
+        "page-0201",
+        "page-0205"
       ],
       "digital": [
         "page-0202"
@@ -106455,7 +106601,7 @@
       ],
       "digitalocean": [
         "page-0202",
-        "page-0941"
+        "page-0942"
       ],
       "droplet": [
         "page-0202"
@@ -106654,6 +106800,9 @@
       "west1": [
         "page-0204"
       ],
+      "engine": [
+        "page-0205"
+      ],
       "heroku": [
         "page-0206"
       ],
@@ -107295,7 +107444,7 @@
       ],
       "(recommended)": [
         "page-0225",
-        "page-0942"
+        "page-0943"
       ],
       "pass": [
         "page-0225",
@@ -107346,7 +107495,7 @@
         "page-0931",
         "page-0934",
         "page-0939",
-        "page-0942",
+        "page-0943",
         "page-0980",
         "page-1003",
         "page-1009",
@@ -108522,7 +108671,7 @@
       ],
       "mandrill": [
         "page-0365",
-        "page-0865"
+        "page-0866"
       ],
       "marketstack": [
         "page-0366",
@@ -108827,15 +108976,15 @@
       ],
       "rundeck": [
         "page-0430",
-        "page-0943"
+        "page-0941"
       ],
       "wasabi": [
         "page-0431",
-        "page-0941"
+        "page-0942"
       ],
       "salesforce": [
         "page-0432",
-        "page-0942",
+        "page-0943",
         "page-1102",
         "page-1205"
       ],
@@ -109966,7 +110115,7 @@
       "connected": [
         "page-0561",
         "page-0569",
-        "page-0942"
+        "page-0943"
       ],
       "conversational": [
         "page-0562"
@@ -111114,7 +111263,7 @@
         "page-0863"
       ],
       "malcore": [
-        "page-0866"
+        "page-0865"
       ],
       "(general)": [
         "page-0874"
@@ -111196,13 +111345,13 @@
         "page-0937"
       ],
       "spaces": [
-        "page-0941"
+        "page-0942"
       ],
       "(legacy)": [
-        "page-0942"
+        "page-0943"
       ],
       "authenticating": [
-        "page-0942"
+        "page-0943"
       ],
       "sekoia": [
         "page-0949"
@@ -113049,6 +113198,7 @@
         "page-0202",
         "page-0203",
         "page-0204",
+        "page-0205",
         "page-0206",
         "page-0207",
         "page-0208",