@n8n-as-code/skills 1.3.0-next.13 → 1.3.1

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-03-30T10:56:41.465Z",
+  "generatedAt": "2026-03-30T12:55:10.618Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
   "totalPages": 1260,
@@ -36516,59 +36516,6 @@
     },
     {
       "id": "page-0485",
-      "title": "Zulip",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.zulip/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.zulip/index.md",
-      "category": "integrations",
-      "subcategory": "app-nodes",
-      "nodeName": "zulip",
-      "nodeType": "n8n-nodes-base.zulip",
-      "content": {
-        "markdown": "# Zulip node\n\nUse the Zulip node to automate work in Zulip, and integrate Zulip with other applications. n8n has built-in support for a wide range of Zulip features, including creating, deleting, and getting users and streams, as well as sending messages.\n\nOn this page, you'll find a list of operations the Zulip node supports and links to more resources.\n\nCredentials\n\nRefer to [Zulip credentials](../../credentials/zulip/) for guidance on setting up authentication.\n\n## Operations\n\n- Message\n  - Delete a message\n  - Get a message\n  - Send a private message\n  - Send a message to stream\n  - Update a message\n  - Upload a file\n- Stream\n  - Create a stream.\n  - Delete a stream.\n  - Get all streams.\n  - Get subscribed streams.\n  - Update a stream.\n- User\n  - Create a user.\n  - Deactivate a user.\n  - Get a user.\n  - Get all users.\n  - Update a user.\n\n## Templates and examples\n\n[Browse Zulip integration templates](https://n8n.io/integrations/zulip/), or [search all templates](https://n8n.io/workflows/)\n",
-        "excerpt": "# Zulip node  Use the Zulip node to automate work in Zulip, and integrate Zulip with other applications. n8n has built-in support for a wide range of Zulip features, including creating, deleting, and getting users and streams, as well as sending messages.  On this page, you'll find a list of operations the Zulip node supports and links to more resources.  Credentials  Refer to [Zulip credentials](../../credentials/zulip/) for guidance on setting up authentication.  ## Operations  - Message   - D...",
-        "sections": [
-          {
-            "title": "Zulip node",
-            "level": 1,
-            "content": "Use the Zulip node to automate work in Zulip, and integrate Zulip with other applications. n8n has built-in support for a wide range of Zulip features, including creating, deleting, and getting users and streams, as well as sending messages.\n\nOn this page, you'll find a list of operations the Zulip node supports and links to more resources.\n\nCredentials\n\nRefer to [Zulip credentials](../../credentials/zulip/) for guidance on setting up authentication."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "zulip",
-          "node",
-          "operations",
-          "templates",
-          "examples"
-        ],
-        "useCases": [],
-        "operations": [
-          ""
-        ],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 1008,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "zulip # zulip node\n\nuse the zulip node to automate work in zulip, and integrate zulip with other applications. n8n has built-in support for a wide range of zulip features, including creating, deleting, and getting users and streams, as well as sending messages.\n\non this page, you'll find a list of operations the zulip node supports and links to more resources.\n\ncredentials\n\nrefer to [zulip credentials](../../credentials/zulip/) for guidance on setting up authentication.\n\n## operations\n\n- message\n  - delete a message\n  - get a message\n  - send a private message\n  - send a message to stream\n  - update a message\n  - upload a file\n- stream\n  - create a stream.\n  - delete a stream.\n  - get all streams.\n  - get subscribed streams.\n  - update a stream.\n- user\n  - create a user.\n  - deactivate a user.\n  - get a user.\n  - get all users.\n  - update a user.\n\n## templates and examples\n\n[browse zulip integration templates](https://n8n.io/integrations/zulip/), or [search all templates](https://n8n.io/workflows/)\n zulip node",
-        "importantTerms": [
-          "zulip",
-          "message",
-          "stream",
-          "user",
-          "node",
-          "streams",
-          "credentials",
-          "update",
-          "templates"
-        ]
-      }
-    },
-    {
-      "id": "page-0486",
       "title": "Anthropic",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-langchain.anthropic/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-langchain.anthropic/index.md",
@@ -36646,7 +36593,7 @@
       }
     },
     {
-      "id": "page-0487",
+      "id": "page-0486",
       "title": "Google Gemini",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-langchain.googlegemini/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-langchain.googlegemini/index.md",
@@ -36742,6 +36689,59 @@
         ]
       }
     },
+    {
+      "id": "page-0487",
+      "title": "Zulip",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.zulip/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.zulip/index.md",
+      "category": "integrations",
+      "subcategory": "app-nodes",
+      "nodeName": "zulip",
+      "nodeType": "n8n-nodes-base.zulip",
+      "content": {
+        "markdown": "# Zulip node\n\nUse the Zulip node to automate work in Zulip, and integrate Zulip with other applications. n8n has built-in support for a wide range of Zulip features, including creating, deleting, and getting users and streams, as well as sending messages.\n\nOn this page, you'll find a list of operations the Zulip node supports and links to more resources.\n\nCredentials\n\nRefer to [Zulip credentials](../../credentials/zulip/) for guidance on setting up authentication.\n\n## Operations\n\n- Message\n  - Delete a message\n  - Get a message\n  - Send a private message\n  - Send a message to stream\n  - Update a message\n  - Upload a file\n- Stream\n  - Create a stream.\n  - Delete a stream.\n  - Get all streams.\n  - Get subscribed streams.\n  - Update a stream.\n- User\n  - Create a user.\n  - Deactivate a user.\n  - Get a user.\n  - Get all users.\n  - Update a user.\n\n## Templates and examples\n\n[Browse Zulip integration templates](https://n8n.io/integrations/zulip/), or [search all templates](https://n8n.io/workflows/)\n",
+        "excerpt": "# Zulip node  Use the Zulip node to automate work in Zulip, and integrate Zulip with other applications. n8n has built-in support for a wide range of Zulip features, including creating, deleting, and getting users and streams, as well as sending messages.  On this page, you'll find a list of operations the Zulip node supports and links to more resources.  Credentials  Refer to [Zulip credentials](../../credentials/zulip/) for guidance on setting up authentication.  ## Operations  - Message   - D...",
+        "sections": [
+          {
+            "title": "Zulip node",
+            "level": 1,
+            "content": "Use the Zulip node to automate work in Zulip, and integrate Zulip with other applications. n8n has built-in support for a wide range of Zulip features, including creating, deleting, and getting users and streams, as well as sending messages.\n\nOn this page, you'll find a list of operations the Zulip node supports and links to more resources.\n\nCredentials\n\nRefer to [Zulip credentials](../../credentials/zulip/) for guidance on setting up authentication."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "zulip",
+          "node",
+          "operations",
+          "templates",
+          "examples"
+        ],
+        "useCases": [],
+        "operations": [
+          ""
+        ],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 1008,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "zulip # zulip node\n\nuse the zulip node to automate work in zulip, and integrate zulip with other applications. n8n has built-in support for a wide range of zulip features, including creating, deleting, and getting users and streams, as well as sending messages.\n\non this page, you'll find a list of operations the zulip node supports and links to more resources.\n\ncredentials\n\nrefer to [zulip credentials](../../credentials/zulip/) for guidance on setting up authentication.\n\n## operations\n\n- message\n  - delete a message\n  - get a message\n  - send a private message\n  - send a message to stream\n  - update a message\n  - upload a file\n- stream\n  - create a stream.\n  - delete a stream.\n  - get all streams.\n  - get subscribed streams.\n  - update a stream.\n- user\n  - create a user.\n  - deactivate a user.\n  - get a user.\n  - get all users.\n  - update a user.\n\n## templates and examples\n\n[browse zulip integration templates](https://n8n.io/integrations/zulip/), or [search all templates](https://n8n.io/workflows/)\n zulip node",
+        "importantTerms": [
+          "zulip",
+          "message",
+          "stream",
+          "user",
+          "node",
+          "streams",
+          "credentials",
+          "update",
+          "templates"
+        ]
+      }
+    },
     {
       "id": "page-0488",
       "title": "Perplexity",
@@ -37756,76 +37756,6 @@
     },
     {
       "id": "page-0499",
-      "title": "Google Calendar",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/index.md",
-      "category": "integrations",
-      "subcategory": "app-nodes",
-      "nodeName": "googlecalendar",
-      "nodeType": "n8n-nodes-base.googlecalendar",
-      "content": {
-        "markdown": "# Google Calendar node\n\nUse the Google Calendar node to automate work in Google Calendar, and integrate Google Calendar with other applications. n8n has built-in support for a wide range of Google Calendar features, including adding, retrieving, deleting and updating calendar events.\n\nOn this page, you'll find a list of operations the Google Calendar node supports and links to more resources.\n\nCredentials\n\nRefer to [Google Calendar credentials](../../credentials/google/) 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- **Calendar**\n  - [**Availability**](calendar-operations/#availability): If a time-slot is available in a calendar\n- **Event**\n  - [**Create**](event-operations/#create): Add an event to calendar\n  - [**Delete**](event-operations/#delete): Delete an event\n  - [**Get**](event-operations/#get): Retrieve an event\n  - [**Get Many**](event-operations/#get-many): Retrieve all events from a calendar\n  - [**Update**](event-operations/#update): Update an event\n\n## Templates and examples\n\n**AI Agent : Google calendar assistant using OpenAI**\n\nby Dataki\n\n[View template details](https://n8n.io/workflows/2703-ai-agent-google-calendar-assistant-using-openai/)\n\n**Build an MCP Server with Google Calendar and Custom Functions**\n\nby Solomon\n\n[View template details](https://n8n.io/workflows/3514-build-an-mcp-server-with-google-calendar-and-custom-functions/)\n\n**Actioning Your Meeting Next Steps using Transcripts and AI**\n\nby Jimleuk\n\n[View template details](https://n8n.io/workflows/2328-actioning-your-meeting-next-steps-using-transcripts-and-ai/)\n\n[Browse Google Calendar integration templates](https://n8n.io/integrations/google-calendar/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nn8n provides a trigger node for Google Calendar. You can find the trigger node docs [here](../../trigger-nodes/n8n-nodes-base.googlecalendartrigger/).\n\nRefer to [Google Calendar's documentation](https://developers.google.com/calendar/api/v3/reference) for more information about the service.\n\nView [example workflows and related content](https://n8n.io/integrations/google-calendar/) on n8n's website.\n",
-        "excerpt": "# Google Calendar node  Use the Google Calendar node to automate work in Google Calendar, and integrate Google Calendar with other applications. n8n has built-in support for a wide range of Google Calendar features, including adding, retrieving, deleting and updating calendar events.  On this page, you'll find a list of operations the Google Calendar node supports and links to more resources.  Credentials  Refer to [Google Calendar credentials](../../credentials/google/) for guidance on setting...",
-        "sections": [
-          {
-            "title": "Google Calendar node",
-            "level": 1,
-            "content": "Use the Google Calendar node to automate work in Google Calendar, and integrate Google Calendar with other applications. n8n has built-in support for a wide range of Google Calendar features, including adding, retrieving, deleting and updating calendar events.\n\nOn this page, you'll find a list of operations the Google Calendar node supports and links to more resources.\n\nCredentials\n\nRefer to [Google Calendar credentials](../../credentials/google/) 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/)."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "google",
-          "calendar",
-          "node",
-          "operations",
-          "templates",
-          "examples",
-          "related",
-          "resources"
-        ],
-        "useCases": [],
-        "operations": [
-          ""
-        ],
-        "codeExamples": 0,
-        "complexity": "intermediate",
-        "readingTime": "2 min",
-        "contentLength": 2477,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "google calendar # google calendar node\n\nuse the google calendar node to automate work in google calendar, and integrate google calendar with other applications. n8n has built-in support for a wide range of google calendar features, including adding, retrieving, deleting and updating calendar events.\n\non this page, you'll find a list of operations the google calendar node supports and links to more resources.\n\ncredentials\n\nrefer to [google calendar credentials](../../credentials/google/) 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- **calendar**\n  - [**availability**](calendar-operations/#availability): if a time-slot is available in a calendar\n- **event**\n  - [**create**](event-operations/#create): add an event to calendar\n  - [**delete**](event-operations/#delete): delete an event\n  - [**get**](event-operations/#get): retrieve an event\n  - [**get many**](event-operations/#get-many): retrieve all events from a calendar\n  - [**update**](event-operations/#update): update an event\n\n## templates and examples\n\n**ai agent : google calendar assistant using openai**\n\nby dataki\n\n[view template details](https://n8n.io/workflows/2703-ai-agent-google-calendar-assistant-using-openai/)\n\n**build an mcp server with google calendar and custom functions**\n\nby solomon\n\n[view template details](https://n8n.io/workflows/3514-build-an-mcp-server-with-google-calendar-and-custom-functions/)\n\n**actioning your meeting next steps using transcripts and ai**\n\nby jimleuk\n\n[view template details](https://n8n.io/workflows/2328-actioning-your-meeting-next-steps-using-transcripts-and-ai/)\n\n[browse google calendar integration templates](https://n8n.io/integrations/google-calendar/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nn8n provides a trigger node for google calendar. you can find the trigger node docs [here](../../trigger-nodes/n8n-nodes-base.googlecalendartrigger/).\n\nrefer to [google calendar's documentation](https://developers.google.com/calendar/api/v3/reference) for more information about the service.\n\nview [example workflows and related content](https://n8n.io/integrations/google-calendar/) on n8n's website.\n google calendar node",
-        "importantTerms": [
-          "calendar",
-          "google",
-          "event",
-          "node",
-          "operations",
-          "https",
-          "using",
-          "workflows",
-          "with",
-          "this",
-          "view",
-          "find",
-          "more",
-          "credentials",
-          "used",
-          "agent",
-          "many",
-          "delete",
-          "update",
-          "templates",
-          "template",
-          "details",
-          "trigger"
-        ]
-      }
-    },
-    {
-      "id": "page-0500",
       "title": "Calendar operations",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/calendar-operations/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/calendar-operations/index.md",
@@ -37883,7 +37813,7 @@
       }
     },
     {
-      "id": "page-0501",
+      "id": "page-0500",
       "title": "Event operations",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/event-operations/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/event-operations/index.md",
@@ -37979,7 +37909,7 @@
       }
     },
     {
-      "id": "page-0502",
+      "id": "page-0501",
       "title": "Google Drive",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googledrive/index.md",
@@ -38065,6 +37995,76 @@
         ]
       }
     },
+    {
+      "id": "page-0502",
+      "title": "Google Calendar",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/index.md",
+      "category": "integrations",
+      "subcategory": "app-nodes",
+      "nodeName": "googlecalendar",
+      "nodeType": "n8n-nodes-base.googlecalendar",
+      "content": {
+        "markdown": "# Google Calendar node\n\nUse the Google Calendar node to automate work in Google Calendar, and integrate Google Calendar with other applications. n8n has built-in support for a wide range of Google Calendar features, including adding, retrieving, deleting and updating calendar events.\n\nOn this page, you'll find a list of operations the Google Calendar node supports and links to more resources.\n\nCredentials\n\nRefer to [Google Calendar credentials](../../credentials/google/) 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- **Calendar**\n  - [**Availability**](calendar-operations/#availability): If a time-slot is available in a calendar\n- **Event**\n  - [**Create**](event-operations/#create): Add an event to calendar\n  - [**Delete**](event-operations/#delete): Delete an event\n  - [**Get**](event-operations/#get): Retrieve an event\n  - [**Get Many**](event-operations/#get-many): Retrieve all events from a calendar\n  - [**Update**](event-operations/#update): Update an event\n\n## Templates and examples\n\n**AI Agent : Google calendar assistant using OpenAI**\n\nby Dataki\n\n[View template details](https://n8n.io/workflows/2703-ai-agent-google-calendar-assistant-using-openai/)\n\n**Build an MCP Server with Google Calendar and Custom Functions**\n\nby Solomon\n\n[View template details](https://n8n.io/workflows/3514-build-an-mcp-server-with-google-calendar-and-custom-functions/)\n\n**Actioning Your Meeting Next Steps using Transcripts and AI**\n\nby Jimleuk\n\n[View template details](https://n8n.io/workflows/2328-actioning-your-meeting-next-steps-using-transcripts-and-ai/)\n\n[Browse Google Calendar integration templates](https://n8n.io/integrations/google-calendar/), or [search all templates](https://n8n.io/workflows/)\n\n## Related resources\n\nn8n provides a trigger node for Google Calendar. You can find the trigger node docs [here](../../trigger-nodes/n8n-nodes-base.googlecalendartrigger/).\n\nRefer to [Google Calendar's documentation](https://developers.google.com/calendar/api/v3/reference) for more information about the service.\n\nView [example workflows and related content](https://n8n.io/integrations/google-calendar/) on n8n's website.\n",
+        "excerpt": "# Google Calendar node  Use the Google Calendar node to automate work in Google Calendar, and integrate Google Calendar with other applications. n8n has built-in support for a wide range of Google Calendar features, including adding, retrieving, deleting and updating calendar events.  On this page, you'll find a list of operations the Google Calendar node supports and links to more resources.  Credentials  Refer to [Google Calendar credentials](../../credentials/google/) for guidance on setting...",
+        "sections": [
+          {
+            "title": "Google Calendar node",
+            "level": 1,
+            "content": "Use the Google Calendar node to automate work in Google Calendar, and integrate Google Calendar with other applications. n8n has built-in support for a wide range of Google Calendar features, including adding, retrieving, deleting and updating calendar events.\n\nOn this page, you'll find a list of operations the Google Calendar node supports and links to more resources.\n\nCredentials\n\nRefer to [Google Calendar credentials](../../credentials/google/) 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/)."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "google",
+          "calendar",
+          "node",
+          "operations",
+          "templates",
+          "examples",
+          "related",
+          "resources"
+        ],
+        "useCases": [],
+        "operations": [
+          ""
+        ],
+        "codeExamples": 0,
+        "complexity": "intermediate",
+        "readingTime": "2 min",
+        "contentLength": 2477,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "google calendar # google calendar node\n\nuse the google calendar node to automate work in google calendar, and integrate google calendar with other applications. n8n has built-in support for a wide range of google calendar features, including adding, retrieving, deleting and updating calendar events.\n\non this page, you'll find a list of operations the google calendar node supports and links to more resources.\n\ncredentials\n\nrefer to [google calendar credentials](../../credentials/google/) 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- **calendar**\n  - [**availability**](calendar-operations/#availability): if a time-slot is available in a calendar\n- **event**\n  - [**create**](event-operations/#create): add an event to calendar\n  - [**delete**](event-operations/#delete): delete an event\n  - [**get**](event-operations/#get): retrieve an event\n  - [**get many**](event-operations/#get-many): retrieve all events from a calendar\n  - [**update**](event-operations/#update): update an event\n\n## templates and examples\n\n**ai agent : google calendar assistant using openai**\n\nby dataki\n\n[view template details](https://n8n.io/workflows/2703-ai-agent-google-calendar-assistant-using-openai/)\n\n**build an mcp server with google calendar and custom functions**\n\nby solomon\n\n[view template details](https://n8n.io/workflows/3514-build-an-mcp-server-with-google-calendar-and-custom-functions/)\n\n**actioning your meeting next steps using transcripts and ai**\n\nby jimleuk\n\n[view template details](https://n8n.io/workflows/2328-actioning-your-meeting-next-steps-using-transcripts-and-ai/)\n\n[browse google calendar integration templates](https://n8n.io/integrations/google-calendar/), or [search all templates](https://n8n.io/workflows/)\n\n## related resources\n\nn8n provides a trigger node for google calendar. you can find the trigger node docs [here](../../trigger-nodes/n8n-nodes-base.googlecalendartrigger/).\n\nrefer to [google calendar's documentation](https://developers.google.com/calendar/api/v3/reference) for more information about the service.\n\nview [example workflows and related content](https://n8n.io/integrations/google-calendar/) on n8n's website.\n google calendar node",
+        "importantTerms": [
+          "calendar",
+          "google",
+          "event",
+          "node",
+          "operations",
+          "https",
+          "using",
+          "workflows",
+          "with",
+          "this",
+          "view",
+          "find",
+          "more",
+          "credentials",
+          "used",
+          "agent",
+          "many",
+          "delete",
+          "update",
+          "templates",
+          "template",
+          "details",
+          "trigger"
+        ]
+      }
+    },
     {
       "id": "page-0503",
       "title": "Common issues",
@@ -52979,6 +52979,73 @@
     },
     {
       "id": "page-0676",
+      "title": "Rename Keys",
+      "url": "https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.renamekeys/index.md",
+      "urlPath": "integrations/builtin/core-nodes/n8n-nodes-base.renamekeys/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": "renamekeys",
+      "nodeType": "n8n-nodes-base.renamekeys",
+      "content": {
+        "markdown": "# Rename Keys\n\nUse the Rename Keys node to rename the keys of a key-value pair in n8n.\n\n## Node parameters\n\nYou can rename one or multiple keys using the Rename Keys node. Select the **Add new key** button to rename a key.\n\nFor each key, enter the:\n\n- **Current Key Name**: The current name of the key you want to rename.\n- **New Key Name**: The new name you want to assign to the key.\n\n## Node options\n\nChoose whether to use a **Regex** regular expression to identify keys to rename. To use this option, you must also enter:\n\n- The **Regular Expression** you'd like to use.\n- **Replace With**: Enter the new name you want to assign to the key(s) that match the **Regular Expression**.\n- You can also choose these Regex-specific options:\n  - **Case Insensitive**: Set whether the regular expression should match case (turned off) or be case insensitive (turned on).\n  - **Max Depth**: Enter the maximum depth to replace keys, using `-1` for unlimited and `0` for top-level only.\n\nRegex impacts\n\nUsing a regular expression can affect any keys that match the expression, including keys you've already renamed.\n\n## Templates and examples\n\n**Explore n8n Nodes in a Visual Reference Library**\n\nby I versus AI\n\n[View template details](https://n8n.io/workflows/3891-explore-n8n-nodes-in-a-visual-reference-library/)\n\n**Create Salesforce accounts based on Google Sheets data**\n\nby Tom\n\n[View template details](https://n8n.io/workflows/1792-create-salesforce-accounts-based-on-google-sheets-data/)\n\n**Create Salesforce accounts based on Excel 365 data**\n\nby Tom\n\n[View template details](https://n8n.io/workflows/1793-create-salesforce-accounts-based-on-excel-365-data/)\n\n[Browse Rename Keys integration templates](https://n8n.io/integrations/rename-keys/), or [search all templates](https://n8n.io/workflows/)\n",
+        "excerpt": "# Rename Keys  Use the Rename Keys node to rename the keys of a key-value pair in n8n.  ## Node parameters  You can rename one or multiple keys using the Rename Keys node. Select the **Add new key** button to rename a key.  For each key, enter the:  - **Current Key Name**: The current name of the key you want to rename. - **New Key Name**: The new name you want to assign to the key.  ## Node options  Choose whether to use a **Regex** regular expression to identify keys to rename. To use this opt...",
+        "sections": [
+          {
+            "title": "Rename Keys",
+            "level": 1,
+            "content": "Use the Rename Keys node to rename the keys of a key-value pair in n8n."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "rename",
+          "keys",
+          "node",
+          "parameters",
+          "options",
+          "templates",
+          "examples"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 1801,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "rename keys # rename keys\n\nuse the rename keys node to rename the keys of a key-value pair in n8n.\n\n## node parameters\n\nyou can rename one or multiple keys using the rename keys node. select the **add new key** button to rename a key.\n\nfor each key, enter the:\n\n- **current key name**: the current name of the key you want to rename.\n- **new key name**: the new name you want to assign to the key.\n\n## node options\n\nchoose whether to use a **regex** regular expression to identify keys to rename. to use this option, you must also enter:\n\n- the **regular expression** you'd like to use.\n- **replace with**: enter the new name you want to assign to the key(s) that match the **regular expression**.\n- you can also choose these regex-specific options:\n  - **case insensitive**: set whether the regular expression should match case (turned off) or be case insensitive (turned on).\n  - **max depth**: enter the maximum depth to replace keys, using `-1` for unlimited and `0` for top-level only.\n\nregex impacts\n\nusing a regular expression can affect any keys that match the expression, including keys you've already renamed.\n\n## templates and examples\n\n**explore n8n nodes in a visual reference library**\n\nby i versus ai\n\n[view template details](https://n8n.io/workflows/3891-explore-n8n-nodes-in-a-visual-reference-library/)\n\n**create salesforce accounts based on google sheets data**\n\nby tom\n\n[view template details](https://n8n.io/workflows/1792-create-salesforce-accounts-based-on-google-sheets-data/)\n\n**create salesforce accounts based on excel 365 data**\n\nby tom\n\n[view template details](https://n8n.io/workflows/1793-create-salesforce-accounts-based-on-excel-365-data/)\n\n[browse rename keys integration templates](https://n8n.io/integrations/rename-keys/), or [search all templates](https://n8n.io/workflows/)\n rename keys",
+        "importantTerms": [
+          "keys",
+          "rename",
+          "expression",
+          "name",
+          "regular",
+          "https",
+          "node",
+          "enter",
+          "workflows",
+          "create",
+          "salesforce",
+          "accounts",
+          "based",
+          "data",
+          "using",
+          "want",
+          "regex",
+          "match",
+          "case",
+          "templates",
+          "view",
+          "template",
+          "details"
+        ]
+      }
+    },
+    {
+      "id": "page-0677",
       "title": "Read/Write Files from Disk",
       "url": "https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.readwritefile/index.md",
       "urlPath": "integrations/builtin/core-nodes/n8n-nodes-base.readwritefile/index.md",
@@ -53068,73 +53135,6 @@
         ]
       }
     },
-    {
-      "id": "page-0677",
-      "title": "Rename Keys",
-      "url": "https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.renamekeys/index.md",
-      "urlPath": "integrations/builtin/core-nodes/n8n-nodes-base.renamekeys/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": "renamekeys",
-      "nodeType": "n8n-nodes-base.renamekeys",
-      "content": {
-        "markdown": "# Rename Keys\n\nUse the Rename Keys node to rename the keys of a key-value pair in n8n.\n\n## Node parameters\n\nYou can rename one or multiple keys using the Rename Keys node. Select the **Add new key** button to rename a key.\n\nFor each key, enter the:\n\n- **Current Key Name**: The current name of the key you want to rename.\n- **New Key Name**: The new name you want to assign to the key.\n\n## Node options\n\nChoose whether to use a **Regex** regular expression to identify keys to rename. To use this option, you must also enter:\n\n- The **Regular Expression** you'd like to use.\n- **Replace With**: Enter the new name you want to assign to the key(s) that match the **Regular Expression**.\n- You can also choose these Regex-specific options:\n  - **Case Insensitive**: Set whether the regular expression should match case (turned off) or be case insensitive (turned on).\n  - **Max Depth**: Enter the maximum depth to replace keys, using `-1` for unlimited and `0` for top-level only.\n\nRegex impacts\n\nUsing a regular expression can affect any keys that match the expression, including keys you've already renamed.\n\n## Templates and examples\n\n**Explore n8n Nodes in a Visual Reference Library**\n\nby I versus AI\n\n[View template details](https://n8n.io/workflows/3891-explore-n8n-nodes-in-a-visual-reference-library/)\n\n**Create Salesforce accounts based on Google Sheets data**\n\nby Tom\n\n[View template details](https://n8n.io/workflows/1792-create-salesforce-accounts-based-on-google-sheets-data/)\n\n**Create Salesforce accounts based on Excel 365 data**\n\nby Tom\n\n[View template details](https://n8n.io/workflows/1793-create-salesforce-accounts-based-on-excel-365-data/)\n\n[Browse Rename Keys integration templates](https://n8n.io/integrations/rename-keys/), or [search all templates](https://n8n.io/workflows/)\n",
-        "excerpt": "# Rename Keys  Use the Rename Keys node to rename the keys of a key-value pair in n8n.  ## Node parameters  You can rename one or multiple keys using the Rename Keys node. Select the **Add new key** button to rename a key.  For each key, enter the:  - **Current Key Name**: The current name of the key you want to rename. - **New Key Name**: The new name you want to assign to the key.  ## Node options  Choose whether to use a **Regex** regular expression to identify keys to rename. To use this opt...",
-        "sections": [
-          {
-            "title": "Rename Keys",
-            "level": 1,
-            "content": "Use the Rename Keys node to rename the keys of a key-value pair in n8n."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "rename",
-          "keys",
-          "node",
-          "parameters",
-          "options",
-          "templates",
-          "examples"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 1801,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "rename keys # rename keys\n\nuse the rename keys node to rename the keys of a key-value pair in n8n.\n\n## node parameters\n\nyou can rename one or multiple keys using the rename keys node. select the **add new key** button to rename a key.\n\nfor each key, enter the:\n\n- **current key name**: the current name of the key you want to rename.\n- **new key name**: the new name you want to assign to the key.\n\n## node options\n\nchoose whether to use a **regex** regular expression to identify keys to rename. to use this option, you must also enter:\n\n- the **regular expression** you'd like to use.\n- **replace with**: enter the new name you want to assign to the key(s) that match the **regular expression**.\n- you can also choose these regex-specific options:\n  - **case insensitive**: set whether the regular expression should match case (turned off) or be case insensitive (turned on).\n  - **max depth**: enter the maximum depth to replace keys, using `-1` for unlimited and `0` for top-level only.\n\nregex impacts\n\nusing a regular expression can affect any keys that match the expression, including keys you've already renamed.\n\n## templates and examples\n\n**explore n8n nodes in a visual reference library**\n\nby i versus ai\n\n[view template details](https://n8n.io/workflows/3891-explore-n8n-nodes-in-a-visual-reference-library/)\n\n**create salesforce accounts based on google sheets data**\n\nby tom\n\n[view template details](https://n8n.io/workflows/1792-create-salesforce-accounts-based-on-google-sheets-data/)\n\n**create salesforce accounts based on excel 365 data**\n\nby tom\n\n[view template details](https://n8n.io/workflows/1793-create-salesforce-accounts-based-on-excel-365-data/)\n\n[browse rename keys integration templates](https://n8n.io/integrations/rename-keys/), or [search all templates](https://n8n.io/workflows/)\n rename keys",
-        "importantTerms": [
-          "keys",
-          "rename",
-          "expression",
-          "name",
-          "regular",
-          "https",
-          "node",
-          "enter",
-          "workflows",
-          "create",
-          "salesforce",
-          "accounts",
-          "based",
-          "data",
-          "using",
-          "want",
-          "regex",
-          "match",
-          "case",
-          "templates",
-          "view",
-          "template",
-          "details"
-        ]
-      }
-    },
     {
       "id": "page-0678",
       "title": "Respond to Webhook",
@@ -85313,76 +85313,6 @@
     },
     {
       "id": "page-1175",
-      "title": "Structure",
-      "url": "https://docs.n8n.io/integrations/creating-nodes/build/reference/node-base-files/structure/index.md",
-      "urlPath": "integrations/creating-nodes/build/reference/node-base-files/structure/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Structure of the node base file\n\nThe node base file follows this basic structure:\n\n1. Add import statements.\n1. Create a class for the node.\n1. Within the node class, create a `description` object, which defines the node.\n\nA programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. The declarative style handles this using the `routing` key in the `properties` object, within `descriptions`.\n\n## Outline structure for a declarative-style node\n\nThis code snippet gives an outline of the node structure.\n\n```\nimport { INodeType, INodeTypeDescription } from 'n8n-workflow';\n\nexport class ExampleNode implements INodeType {\n\tdescription: INodeTypeDescription = {\n\t\t// Basic node details here\n\t\tproperties: [\n\t\t\t// Resources and operations here\n\t\t]\n\t};\n}\n```\n\nRefer to [Standard parameters](../standard-parameters/) for information on parameters available to all node types. Refer to [Declarative-style parameters](../declarative-style-parameters/) for the parameters available for declarative-style nodes.\n\n## Outline structure for a programmatic-style node\n\nThis code snippet gives an outline of the node structure.\n\n```\nimport { IExecuteFunctions } from 'n8n-core';\nimport { INodeExecutionData, INodeType, INodeTypeDescription } from 'n8n-workflow';\n\nexport class ExampleNode implements INodeType {\n\tdescription: INodeTypeDescription = {\n    // Basic node details here\n    properties: [\n      // Resources and operations here\n    ]\n  };\n\n  async execute(this: IExecuteFunctions): Promise<INodeExecutionData[][]> {\n    // Process data and return\n  }\n};\n```\n\nRefer to [Standard parameters](../standard-parameters/) for information on parameters available to all node types. Refer to [Programmatic-style parameters](../programmatic-style-parameters/) and [Programmatic-style execute method](../programmatic-style-execute-method/) for more information on working with programmatic-style nodes.\n",
-        "excerpt": "# Structure of the node base file  The node base file follows this basic structure:  1. Add import statements. 1. Create a class for the node. 1. Within the node class, create a `description` object, which defines the node.  A programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. The declarative style handles this using the `routing` key in the `properties` object, within `descriptions`.  ## Outline structure for a declarative-st...",
-        "sections": [
-          {
-            "title": "Structure of the node base file",
-            "level": 1,
-            "content": "The node base file follows this basic structure:\n\n1. Add import statements.\n1. Create a class for the node.\n1. Within the node class, create a `description` object, which defines the node.\n\nA programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. The declarative style handles this using the `routing` key in the `properties` object, within `descriptions`."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "structure",
-          "node",
-          "base",
-          "file",
-          "outline",
-          "declarative",
-          "style",
-          "programmatic"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 2,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 1954,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "structure # structure of the node base file\n\nthe node base file follows this basic structure:\n\n1. add import statements.\n1. create a class for the node.\n1. within the node class, create a `description` object, which defines the node.\n\na programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. the declarative style handles this using the `routing` key in the `properties` object, within `descriptions`.\n\n## outline structure for a declarative-style node\n\nthis code snippet gives an outline of the node structure.\n\n```\nimport { inodetype, inodetypedescription } from 'n8n-workflow';\n\nexport class examplenode implements inodetype {\n\tdescription: inodetypedescription = {\n\t\t// basic node details here\n\t\tproperties: [\n\t\t\t// resources and operations here\n\t\t]\n\t};\n}\n```\n\nrefer to [standard parameters](../standard-parameters/) for information on parameters available to all node types. refer to [declarative-style parameters](../declarative-style-parameters/) for the parameters available for declarative-style nodes.\n\n## outline structure for a programmatic-style node\n\nthis code snippet gives an outline of the node structure.\n\n```\nimport { iexecutefunctions } from 'n8n-core';\nimport { inodeexecutiondata, inodetype, inodetypedescription } from 'n8n-workflow';\n\nexport class examplenode implements inodetype {\n\tdescription: inodetypedescription = {\n    // basic node details here\n    properties: [\n      // resources and operations here\n    ]\n  };\n\n  async execute(this: iexecutefunctions): promise<inodeexecutiondata[][]> {\n    // process data and return\n  }\n};\n```\n\nrefer to [standard parameters](../standard-parameters/) for information on parameters available to all node types. refer to [programmatic-style parameters](../programmatic-style-parameters/) and [programmatic-style execute method](../programmatic-style-execute-method/) for more information on working with programmatic-style nodes.\n structure of the node base file",
-        "importantTerms": [
-          "node",
-          "style",
-          "parameters",
-          "structure",
-          "programmatic",
-          "this",
-          "declarative",
-          "import",
-          "class",
-          "execute",
-          "outline",
-          "inodetype",
-          "inodetypedescription",
-          "here",
-          "refer",
-          "standard",
-          "base",
-          "file",
-          "basic",
-          "description",
-          "method",
-          "properties",
-          "from",
-          "information",
-          "available"
-        ]
-      }
-    },
-    {
-      "id": "page-1176",
       "title": "Deploy a node",
       "url": "https://docs.n8n.io/integrations/creating-nodes/deploy/index.md",
       "urlPath": "integrations/creating-nodes/deploy/index.md",
@@ -85428,7 +85358,7 @@
       }
     },
     {
-      "id": "page-1177",
+      "id": "page-1176",
       "title": "Install private nodes",
       "url": "https://docs.n8n.io/integrations/creating-nodes/deploy/install-private-nodes/index.md",
       "urlPath": "integrations/creating-nodes/deploy/install-private-nodes/index.md",
@@ -85494,6 +85424,76 @@
         ]
       }
     },
+    {
+      "id": "page-1177",
+      "title": "Structure",
+      "url": "https://docs.n8n.io/integrations/creating-nodes/build/reference/node-base-files/structure/index.md",
+      "urlPath": "integrations/creating-nodes/build/reference/node-base-files/structure/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Structure of the node base file\n\nThe node base file follows this basic structure:\n\n1. Add import statements.\n1. Create a class for the node.\n1. Within the node class, create a `description` object, which defines the node.\n\nA programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. The declarative style handles this using the `routing` key in the `properties` object, within `descriptions`.\n\n## Outline structure for a declarative-style node\n\nThis code snippet gives an outline of the node structure.\n\n```\nimport { INodeType, INodeTypeDescription } from 'n8n-workflow';\n\nexport class ExampleNode implements INodeType {\n\tdescription: INodeTypeDescription = {\n\t\t// Basic node details here\n\t\tproperties: [\n\t\t\t// Resources and operations here\n\t\t]\n\t};\n}\n```\n\nRefer to [Standard parameters](../standard-parameters/) for information on parameters available to all node types. Refer to [Declarative-style parameters](../declarative-style-parameters/) for the parameters available for declarative-style nodes.\n\n## Outline structure for a programmatic-style node\n\nThis code snippet gives an outline of the node structure.\n\n```\nimport { IExecuteFunctions } from 'n8n-core';\nimport { INodeExecutionData, INodeType, INodeTypeDescription } from 'n8n-workflow';\n\nexport class ExampleNode implements INodeType {\n\tdescription: INodeTypeDescription = {\n    // Basic node details here\n    properties: [\n      // Resources and operations here\n    ]\n  };\n\n  async execute(this: IExecuteFunctions): Promise<INodeExecutionData[][]> {\n    // Process data and return\n  }\n};\n```\n\nRefer to [Standard parameters](../standard-parameters/) for information on parameters available to all node types. Refer to [Programmatic-style parameters](../programmatic-style-parameters/) and [Programmatic-style execute method](../programmatic-style-execute-method/) for more information on working with programmatic-style nodes.\n",
+        "excerpt": "# Structure of the node base file  The node base file follows this basic structure:  1. Add import statements. 1. Create a class for the node. 1. Within the node class, create a `description` object, which defines the node.  A programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. The declarative style handles this using the `routing` key in the `properties` object, within `descriptions`.  ## Outline structure for a declarative-st...",
+        "sections": [
+          {
+            "title": "Structure of the node base file",
+            "level": 1,
+            "content": "The node base file follows this basic structure:\n\n1. Add import statements.\n1. Create a class for the node.\n1. Within the node class, create a `description` object, which defines the node.\n\nA programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. The declarative style handles this using the `routing` key in the `properties` object, within `descriptions`."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "structure",
+          "node",
+          "base",
+          "file",
+          "outline",
+          "declarative",
+          "style",
+          "programmatic"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 2,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 1954,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "structure # structure of the node base file\n\nthe node base file follows this basic structure:\n\n1. add import statements.\n1. create a class for the node.\n1. within the node class, create a `description` object, which defines the node.\n\na programmatic-style node also has an `execute()` method, which reads incoming data and parameters, then builds a request. the declarative style handles this using the `routing` key in the `properties` object, within `descriptions`.\n\n## outline structure for a declarative-style node\n\nthis code snippet gives an outline of the node structure.\n\n```\nimport { inodetype, inodetypedescription } from 'n8n-workflow';\n\nexport class examplenode implements inodetype {\n\tdescription: inodetypedescription = {\n\t\t// basic node details here\n\t\tproperties: [\n\t\t\t// resources and operations here\n\t\t]\n\t};\n}\n```\n\nrefer to [standard parameters](../standard-parameters/) for information on parameters available to all node types. refer to [declarative-style parameters](../declarative-style-parameters/) for the parameters available for declarative-style nodes.\n\n## outline structure for a programmatic-style node\n\nthis code snippet gives an outline of the node structure.\n\n```\nimport { iexecutefunctions } from 'n8n-core';\nimport { inodeexecutiondata, inodetype, inodetypedescription } from 'n8n-workflow';\n\nexport class examplenode implements inodetype {\n\tdescription: inodetypedescription = {\n    // basic node details here\n    properties: [\n      // resources and operations here\n    ]\n  };\n\n  async execute(this: iexecutefunctions): promise<inodeexecutiondata[][]> {\n    // process data and return\n  }\n};\n```\n\nrefer to [standard parameters](../standard-parameters/) for information on parameters available to all node types. refer to [programmatic-style parameters](../programmatic-style-parameters/) and [programmatic-style execute method](../programmatic-style-execute-method/) for more information on working with programmatic-style nodes.\n structure of the node base file",
+        "importantTerms": [
+          "node",
+          "style",
+          "parameters",
+          "structure",
+          "programmatic",
+          "this",
+          "declarative",
+          "import",
+          "class",
+          "execute",
+          "outline",
+          "inodetype",
+          "inodetypedescription",
+          "here",
+          "refer",
+          "standard",
+          "base",
+          "file",
+          "basic",
+          "description",
+          "method",
+          "properties",
+          "from",
+          "information",
+          "available"
+        ]
+      }
+    },
     {
       "id": "page-1178",
       "title": "Submit community nodes",
@@ -92140,7 +92140,7 @@
         "page-0496",
         "page-0497",
         "page-0498",
-        "page-0499",
+        "page-0501",
         "page-0502",
         "page-0503",
         "page-0509",
@@ -92287,7 +92287,7 @@
         "page-0671",
         "page-0672",
         "page-0674",
-        "page-0677",
+        "page-0676",
         "page-0678",
         "page-0679",
         "page-0680",
@@ -92593,7 +92593,7 @@
         "page-0520",
         "page-0630",
         "page-0634",
-        "page-1177"
+        "page-1176"
       ],
       "permissions": [
         "page-0002",
@@ -92869,7 +92869,7 @@
         "page-1161",
         "page-1164",
         "page-1168",
-        "page-1177",
+        "page-1176",
         "page-1178",
         "page-1181",
         "page-1202",
@@ -93119,7 +93119,7 @@
         "page-0496",
         "page-0497",
         "page-0498",
-        "page-0502",
+        "page-0501",
         "page-0503",
         "page-0508",
         "page-0509",
@@ -93280,7 +93280,7 @@
         "page-0638",
         "page-0647",
         "page-0657",
-        "page-0676",
+        "page-0677",
         "page-0681",
         "page-0684",
         "page-0708",
@@ -93581,7 +93581,7 @@
         "page-0645",
         "page-0657",
         "page-0669",
-        "page-0676",
+        "page-0677",
         "page-0687",
         "page-0699",
         "page-0707",
@@ -93591,7 +93591,7 @@
         "page-1164",
         "page-1169",
         "page-1170",
-        "page-1175",
+        "page-1177",
         "page-1186"
       ],
       "enable": [
@@ -94246,7 +94246,7 @@
         "page-0503",
         "page-0504",
         "page-0534",
-        "page-0676",
+        "page-0677",
         "page-1027",
         "page-1160",
         "page-1163",
@@ -94494,15 +94494,15 @@
         "page-0482",
         "page-0483",
         "page-0484",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0490",
         "page-0491",
         "page-0493",
         "page-0494",
-        "page-0502",
+        "page-0501",
         "page-0508",
         "page-0514",
         "page-0519",
@@ -94524,7 +94524,7 @@
         "page-1155",
         "page-1156",
         "page-1157",
-        "page-1177",
+        "page-1176",
         "page-1178",
         "page-1180",
         "page-1182",
@@ -94692,7 +94692,7 @@
         "page-0005",
         "page-0219",
         "page-0497",
-        "page-0676",
+        "page-0677",
         "page-0679",
         "page-0684"
       ],
@@ -96576,7 +96576,7 @@
         "page-0636",
         "page-0754",
         "page-0900",
-        "page-1177",
+        "page-1176",
         "page-1188",
         "page-1196",
         "page-1203",
@@ -96657,7 +96657,7 @@
         "page-0013",
         "page-0061",
         "page-0197",
-        "page-0501",
+        "page-0500",
         "page-0505",
         "page-0507",
         "page-0511",
@@ -97226,13 +97226,13 @@
         "page-0482",
         "page-0483",
         "page-0484",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0502",
+        "page-0501",
         "page-0508",
         "page-0514",
         "page-0519",
@@ -97532,13 +97532,13 @@
         "page-0482",
         "page-0483",
         "page-0484",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0502",
+        "page-0501",
         "page-0508",
         "page-0514",
         "page-0519",
@@ -97691,7 +97691,7 @@
         "page-0489",
         "page-0495",
         "page-0496",
-        "page-0501",
+        "page-0500",
         "page-0505",
         "page-0506",
         "page-0507",
@@ -97936,13 +97936,13 @@
         "page-0469",
         "page-0470",
         "page-0478",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0499",
+        "page-0502",
         "page-0508",
         "page-0512",
         "page-0514",
@@ -98475,13 +98475,13 @@
         "page-0469",
         "page-0470",
         "page-0478",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0499",
+        "page-0502",
         "page-0508",
         "page-0512",
         "page-0514",
@@ -99228,7 +99228,7 @@
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0499",
+        "page-0501",
         "page-0502",
         "page-0508",
         "page-0512",
@@ -100009,7 +100009,7 @@
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0499",
+        "page-0501",
         "page-0502",
         "page-0508",
         "page-0512",
@@ -100208,7 +100208,7 @@
         "page-0325",
         "page-0326",
         "page-0331",
-        "page-0487",
+        "page-0486",
         "page-0499",
         "page-0500",
         "page-0501",
@@ -100699,7 +100699,7 @@
       ],
       "write": [
         "page-0024",
-        "page-0676",
+        "page-0677",
         "page-1159"
       ],
       "outputs": [
@@ -100779,7 +100779,7 @@
         "page-0496",
         "page-0497",
         "page-0498",
-        "page-0502",
+        "page-0501",
         "page-0503",
         "page-0508",
         "page-0509",
@@ -101163,7 +101163,7 @@
         "page-0671",
         "page-0672",
         "page-0674",
-        "page-0677",
+        "page-0676",
         "page-0678",
         "page-0679",
         "page-0680",
@@ -101363,7 +101363,7 @@
         "page-0496",
         "page-0497",
         "page-0498",
-        "page-0501",
+        "page-0500",
         "page-0505",
         "page-0506",
         "page-0507",
@@ -101697,13 +101697,13 @@
         "page-0482",
         "page-0483",
         "page-0484",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0502",
+        "page-0501",
         "page-0508",
         "page-0514",
         "page-0519",
@@ -102634,7 +102634,7 @@
       "global": [
         "page-0061",
         "page-0700",
-        "page-1177"
+        "page-1176"
       ],
       "static": [
         "page-0061"
@@ -103015,7 +103015,7 @@
         "page-1160",
         "page-1164",
         "page-1168",
-        "page-1175"
+        "page-1177"
       ],
       "sets": [
         "page-0086"
@@ -104484,7 +104484,7 @@
         "page-0496",
         "page-0497",
         "page-0498",
-        "page-0501",
+        "page-0500",
         "page-0507",
         "page-0532",
         "page-0546",
@@ -104909,7 +104909,7 @@
       ],
       "event": [
         "page-0153",
-        "page-0501",
+        "page-0500",
         "page-1140",
         "page-1142"
       ],
@@ -105131,7 +105131,7 @@
         "page-1040",
         "page-1157",
         "page-1170",
-        "page-1175"
+        "page-1177"
       ],
       "front": [
         "page-0160",
@@ -105413,7 +105413,7 @@
         "page-1150",
         "page-1151",
         "page-1155",
-        "page-1177"
+        "page-1176"
       ],
       "globally": [
         "page-0196",
@@ -105442,8 +105442,8 @@
         "page-0496",
         "page-0497",
         "page-0498",
+        "page-0499",
         "page-0500",
-        "page-0501",
         "page-0504",
         "page-0505",
         "page-0506",
@@ -105804,7 +105804,7 @@
       "deploy": [
         "page-0203",
         "page-0205",
-        "page-1176",
+        "page-1175",
         "page-1205",
         "page-1206"
       ],
@@ -106491,7 +106491,7 @@
         "page-0667",
         "page-0671",
         "page-0673",
-        "page-0676",
+        "page-0677",
         "page-0687",
         "page-0688",
         "page-0692",
@@ -106738,13 +106738,13 @@
         "page-0482",
         "page-0483",
         "page-0484",
+        "page-0485",
         "page-0486",
-        "page-0487",
         "page-0488",
         "page-0489",
         "page-0491",
         "page-0493",
-        "page-0502",
+        "page-0501",
         "page-0508",
         "page-0514",
         "page-0519",
@@ -107933,21 +107933,21 @@
         "page-0483",
         "page-1020"
       ],
-      "zulip": [
-        "page-0485",
-        "page-1023"
-      ],
       "anthropic": [
-        "page-0486",
+        "page-0485",
         "page-0583",
         "page-0729"
       ],
       "gemini": [
-        "page-0487",
+        "page-0486",
         "page-0575",
         "page-0588",
         "page-1203"
       ],
+      "zulip": [
+        "page-0487",
+        "page-1023"
+      ],
       "perplexity": [
         "page-0488",
         "page-0913"
@@ -108099,15 +108099,15 @@
       "calendar": [
         "page-0499",
         "page-0500",
-        "page-0501",
+        "page-0502",
         "page-1069"
       ],
       "availability": [
-        "page-0500",
+        "page-0499",
         "page-1203"
       ],
       "drive": [
-        "page-0502",
+        "page-0501",
         "page-0503",
         "page-0504",
         "page-0505",
@@ -108777,7 +108777,7 @@
       ],
       "keys": [
         "page-0556",
-        "page-0677",
+        "page-0676",
         "page-1167",
         "page-1182",
         "page-1203"
@@ -109365,7 +109365,7 @@
       "rename": [
         "page-0661",
         "page-0667",
-        "page-0677"
+        "page-0676"
       ],
       "commit": [
         "page-0662",
@@ -109479,16 +109479,16 @@
         "page-0675"
       ],
       "read/write": [
-        "page-0676"
+        "page-0677"
       ],
       "disk": [
-        "page-0676"
+        "page-0677"
       ],
       "file(s)": [
-        "page-0676"
+        "page-0677"
       ],
       "locations": [
-        "page-0676"
+        "page-0677"
       ],
       "secures": [
         "page-0678",
@@ -109889,7 +109889,7 @@
         "page-0843",
         "page-0963",
         "page-1006",
-        "page-1177"
+        "page-1176"
       ],
       "meta": [
         "page-0797",
@@ -110327,7 +110327,7 @@
       "declarative": [
         "page-1154",
         "page-1171",
-        "page-1175"
+        "page-1177"
       ],
       "style": [
         "page-1154",
@@ -110337,7 +110337,7 @@
         "page-1171",
         "page-1172",
         "page-1173",
-        "page-1175",
+        "page-1177",
         "page-1180",
         "page-1182"
       ],
@@ -110373,7 +110373,7 @@
         "page-1167",
         "page-1172",
         "page-1173",
-        "page-1175"
+        "page-1177"
       ],
       "define": [
         "page-1157"
@@ -110400,7 +110400,7 @@
       ],
       "outline": [
         "page-1160",
-        "page-1175"
+        "page-1177"
       ],
       "`name`": [
         "page-1160",
@@ -113308,7 +113308,7 @@
         "page-0484"
       ],
       "zulip": [
-        "page-0485"
+        "page-0487"
       ],
       "airtable": [
         "page-0489",
@@ -113329,10 +113329,10 @@
       "googlecalendar": [
         "page-0499",
         "page-0500",
-        "page-0501"
+        "page-0502"
       ],
       "googledrive": [
-        "page-0502",
+        "page-0501",
         "page-0503",
         "page-0504",
         "page-0505",
@@ -113484,10 +113484,10 @@
       "noop": [
         "page-0675"
       ],
-      "readwritefile": [
+      "renamekeys": [
         "page-0676"
       ],
-      "renamekeys": [
+      "readwritefile": [
         "page-0677"
       ],
       "respondtowebhook": [