{"_id":"@zenland-dev/n8n-nodes-bitrix24","_rev":"20-ffbcef0f2c411f04b5685e4b0b768adf","name":"@zenland-dev/n8n-nodes-bitrix24","dist-tags":{"latest":"0.11.0"},"versions":{"0.5.0":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.5.0","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","tasks","messenger","chat","open lines","contact center","chatbot","bot","drive","files"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.5.0","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"be6fb2c6fdd47bad092b9109186cdcf245434c5a","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.5.0.tgz","fileCount":268,"integrity":"sha512-g23D+5nRp9AxNJDljjjqkgbDCpuOWTeNViPPU6a2NioZXITAN6v6mskXmK8O59hifdyUFw/MtgUmKfTdKPLNhw==","signatures":[{"sig":"MEUCIQDG3+aB8H/bWWz6YGVko6o4CENH3TPUMLJDfU+v7HJkwQIgIkhuFCqJiyPpAvrFi5JvOvu8MLvGAK03/9L/5wdH2Z4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQC4bScrRqAGxC5TyGia1lE9uPUrzYmM0TCWt+lLaHa4ugIhANmHaKglNNXjATFC86fhmgwUVE+jckyPolZoxIZyZHBY","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.5.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1433763},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"fae7e1a2354eced78276c1750aedcbe133ed7a55","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, tasks and workgroups, messenger and open lines, chatbots, Drive files and folders, any REST method, batches, a webhook trigger and polling triggers for chats and bots","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.5.0_1789538244272_0.7553176745491272","host":"s3://npm-registry-packages-npm-production"}},"0.6.0":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.6.0","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","tasks","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.6.0","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"72238af36afcc003775f898a6b6b40a0ab01f044","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.6.0.tgz","fileCount":293,"integrity":"sha512-AX2QkrEht8ADg7J12SPdphze3AQSRrQ0F2M3WxvzR/0UCX70w/EzTk8UYTl9T8gVKHtOyV6HzLLLge4oHbogeg==","signatures":[{"sig":"MEUCIQDYexem8vrwx9VgKCPZ49+D3wbv6sxK6c/plJ5gS2lmEAIgSsl6gGTD89W++YA+I3Yp/7hYh8LZymdopD/vAy/2uWM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCNWRc3ipHk7VrCUimtf+qYiok1SsGnkvyFX9kV1aCMuQIgOehfA90tEBqckUrgE6AXdXDbMQcZOLiO/8Jfs4bOkM4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.6.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1567702},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"9f36b9d8baeef663172022c1ccf08b219b521565","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, tasks and workgroups, calendar and resource booking, messenger and open lines, chatbots, Drive files and folders, any REST method, batches, a webhook trigger and polling triggers for chats and bots","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.6.0_1789549081213_0.5016301494579452","host":"s3://npm-registry-packages-npm-production"}},"0.7.0":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.7.0","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","tasks","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.7.0","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"f12d2757a06823873139b315ff234bcdf118207e","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.7.0.tgz","fileCount":321,"integrity":"sha512-IUjPAowcA027TTAhU1c2mJ4kpVfCrvhvxCm1SBx9uvGMFAmx0dUMKvp04uSMDIAh3FR23/J3T6VbU4QWcmHPNg==","signatures":[{"sig":"MEUCIEEM2dR3OB8P7iYcGLpOq4Z2MlL8CGwtKfxpQGULbNUkAiEA0dynyya2YwZrn8N6eA/jItBEetarVEB56Vk3CIGsm2c=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCFEqP5HC2tEYPwBT8n2ZMMPlaoJExVW70rFHFcAUYecQIhAJNYlgdXj9xJxAXc6F7onghyIpgBgQEwpzIi972oJsIB","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.7.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1695787},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"540ea9d13b55db851bed464f580a42ca1a142a5d","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, tasks and workgroups, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive files and folders, any REST method, batches, a webhook trigger and polling triggers for chats and ","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.7.0_1789575811598_0.7720374311313503","host":"s3://npm-registry-packages-npm-production"}},"0.8.2":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.8.2","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.8.2","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"585551aa6a2fa23c03cadf6ec1cdad7e8c91232a","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.8.2.tgz","fileCount":359,"integrity":"sha512-VFZg239+RjFzODmr/21GV90dHp9Y2zcLLliNsRTDgghRjW50j84w3pkkP/tQiT3LRgS08sWI28KohLvtG/cVDA==","signatures":[{"sig":"MEYCIQD7Sd8Qwz91A5xpSqkgDrxpUpOuTIF5qhkc1FwZsgDysAIhAJbErvKCREnnxbMDzmCKKGs2lkHAJ3z/aw+nbiUOFqUN","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDmHuUSicS84f0cuHPTAC44QGg805vGFqUcZG3akdqJXgIhAIwzgoBxcWw+ONWk47cGay6atsYDoXM8qxnyFxm+AqBA","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.8.2","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1863400},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"efd19413c8208b1294551b974b4546dadfda8fbe","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive files and folders, any REST method, batches, a webhook trigge","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.8.2_1789722346812_0.4750370931850658","host":"s3://npm-registry-packages-npm-production"}},"0.8.3":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.8.3","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.8.3","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"542ad63458bf3450c6744da16a53a2125f5b8574","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.8.3.tgz","fileCount":359,"integrity":"sha512-gPlILF3y8zkb4satArq2yYX5Scu3ans1mKZ+9z8aNxA3b8P21CnZguC3sn+Gw5y6hahD7jT9Qb2WN4eyM4WPsA==","signatures":[{"sig":"MEQCIEpMXs34+UJxNWzEuRwAtvZMmGaCyGuFIC2DAoVGUYF3AiARpheSXCTEVf4H1LWJSxnuAZb9olrsWfY5i5NF/4akOQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCLg8UDxNwb5erQ6SnNEj9RXZ1nwVsUPQ9sSj5B3eO3OgIhAP4CC73FRoi3FxqO12xhhwpd3yxO0ZpMIp8ZMyY68ZM5","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.8.3","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":1864695},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"979ff8c349de3cf2b055a7f313f8c7046c7bb428","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive files and folders, any REST method, batches, a webhook trigge","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.8.3_1789806123653_0.8723947276536179","host":"s3://npm-registry-packages-npm-production"}},"0.9.0":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.9.0","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","catalog","products","prices","inventory","warehouse","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.9.0","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Catalog/Bitrix24Catalog.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"473d9f61a65447259e48c393efcdddc796831219","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.9.0.tgz","fileCount":390,"integrity":"sha512-aXIaZTzB0lbodvgLEzSicUuZhDN0Q3UlR7nmWV4K95WxW0cL++hE0lbVuph9LvK02Oz2qFMvW4lSqMu/5DnafQ==","signatures":[{"sig":"MEQCIC87FDAldomAesK5w7rCgeGf5HFnBFMdRJZ2b5fe8GSgAiBX7l1skXXiNlsXCKpYi8ivNJErE+2pDieiGQKjb6Gt0g==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQC//VYBOQrwsOPOPU5FcuS6tlQOyXKAMz1L1FrZbAzEwQIgI6Ctb1t551epIWzAe9QyBDxW1kHlH2llBA2yhd0684I=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.9.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2055878},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"aa820b2177b6fdd15f10d488b143bd8333035c97","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, product catalog with prices, stock and inventory documents, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive f","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.9.0_1789812538093_0.6019477130147253","host":"s3://npm-registry-packages-npm-production"}},"0.10.0":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.10.0","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","catalog","products","prices","inventory","warehouse","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking","event log","audit","consent","agreement","ai"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.10.0","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Ai/Bitrix24Ai.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Catalog/Bitrix24Catalog.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Consents/Bitrix24Consents.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24EventLog/Bitrix24EventLog.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"110c75e21467e4f5ea92c1b7e1d6a2bc889d28af","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.10.0.tgz","fileCount":420,"integrity":"sha512-63oqUdBmdc+q0+TDhrilLOwj+yaL5Co7wcX6PXswt0TjJ0Q81qnkRTdM3EacIw6GSrc0eXmlykxuYEHcWj5miQ==","signatures":[{"sig":"MEUCIBGKzqTpYy4JnLskOUMQt5Szi/jtzAdhOu9yYHXmWB98AiEA4VizBHgoD28jjeYe441fhHArR48fFrgPXplzNBiTeG8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCChhfx5TtM0gBZr0unea9pUDRSS0YWwUkpKhYhOcC/YgIhALYSTk8WmsOpFAHruq6lCDbFxxJVClvQPqw1M526hw7E","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.10.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2141802},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"102c0dcbb9af54e065d20a20639220b9fc0fd42b","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, product catalog with prices, stock and inventory documents, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive f","directories":{},"_nodeVersion":"24.21.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.10.0_1790163987039_0.2190473762748657","host":"s3://npm-registry-packages-npm-production"}},"0.10.1":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.10.1","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","catalog","products","prices","inventory","warehouse","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking","event log","audit","consent","agreement","ai"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.10.1","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Ai/Bitrix24Ai.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Catalog/Bitrix24Catalog.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Consents/Bitrix24Consents.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24EventLog/Bitrix24EventLog.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"2aa15c608aa0151f83ee7ef93924ffe844e5fb9d","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.10.1.tgz","fileCount":423,"integrity":"sha512-DsHGcqTeHfUUJ5D2ixI1E1E/0xtzj/G9UoSh2NoFmbD1jr4Ea4KEB/ObEmxVfSrPvak1Myjwupta2Wq2kwPYdQ==","signatures":[{"sig":"MEQCICcfjkd2wM2JxW49/LZrOOy8VwwdbTwHDEk19u1DpRLHAiBYxxDyYjdIgJN62g5N6YzcxLwxBrg3sxQpycdNVkdX+g==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDNwvM+Q4OtGTG8f3yyZ3waxyuuUrNJRAg9yScsTq6/PAIgLfNwT05bAECgV8OAgltT2VDiSpB2e+IMLyhEr8y2Hqo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.10.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2144724},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"b12e0cabb07ee82e1c43b5a444c56a970009191a","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, product catalog with prices, stock and inventory documents, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive f","directories":{},"_nodeVersion":"24.20.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.10.1_1790165539868_0.34851387798270994","host":"s3://npm-registry-packages-npm-production"}},"0.10.2":{"name":"@zenland-dev/n8n-nodes-bitrix24","version":"0.10.2","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","catalog","products","prices","inventory","warehouse","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking","event log","audit","consent","agreement","ai"],"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","_id":"@zenland-dev/n8n-nodes-bitrix24@0.10.2","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Ai/Bitrix24Ai.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Catalog/Bitrix24Catalog.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Consents/Bitrix24Consents.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24EventLog/Bitrix24EventLog.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"dist":{"shasum":"cc2d8bdcb3500331c48f7fc64451ebe8893ddf50","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.10.2.tgz","fileCount":423,"integrity":"sha512-EhK1Bv00CV7hQ/pKVAq4jNBSr9Y7M23ac+CgXX1e0PLZzkjWOr5wuqA08cem/odzavNU9Pb7bkiyTqAzMk6kMA==","signatures":[{"sig":"MEUCIGKy7IMcBgu7GMIfWiBiBen8OlKuferM/fgQ8exlEGecAiEA4aochpaopA4u3ZmKnnOq6Qjy4wgJSKpEdpDwnB7f6W8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIAYfnl87CWsKvEyd9aGDnXmKB186M089J6Wm3nUaZmP/AiB9paad9LgX6R5S08Jv7u2kqUhLEX+XCazZ7aYBEVq74w==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.10.2","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2145865},"main":"index.js","engines":{"node":">=20.19"},"gitHead":"86cd43df692680b21df7e5a46812d04631f038e2","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, product catalog with prices, stock and inventory documents, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive f","directories":{},"_nodeVersion":"24.21.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"tmp":"tmp/n8n-nodes-bitrix24_0.10.2_1790233565645_0.7123488649318308","host":"s3://npm-registry-packages-npm-production"}},"0.11.0":{"_id":"@zenland-dev/n8n-nodes-bitrix24@0.11.0","n8n":{"nodes":["dist/nodes/Bitrix24/Bitrix24.node.js","dist/nodes/Bitrix24Ai/Bitrix24Ai.node.js","dist/nodes/Bitrix24BizProc/Bitrix24BizProc.node.js","dist/nodes/Bitrix24Calendar/Bitrix24Calendar.node.js","dist/nodes/Bitrix24Catalog/Bitrix24Catalog.node.js","dist/nodes/Bitrix24Chatbot/Bitrix24Chatbot.node.js","dist/nodes/Bitrix24ChatbotTrigger/Bitrix24ChatbotTrigger.node.js","dist/nodes/Bitrix24Consents/Bitrix24Consents.node.js","dist/nodes/Bitrix24Crm/Bitrix24Crm.node.js","dist/nodes/Bitrix24Drive/Bitrix24Drive.node.js","dist/nodes/Bitrix24Employees/Bitrix24Employees.node.js","dist/nodes/Bitrix24EventLog/Bitrix24EventLog.node.js","dist/nodes/Bitrix24Lists/Bitrix24Lists.node.js","dist/nodes/Bitrix24Messenger/Bitrix24Messenger.node.js","dist/nodes/Bitrix24MessengerTrigger/Bitrix24MessengerTrigger.node.js","dist/nodes/Bitrix24OpenLines/Bitrix24OpenLines.node.js","dist/nodes/Bitrix24Tasks/Bitrix24Tasks.node.js","dist/nodes/Bitrix24Trigger/Bitrix24Trigger.node.js"],"strict":true,"credentials":["dist/credentials/Bitrix24ChatbotWebhookApi.credentials.js","dist/credentials/Bitrix24WebhookApi.credentials.js"],"n8nNodesApiVersion":1},"bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"dist":{"shasum":"a7a2a634f9f754df73236ec5e3f8756f99cc7176","tarball":"https://registry.npmjs.org/@zenland-dev/n8n-nodes-bitrix24/-/n8n-nodes-bitrix24-0.11.0.tgz","fileCount":423,"integrity":"sha512-vMKPE/xBaJa0bvnkH5P6keeV8Zzasm3Y1bOb7j2BFxwtA1JPZuH71gOau82UJPbzJQKq2r2o5nCQJ1PW1mEyCg==","signatures":[{"sig":"MEUCIQCP5mlk6CU4ad8JSHeBtTcIfjja+z3M/H7ATXpdgdwbbQIgWoCgzf6QkK7bO0UXpxDlRpylDRSzXtRIuG8SRRDVc7A=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQC6+bWfQih9mta1jZpgoiISXVSjFMGQqaDiUi+wfOj/ngIhAOS238dBJYxpYtm2fO45B1bFCKPReQk6eAkiCas7hKKg"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@zenland-dev%2fn8n-nodes-bitrix24@0.11.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":2153667},"main":"index.js","name":"@zenland-dev/n8n-nodes-bitrix24","author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"engines":{"node":">=20.19"},"gitHead":"531ca80474f6df6926bd6434b03c24686258e977","license":"MIT","scripts":{"dev":"n8n-node dev","lint":"n8n-node lint","build":"n8n-node build","format":"prettier nodes credentials shared --write","release":"n8n-node release","lint:fix":"n8n-node lint --fix","prepublishOnly":"n8n-node prerelease"},"version":"0.11.0","_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:3e8c737c-5d25-434e-b832-8ad566063048"}},"homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","catalog","products","prices","inventory","warehouse","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking","event log","audit","consent","agreement","ai"],"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"_npmVersion":"11.19.0","description":"Bitrix24 nodes for n8n: CRM, product catalog with prices, stock and inventory documents, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive f","directories":{},"maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"_nodeVersion":"24.21.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"eslint":"9.39.4","prettier":"3.8.3","release-it":"^19.0.4","typescript":"5.9.3","@n8n/node-cli":"^0.46.4"},"peerDependencies":{"n8n-workflow":"*"},"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/n8n-nodes-bitrix24_0.11.0_1790444579865_0.09483236889879354"}}},"time":{"created":"2026-09-14T14:24:30.646Z","modified":"2026-09-26T17:43:00.336Z","0.1.0":"2026-09-14T14:24:30.979Z","0.2.0":"2026-09-14T19:07:01.467Z","0.3.0":"2026-09-14T20:38:33.324Z","0.4.0":"2026-09-15T18:04:33.763Z","0.4.1":"2026-09-15T18:41:07.488Z","0.5.0":"2026-09-16T05:57:24.366Z","0.6.0":"2026-09-16T08:58:01.294Z","0.7.0":"2026-09-16T16:23:31.749Z","0.8.2":"2026-09-18T09:05:46.899Z","0.8.3":"2026-09-19T08:22:03.738Z","0.9.0":"2026-09-19T10:08:58.210Z","0.10.0":"2026-09-23T11:46:27.257Z","0.10.1":"2026-09-23T12:12:20.068Z","0.10.2":"2026-09-24T07:06:05.768Z","0.11.0":"2026-09-26T17:42:59.973Z"},"bugs":{"url":"https://github.com/zenland-dev/n8n-nodes-bitrix24/issues"},"author":{"name":"zenland-dev","email":"zenland.dev@gmail.com"},"license":"MIT","homepage":"https://github.com/zenland-dev/n8n-nodes-bitrix24","keywords":["n8n-community-node-package","n8n","bitrix24","bitrix","crm","catalog","products","prices","inventory","warehouse","tasks","business process","workflow","lists","calendar","events","booking","messenger","chat","open lines","contact center","chatbot","bot","drive","files","employees","hr","time tracking","event log","audit","consent","agreement","ai"],"repository":{"url":"git+https://github.com/zenland-dev/n8n-nodes-bitrix24.git","type":"git"},"description":"Bitrix24 nodes for n8n: CRM, product catalog with prices, stock and inventory documents, tasks and workgroups, business processes, universal lists, calendar and resource booking, employees and company structure, messenger and open lines, chatbots, Drive f","maintainers":[{"name":"zenland-dev","email":"zenland.dev@gmail.com"}],"readme":"# @zenland-dev/n8n-nodes-bitrix24\n\nn8n community nodes for [Bitrix24](https://www.bitrix24.com): a CRM node with 268 operations\nacross 42 resources, a catalog node with 148 operations across 26 resources, a tasks node with 129\noperations across 17 resources, a messenger node with 63 operations, an open lines node with 43, a Drive node with 36, a chatbot node with 34, an\nemployees node with 32, a calendar node with 21, a lists node with 19, a business process node with\n10, an event log node with 5, a consents node with 3 and an AI node with 3, a node that calls any of\nthe ~1400 REST methods by name or in batches, a trigger for outgoing\nwebhooks, and two triggers that need no public URL: one for chat messages, one for messages and\ncommands sent to a bot.\n\nWritten from scratch against the official REST documentation\n([bitrix24/b24restdocs](https://github.com/bitrix24/b24restdocs), read on 14.09.2026). No code\nfrom any other package.\n\n**Status: 0.10.2.** Every operation of the CRM, tasks, Drive, chatbot, calendar, lists and event log\nnodes was run against a live Bitrix24 portal, 143 of the 148 of the catalog node, 29 of the 32 of the\nemployees node, 57 of the 63 of the messenger node, 14 of the 43 of the open lines node, 7 of the 10 of the business process node, 2 of the 3 of the consents node and\n1 of the 3 of the AI node: reads as they are, writes on objects the test created and deleted. What was\nnot run, and why, is under [What was checked](#what-was-checked). Operations that work with a\nlimitation of Bitrix24 itself are listed under [Quirks](#quirks-worth-knowing).\n\n- [Installation](#installation)\n- [Credentials](#credentials)\n- [Bitrix24 node](#bitrix24-node)\n- [Bitrix24 CRM](#bitrix24-crm)\n- [Bitrix24 Tasks](#bitrix24-tasks)\n- [Bitrix24 Messenger](#bitrix24-messenger)\n- [Bitrix24 Open Lines](#bitrix24-open-lines)\n- [Bitrix24 Chatbot](#bitrix24-chatbot)\n- [Bitrix24 Drive](#bitrix24-drive)\n- [Bitrix24 Calendar](#bitrix24-calendar)\n- [Bitrix24 Employees](#bitrix24-employees)\n- [Bitrix24 Business Processes](#bitrix24-business-processes)\n- [Bitrix24 Lists](#bitrix24-lists)\n- [Bitrix24 Catalog](#bitrix24-catalog)\n- [Bitrix24 Event Log](#bitrix24-event-log)\n- [Bitrix24 Consents](#bitrix24-consents)\n- [Bitrix24 AI](#bitrix24-ai)\n- [Bitrix24 Trigger](#bitrix24-trigger)\n- [Bitrix24 Messenger Trigger](#bitrix24-messenger-trigger)\n- [Bitrix24 Chatbot Trigger](#bitrix24-chatbot-trigger)\n- [Rate limits](#rate-limits)\n- [Quirks worth knowing](#quirks-worth-knowing)\n- [What was checked](#what-was-checked)\n- [What is not here yet](#what-is-not-here-yet)\n\n## Installation\n\nIn n8n: **Settings → Community nodes → Install**, then enter `@zenland-dev/n8n-nodes-bitrix24`.\n\nSelf-hosted, from the command line:\n\n```bash\nnpm install @zenland-dev/n8n-nodes-bitrix24\n```\n\nRequires n8n 2.x and Node 20.19 or newer.\n\n## Credentials\n\nNine of the eleven nodes use **Bitrix24 Webhook API**, built from an inbound webhook. The chatbot\nnode and its trigger use **Bitrix24 Chatbot Webhook API**: the same fields plus a bot token, see\n[below](#bitrix24-chatbot-webhook-api).\n\nCreate the webhook in Bitrix24 under **Developer resources → Other → Inbound webhook** and tick\nthe permissions the workflows need: `crm` for the CRM node; `task`, `tasks` and `sonet_group`\nfor the tasks node; `im` for the messenger node and its trigger; `imopenlines` for the open lines\nnode, plus `crm` for its CRM chats; `disk` for the Drive node; `bizproc` for the business process\nnode and `lists` for the lists node; plus whatever modules you call through the Bitrix24 node. The webhook acts as the user who created it and sees only what that\nuser may see, so a webhook made by a sales manager cannot read another manager's deals.\n\nThe credential has three fields instead of one URL.\n\n**Portal Subdomain** and **Portal Domain.** `mycompany` and `bitrix24.com` for\n`mycompany.bitrix24.com`. The domain is a closed list of the 23 zones Bitrix24 serves cloud\nportals on (`.com`, `.eu`, `.de`, `.ru`, `.kz`, `.com.br` and so on). A webhook URL carries\nits secret in the path, so a free-form address would let anyone who can edit the credential\nsend that secret to their own server. The list is enforced again inside the nodes, not only in\nthe dropdown. Self-hosted Bitrix24 on its own domain is not supported for the same reason.\n\nThe zones were found by resolving a random subdomain in each candidate: Bitrix24 zones answer\nwith wildcard DNS, `.ua`, `.am`, `.az`, `.ge` and `.kg` do not resolve, and `.cz` and `.au`\nresolve to parking pages that have nothing to do with Bitrix24.\n\n**Webhook Token.** The part of the webhook URL after `/rest/`, like `1/abcdef0123456789`.\nPasting the whole URL works: only the tail is kept, and the host in it is ignored.\n\n**Requests per Second** defaults to 2, the limit on every plan below Enterprise.\n\nThe credential is pinned out of the HTTP Request node (`Allowed HTTP Request Domains` is fixed\nto none), and it has no `authenticate` block, so even a credential selected there would add\nnothing to a request.\n\n### Bitrix24 Chatbot Webhook API\n\nThrough a webhook, Bitrix24 tells bots apart by `botToken`: a string you make up when the bot is\nregistered and send with every later call. Whoever has the webhook and the token can act as the\nbot, so the token is a secret, and it lives in the credential rather than in a node parameter,\nwhere it would travel inside every exported workflow.\n\n- The webhook needs the `imbot` permission, plus `im` if a bot should also read the webhook user's\n own events.\n- **Bot Token**: up to 40 characters; the documentation announces that registration refuses longer\n ones from 06.08.2026, and the node refuses them already. 32 random letters and digits from a\n password generator do.\n- Keep the token once a bot is registered with it. Another token cannot reach that bot, and the\n node does not offer rotating it: the new token would have to be typed into a workflow.\n- One token can hold several bots. Every operation picks the bot from a list of the token's bots.\n\n**Test** calls `imbot.v2.Revision.get`, which checks the portal, the webhook and its `imbot`\npermission. It cannot check the token: before a bot is registered with it, any token is as good\nas another.\n\n## Bitrix24 node\n\nThe escape hatch. Anything the CRM node lacks, and every module that has no node yet, is one\ncall away here.\n\n| Resource | Operations |\n|---|---|\n| **Method** | Call |\n| **Batch** | Execute Commands, Call for Each Item |\n| **Portal** | Get Permissions, Get Methods, Check Method, Get Current User, Get Server Time, Get Access Names |\n\n**Call** takes a method name and a JSON body, for example `crm.item.list` with\n`{\"entityTypeId\": 2, \"select\": [\"title\", \"stageId\"]}`. Pagination has three modes. *First\nPage Only* sends one request. *Follow Pages* repeats with `start` until Bitrix24 stops\nsending `next`. *Page by ID* filters by the last ID received with `start: -1`, which tells\nBitrix24 not to count the total; on a large portal the count is what makes a page slow.\n\n**API Version** switches to REST 3.0 (`/rest/api/`). Some newer methods exist only there:\n`main.eventlog.*`, `mail.mailbox.*`, `note.*`, `humanresources.*`, `timeman.record.*`.\n\n**Execute Commands** sends up to 50 named calls in one request, and a later command can use an\nearlier result: `{\"id\": \"$result[list][items][0][id]\"}`. Such references only work inside one\nrequest, which is why the node refuses a 51st command instead of splitting the list.\n\n**Call for Each Item** is for bulk work. It makes the same kind of call once per input item and\npacks them 50 to a request, so 500 new leads cost 10 requests instead of 500. Output items stay\npaired with their inputs. With Continue On Fail on, a failed call becomes an error item and the\nrest go through; with it off, the node stops, but every call of that run has already been sent.\n\n## Bitrix24 CRM\n\nBuilt on the universal `crm.item.*` API, so field names are camelCase (`title`, `stageId`,\n`assignedById`) and custom fields are `ufCrm…`. The older per-entity methods (`crm.deal.add`\nand friends) are frozen by Bitrix24 and are not wrapped; call them through the Bitrix24 node if\nan old integration needs their exact behaviour.\n\n| Resource | Operations |\n|---|---|\n| **Lead, Deal, Contact, Company, Quote, Invoice** | Create, Get, Get Many, Update, Delete, Get Fields, Import, Merge |\n| **Smart Process Item** | the same, for any smart process picked from a list |\n| **Product Row** | Add, Get, Get Many, Update, Replace All, Delete, Get Fields, Get Available for Payment |\n| **Activity** | Create To-Do, Update To-Do, Set Deadline, Set Description, Set Responsible, Set Color, Complete, Get, Get Many, Delete, Get Fields, Get Call Transcript, Link to Record, Unlink From Record, Get Links, Move |\n| **Timeline Comment** | Create, Get, Get Many, Update, Delete |\n| **Timeline Note** | Save, Get, Delete |\n| **Timeline Log Entry** | Create, Get, Get Many, Delete |\n| **Timeline Entry** | Link to Record, Unlink From Record, Get Links, Pin, Unpin |\n| **Linked Contact** | Add, Remove, Get Many, Replace All, Remove All (on leads, deals, quotes, companies) |\n| **Linked Company** | the same, on contacts |\n| **Duplicate** | Find by Phone or Email, Get Extra Search Fields, Get Addable Search Fields, Add Search Field, Remove Search Field |\n| **Pipeline** | Create, Get, Get Many, Update, Delete, Get Fields |\n| **Reference Book** | Create, Get, Get Many, Update, Delete, Get Fields, Get Reference Books, Get Book Entries |\n| **Smart Process Type** | Create, Get, Get Many, Update, Delete, Get Fields, Get by Entity Type ID |\n| **Custom Field** | Create, Get, Get Many, Update, Delete (leads, deals, contacts, companies, quotes, requisites) |\n| **Custom Field Config** | Create, Get, Get Many, Update, Delete, Get Field Types (any CRM type, smart processes included) |\n| **Requisite, Bank Detail** | Create, Get, Get Many, Update, Delete, Get Fields |\n| **Address** | Create, Get Many, Update, Delete, Get Fields |\n| **Requisite Link** | Get, Get Many, Set, Remove, Get Fields |\n| **Requisite Template, Requisite Template Field** | Create, Get, Get Many, Update, Delete, Get Fields (+ Get Available to Add) |\n| **Document** | Generate, Get, Get Many, Update, Delete, Set Public Link, Get Placeholders, Upload |\n| **Document Template, Document Numerator** | Create, Get, Get Many, Update, Delete |\n| **Payment** | Create, Get, Get Many, Update, Delete, Mark as Paid, Mark as Unpaid, Get Payment Link, and products and deliveries inside a payment |\n| **Delivery** | Get, Get Many |\n| **Recurring Deal** | Create, Get, Get Many, Update, Delete, Get Fields, Create Deal Now |\n| **Order Link** | Create, Delete, Get Many, Get Fields |\n| **Call List** | Create, Get, Get Many, Update, Get Entries, Get Statuses |\n| **Stage History** | Get Many |\n| **Automation Trigger** | Fire |\n| **Sales Intelligence Trace** | Create, Delete |\n| **Currency** | Create, Get, Get Many, Update, Delete, Get Fields, Get or Set Base Currency, Get, Set or Delete Localizations |\n| **Digital Workplace** | Create, Get, Get Many, Update, Delete, Get Fields |\n| **Card Layout** | Get, Set, Reset, Force Common for All |\n| **Dictionary** | eleven read-only lists: entity types, address types, CRM mode, custom field types and their settings |\n\n### Fields come from the portal\n\nCreate, Update and Import show a field mapper filled from `crm.item.fields`. Custom fields are\nin it with their labels, list fields become dropdowns with the portal's own values, and stage\nIDs come with the pipeline in front (` / `). A deal can have hundreds of\nfields, so the mapper adds nothing by default: pick the fields you need. Nothing is required on Update. Read-only fields are left out, and so are\n`contacts` and `companies`: `crm.item.fields` lists them as writable, under the same titles as\n`contactIds` and `companyIds`, but writing them fails with error 100.\n\nAnything the mapper cannot express goes into **Fields (JSON)**, which is merged last and wins.\nClearing a field is done there too: the mapper skips empty inputs rather than sending blanks.\n\nLeads, contacts and companies have a separate **Phones, Emails and Messengers** list. On Update\nit only adds. `crm.item.update` ignores the ID of an existing value in `fm`, and an empty value\nremoves nothing, so a phone cannot be changed or deleted through this node. The older\nper-entity methods can, through **Bitrix24 → Method → Call**: `crm.contact.update` (or\n`crm.lead.update`, `crm.company.update`) with\n\n```json\n{\"id\": 12, \"fields\": {\"PHONE\": [{\"ID\": 34, \"VALUE\": \"+49 30 1234567\"}]}}\n```\n\nand `\"DELETE\": \"Y\"` in place of `VALUE` to remove one. The value IDs are in `fm` of **Get**, and\nof **Get Many** when **Fields to Return** is empty or `*`; with a list of fields Bitrix24 leaves\n`fm` out.\n\n### Create runs automation, Import does not\n\n**Create** behaves like a person pressing Save: automation rules, workflows, notifications to\nthe responsible user. **Import** (`crm.item.import`) creates the record without automation\nrules and workflows. Use it for tests on a portal where a new deal would send a client an SMS.\n\nImport takes phones, emails and messengers too, but not in `fm`: `crm.item.import` answers\n`The value of an argument 'value' must be of type Bitrix\\Crm\\Multifield\\Collection` to the form\nevery other `crm.item` method uses. The node sends them as `PHONE`, `EMAIL`, `WEB` and `IM`\nlists instead, including `fm` written into Fields (JSON). Before 0.4.1 an Import with contact\ndetails failed.\n\nThe documentation also promises that Import keeps historical `createdTime`. In practice it\ndoes not: any `createdTime` older than records the portal already has, even by an hour, is\nrefused with `The value of \"Date created\" cannot be less than that of any other items`\n(`CRM_FIELD_ERROR_VALUE_NOT_VALID`). Migrating old data with its dates needs a portal that is\nstill empty.\n\n### Get Many reads by ID\n\nGet Many sorts by ID and asks for the next 50 above the last one, with no total count. Set\n**Order (JSON)** and it falls back to Bitrix24's offset paging, which counts the total on\nevery page and gets slower as the portal grows.\n\nBefore creating a client, **Duplicate → Find by Phone or Email** answers `found`, plus lead,\ncontact and company IDs. Bitrix24 itself returns `[]` for no match and an object for a match;\nthe node smooths that into one shape.\n\n## Bitrix24 Tasks\n\nTasks, and everything a task lives in: checklists, time, results, dependencies, kanban\nstages, templates, flows, workgroups and scrum. The webhook needs the `task` permission, plus\n`sonet_group` for workgroups and `tasks` for the operations marked REST 3.0 below.\n\n| Resource | Operations |\n|---|---|\n| **Task** | Create, Get, Get Many, Update, Delete, Get Fields, Start, Pause, Defer, Complete, Reopen, Approve, Return for Rework, Delegate, Start Watching, Stop Watching, Add to Favorites, Remove From Favorites, Pin, Unpin, Mute, Unmute, Add Comment, Get History, Get Counters, Check Access, Attach File, Get Daily Plan |\n| **Checklist Item** | Create, Get, Get Many, Update, Delete, Complete, Reopen, Move After |\n| **Time Entry** | Create, Get, Get Many, Update, Delete |\n| **Result** | Create, Create From Chat Message, Get Many, Update, Delete |\n| **Dependency** | Create, Delete, Get Many |\n| **Kanban Stage** | Create, Get Many, Update, Delete, Move Task, Check Move Permission (group kanbans and My Plan) |\n| **Custom Field** | Create, Get, Get Many, Update, Delete, Get Types, Get Fields |\n| **Task Template** | Create, Get, Update, Delete, Get Fields |\n| **Template Checklist Item** | Create, Get, Get Many, Update, Delete, Complete, Reopen, Move After, Move Before, Attach Drive Files, Remove Attachments |\n| **Flow** | Create, Get, Update, Delete, Activate, Deactivate, Toggle Pin, Check Name |\n| **Workgroup** | Create, Get, Get Many, Get My Groups, Update, Delete, Set Owner, Check Feature Access |\n| **Workgroup Member** | Add, Invite, Request to Join, Get Many, Set Role, Remove |\n| **Scrum Sprint** | Create, Get, Get Many, Update, Delete, Start, Complete Active Sprint, Get Fields |\n| **Scrum Epic, Scrum Backlog** | Create, Get, (Get Many), Update, Delete, Get Fields |\n| **Scrum Kanban Stage** | Create, Get Many, Update, Delete, Add Task, Remove Task, Get Fields |\n| **Scrum Task** | Get, Update, Get Fields |\n\n### Two APIs under one node\n\nBitrix24 is moving tasks to REST 3.0, and on a cloud portal in September 2026 both answer. The\nnode uses the classic `tasks.task.*` for almost everything, because REST 3.0 cannot yet filter a\ntask list by anything but ID. REST 3.0 is used where the classic API has nothing: **Add\nComment**, **Result → Create / Update / Delete / Create From Chat Message** and\n**Dependency → Get Many**.\n\nFields are written in UPPER_CASE and come back in camelCase: `RESPONSIBLE_ID` goes in,\n`responsibleId` comes out. That is Bitrix24, not the node.\n\n### Comments are chat messages now\n\nSince the new task card (module `tasks` 25.700), a task's discussion is a chat. **Add Comment**\nposts into it. The old comment methods (`task.commentitem.*`) no longer read, change or delete\nanything on such portals, so the node does not wrap them. The chat is read with **Bitrix24\nMessenger → Message → Get Many** and the Dialog ID `chat`; `chatId` is in every task.\n\nThe comment events of the **Bitrix24 Trigger** changed with it. According to the documentation,\nTask Comment Updated and Task Comment Deleted are not sent for such tasks, and Task Comment Added\ncomes with `ID` 0 and the message ID in `MESSAGE_ID`. A real delivery was not tried.\n\n### Statuses\n\n`status` is a number: 2 pending, 3 in progress, 4 awaiting control, 5 completed, 6 deferred,\n7 declined. Change it with the operations, not by writing `STATUS`: they run the checks a\nperson pressing the button would. A task with **Require Result** does not complete until\n**Result → Create**; a task with **Task Control** goes to 4 and waits for **Approve** or\n**Return for Rework** by its creator.\n\n### Get Many reads by ID\n\nAs in the CRM node: sorted by ID, the next 50 above the last one, no total. **Order (JSON)**\nswitches to offset paging, which counts the total on every page and gets slower as the task list\ngrows.\n\n## Bitrix24 Messenger\n\nChats, messages, files and notifications, as the user who owns the webhook. Everything this node\nsends comes from that user, and everything it reads is what that user sees: a chat they are not\nin does not open.\n\n| Resource | Operations |\n|---|---|\n| **Message** | Send, Update, Delete, Get Many, Search, Like, Mark as Read, Mark as Unread, Mark All as Read, Send Typing Indicator, Create Object From Message, Run Bot Command |\n| **Chat** | Create, Get, Find by Linked Object, Search, Update, Set Owner, Mute or Unmute, Leave |\n| **Chat Member** | Add, Remove, Get Many, Get IDs |\n| **Recent Chat** | Get Many, Get Changes, Pin or Unpin, Hide, Set Unread Mark |\n| **File** | Upload, Download, Attach Drive Files, Save to Drive, Delete, Get Chat Folder |\n| **Notification** | Send, Get Many, Search, Delete, Mark as Read, Mark All as Read, Answer, Press Button, Get Types |\n| **User** | Get, Get Many, Search, Get Colleagues, Get Status, Set Status, Set Away, Clear Away, Get Unread Counters |\n| **Department** | Get, Get Employees, Get Heads, Search |\n| **Search History** | Add, Remove, Get Many |\n| **Event Queue** | Subscribe, Unsubscribe, Get Many |\n\n### Dialog ID\n\nA conversation has one address in three spellings: `chat123` for group chat 123, `sg12` for the\nchat of workgroup 12, and a plain user ID such as `7` for the private chat with user 7. Operations\nthat only make sense for group chats take **Chat ID**, a number, and accept `chat123` as well.\n\n**Chat → Find by Linked Object** gets the chat of a task (`TASKS_TASK` and the task ID), a CRM\nrecord (`CRM` and `DEAL|1663`), a workgroup, a calendar event or a call. **Create** refuses to bind a\nnew chat to a workgroup: every group already has its chat, and the documentation warns that a\nsecond one breaks the chats of the group's tasks.\n\n### Sending\n\n**Message → Send** takes text with BB codes (`[B]bold[/B]`, `[USER=7]Name[/USER]`,\n`[URL=https://example.com]link[/URL]`), plus optional **Attachment (JSON)**, **Keyboard (JSON)** and\n**Context Menu (JSON)**. Keyboard buttons that only run a bot command are dropped by Bitrix24 when a\nuser sends the message; links and `ACTION` buttons stay.\n\n**Update** refuses an empty text. Bitrix24 treats an empty `MESSAGE` as \"delete this message\", and a\nfield mapped from an empty expression should not do that silently.\n\n**Notification → Send** puts a notice into a user's bell instead of a chat, from the webhook user or\nas a system notice. The documented tags that replace or group notifications do nothing through a\nwebhook: Bitrix24 does not store them, so the node does not offer them.\n\n### Reading\n\n**Message → Get Many** reads the latest messages, or pages back from a message or forward from it,\n50 per request. Each message gets its `author` and `files` joined in, which Bitrix24 returns as\nseparate lists. **Search** finds messages in one chat by text and dates, 200 per request.\n\nReading messages and notifications does not change unread counters. Marking is done only by the\nMark operations.\n\n### Files\n\n**Upload** sends binary data into a chat in one request (`im.v2.File.upload`, up to 100 MB).\n**Download** puts a chat file into binary data. There is no \"get download link\" operation on purpose:\nthe link Bitrix24 returns to a webhook is `/rest///download/…`, so it carries the\nwebhook secret. The node fetches it inside the operation, only from the portal it came from, and\nkeeps it out of the output and out of error messages.\n\n### Event Queue\n\nBitrix24 can record the messenger events of a user and hand them out on request, which needs no\npublic address. **Subscribe** starts recording new messages, deletions, reactions and new members in\nevery chat of the webhook user. **Get Many** reads them; passing the `nextOffset` of the previous read\nconfirms, and deletes, what came before. Events are kept for 24 hours. The **Bitrix24 Messenger\nTrigger** does all of this by itself.\n\n## Bitrix24 Open Lines\n\nThe contact center: conversations with clients who write from a website chat, Telegram, WhatsApp\nand other connected channels. Messages sent here reach clients in their messenger.\n\n| Resource | Operations |\n|---|---|\n| **Dialog** | Get, Get Chat by User Code, Get History, Start Session, Start Session From Message, Join, Take Over, Pin or Unpin, Pin All, Unpin All, Set Silent Mode, Rate as Supervisor, Create Lead, Save as Quick Answer |\n| **Operator** | Take, Skip, Transfer, Finish, Finish Another Operator's, Mark as Spam |\n| **CRM Chat** | Get Many, Get Latest Chat ID, Add User, Remove User, Send Message |\n| **Open Line** | Create, Get, Get Many, Update, Delete, Get Public Page Link, Connect Network Line, Send Network Message |\n| **Statistics** | Get Summary, Get Sessions, Get Session Metrics, Get Transfers, Get Ratings, Get Operator Load |\n| **Bot Dialog** | Send Automatic Message, Hand to Free Operator, Transfer, Finish |\n\nA conversation is an open channel chat (**Chat ID**), and each round of it, from the first client\nmessage to closing, is a session (**Session ID**). To reach the client of a deal, find the chat with\n**CRM Chat → Get Many** or **Get Latest Chat ID**, then **CRM Chat → Send Message** from an employee who\nis in that chat.\n\n**Open Line → Create** and **Update** show the settings people usually change: queue, distribution,\nworking hours, days off, welcome message, rating request. The other sixty or so settings of\n`imopenlines.config.add` go into **Other Settings (JSON)** by their names.\n\n**Statistics** reads the `imopenlines.v2` reports: totals for a period with breakdowns by channel,\nhour and operator; sessions with filters; per-session metrics and transfer history (any number of\nIDs, split into the batches Bitrix24 allows); client ratings; the current load of operators. A period\nis at most 366 days. These methods need access to open channel reports on the plan and for the user.\n\n**Bot Dialog** acts for a chatbot connected to a line. Through a webhook Bitrix24 must be told which\nbot: give the `botToken` it was registered with in `imbot.v2`, the Bot Token of the Bitrix24 Chatbot\nWebhook API credential.\n\nConnectors (`imconnector.*`) are not here: Bitrix24 does not let a webhook call them.\n\n## Bitrix24 Chatbot\n\nA bot of your own in the Bitrix24 messenger (Chatbots 2.0, `imbot.v2`): it has its own name and\navatar, people write to it privately or mention it in group chats, and it answers with text,\ncards, buttons and files. Everything it sends comes from the bot, not from the webhook user.\n\n| Resource | Operations |\n|---|---|\n| **Message** | Send, Update, Delete, Mark as Read, Get, Get Context, Add Reaction, Remove Reaction |\n| **Chat** | Create, Get, Update, Leave, Set Owner, Add Managers, Remove Managers, Show Activity Indicator, Set Input Field |\n| **Chat Member** | Add, Remove, Get Many |\n| **Command** | Register, Update, Get Many, Unregister, Answer |\n| **File** | Upload, Download |\n| **Bot** | Register, Get, Get Many, Update, Unregister, Get API Revision |\n| **Event** | Get Many |\n\n### Getting a bot going\n\n1. Create the **Bitrix24 Chatbot Webhook API** credential with a token of your own.\n2. Run **Bot → Register** once, with a code such as `support_bot` and a name. Registering the same\n code again returns the existing bot unchanged, so leaving this node in a workflow does no harm.\n3. Put a **Bitrix24 Chatbot Trigger** on the bot, and answer with **Message → Send** to the\n `chat.dialogId` of the event.\n\nA conversation is a **Dialog ID**: `chat123` for group chat 123, or a user ID such as `7` for the\nprivate chat of the bot with user 7. In an event from a private chat, `chat.dialogId` is already the\nother person's ID, so it goes straight back into Send.\n\n### Bot types\n\n**Type** is set at registration and cannot be changed later.\n\n- **Bot** gets every message of its private chats, and in group chats only the messages that mention\n it (`[USER=]…[/USER]`). This is the one most bots need.\n- **Supervisor** and **Personal Assistant** get every message of every chat they are in, and only\n they may read with **Message → Get** and **Get Context**. A plain bot asking gets\n `BOT_TYPE_NOT_ALLOWED`. Get Context returns up to 50 messages on each side of one, with authors,\n which is what an AI agent needs to see the conversation.\n- **Open Channel Bot** answers clients in open channels and otherwise behaves like Bot.\n\n### Buttons and commands\n\n**Keyboard (JSON)** puts buttons under a message. A button with `LINK` opens a page, one with\n`ACTION` inserts or sends text on the person's side, and one with `COMMAND` runs a slash command of\nthe bot:\n\n```json\n[{\"TEXT\": \"Talk to a manager\", \"COMMAND\": \"manager\", \"COMMAND_PARAMS\": \"sales\", \"BLOCK\": \"Y\"},\n {\"TYPE\": \"NEWLINE\"},\n {\"TEXT\": \"Price list\", \"LINK\": \"https://example.com/prices\"}]\n```\n\nThe command has to exist: **Command → Register** it first (`manager`, with a title for the command\nlist). Typing `/manager` and pressing the button both arrive as a **Command Called** event; the\nevent's `command.context` says which, `textarea` or `keyboard`. **Command → Answer** replies in the\nchat the command came from. According to the documentation that works even in a chat the bot is not\nin, as a system line; only answers in the bot's own chats were tried.\n\nThe node adds the bot's ID to every keyboard it sends, because Bitrix24 warns that an updated\nkeyboard without one may send the press to the wrong bot.\n\n**Chat → Set Input Field** turns typing off in a chat, so people can only press buttons.\n**Show Activity Indicator** shows \"typing…\" or an agent status such as \"Agent is searching for\ninformation…\" for up to 600 seconds while a workflow prepares the answer.\n\n### Events and files\n\n**Event → Get Many** reads the bot's queue by hand; the trigger does the same on a schedule. Passing\nan offset deletes the events before it for every reader of that bot. **Include Webhook User Events**\nadds the webhook user's own messenger events (`ONIMV2…`) to the same read; that needs the `im`\npermission and **Bitrix24 Messenger → Event Queue → Subscribe** first.\n\n**File → Download** puts a chat file into binary data. The one-time link Bitrix24 hands out for it\ncontains the webhook code, as it does in the messenger node, so it is fetched inside the operation\nand never shown.\n\n**Bot → Update** changes the name, profile, flags and background, and can switch **Event Delivery**\nto a webhook URL of your own. Bitrix24 then posts each event there with an OAuth token of the bot\ninside, and does not retry a failed delivery. The trigger needs the default, **Keep for Polling**.\n\n## Bitrix24 Drive\n\nFiles and folders on Bitrix24 Drive, as the webhook user: its personal drive, the drives of its\nworkgroups and the company drive, plus any drive it has been given access to.\n\n| Resource | Operations |\n|---|---|\n| **File** | Upload, Upload New Version, Download, Get, Search, Rename, Copy, Move, Move to Trash, Restore From Trash, Delete Permanently, Get Public Link, Get Versions, Get Version, Download Version, Restore Version, Get Fields |\n| **Folder** | Create, Get, Get Items, Rename, Copy, Move, Move to Trash, Restore From Trash, Delete Permanently, Share With User, Get Public Link, Get Fields |\n| **Storage** | Get by Owner, Get, Get Many, Get Root Items, Get Fields |\n| **Attached File** | Get, Download |\n\n### Where a file goes\n\nEverything on Drive lives in a folder, and a drive's top level is a folder too: its ID is\n`ROOT_OBJECT_ID`. **Storage → Get by Owner** finds it for the webhook user, another user, a\nworkgroup or the company in one call. **File → Upload** and **Folder → Create** take a folder\nID, or a storage ID with *Drive Root*.\n\nA webhook made by an administrator sees the drive of every user and workgroup, so **Storage → Get\nMany** with Return All can take many requests.\n\n**Access Rights** on both operations hand the new folder or file to someone besides whoever the\nparent folder already lets in: an access code (`U35` a user, `D12` a department, `DR12` that\ndepartment with the ones under it, `*` everybody) and a level from the portal's own list. *Deny*\nturns a row around — it takes the level away from that person and beats the rights the parent\nfolder passes down, which is how you keep one folder out of sight inside a shared one. Rights on a\nfolder inside a folder work since 17.09.2026; before that Bitrix24 took them only at a drive root,\nand **Folder → Share With User** was the only way to hand over a subfolder afterwards.\n\n### Upload and download\n\n**Upload** takes a file from binary data and sends it inside the request, base64-encoded; a 10 MB\nfile uploaded and came back byte for byte. **If the Name Is\nTaken** either adds a number, `report (1).pdf`, or fails with `File with this name already\nexists`.\n\n**Download** puts the file into binary data. Bitrix24 hands out a download link for that, and\nfor a webhook the link has the webhook code in it: `/rest///download/` for Drive\nfiles, `auth[ap]=` in the `uf.php` link of an attached file. So the node fetches the link\ninside the operation and removes `DOWNLOAD_URL` from every output. To give someone a file, use\n**Get Public Link**: it opens the file for anyone who has it, without signing in. The API has no\nmethod to switch such a link off again.\n\n**Attached File** reads files attached to feed posts, comments and list items by attachment ID.\nTasks in the new task card keep their files in the task chat instead and have nothing in\n`ufTaskWebdavFiles`.\n\n### Trash, versions and search\n\n**Move to Trash** is undone by **Restore From Trash**, but only with the ID: the trash cannot be\nlisted through the API. Restoring a folder needs an administrator, according to the\ndocumentation. **Delete Permanently** skips the trash.\n\n**Upload New Version** replaces the contents and keeps the file's name and ID. Do not count on\nthe old contents staying: after every new version **Get Versions** listed only the latest one,\nalso with uploads more than a minute apart, and the earlier contents could not be downloaded any\nmore.\n\n**Move** works within one drive. Moving a file or a folder to another drive answered `false` and\nleft it where it was; the node turns that into an error.\n**Copy** worked across drives, a folder with its contents included, so copy and delete the\noriginal instead.\n\n**Share With User** gives one person access to a folder. It answered `true` for another user and\n`false` for the webhook user itself.\n\n**Search** looks through names and the text of documents, 3 to 255 characters, on every drive the\nwebhook user can read or within one drive or folder. By the documentation it pages no further than\nthe 1000th result, so the most it returns is 1050. Files uploaded two minutes earlier were found on\nthe first try.\n\n### Filters\n\nDrive filters are narrower than the documentation says, and whatever they do not support is\ndropped without an error, so an unsupported filter returns everything:\n\n- A list matches any of its values when written as a plain array, `{\"ID\": [12, 15]}`. The `@` and\n `!@` prefixes from the documentation were ignored.\n- `>`, `>=`, `<`, `<=`, `!` and `%` (contains) work on the fields that **Get Fields** marks\n `USE_IN_FILTER`. For files and folders these are ID, NAME, TYPE, CODE, STORAGE_ID, PARENT_ID, the\n dates and DELETED_TYPE; a filter on SIZE or CREATED_BY in **Get Items** returned every item.\n **Get Versions** does filter on SIZE.\n- A date is read as the webhook user's own local time, and offsets are not understood. A value\n ending in `Z` or in an offset such as `+02:00` matched nothing, while the same moment written as\n the user's local time without an offset matched to the minute. **Get Items → Updated After**\n converts the date for you, from the workflow's time zone to the webhook user's (or the portal's,\n when the user has none set). In **Filter (JSON)** write it that way yourself:\n `{\"LAST_LOGIN\": \"2026-01-01T00:00:00+03:00\"}`.\n\nBoth methods leave out bots, mail users, extranet users and Open Channel accounts, so an ID that\nbelongs to one of those comes back as nothing found. **Fields to Return** makes the call faster: a\nlist without custom fields skips loading them altogether.\n\n### Writing to people\n\n**Invite** creates an employee and sends them the standard invitation email — a real letter to a\nreal address, and one more seat on the plan. **Update** changes a card, and *Active* off in it is\nwhat Bitrix24 calls dismissal. Both need a webhook made by an administrator.\n\n**Custom Field** adds a field to the card of every employee at once, and Bitrix24 upper-cases its\ncode and puts `UF_USR_` in front: `BADGE` is stored as `UF_USR_BADGE`, and that longer name is what\nGet Many and the employee card return. Whether the field holds one value or several is decided when\nit is created and cannot be changed afterwards.\n\n### Company structure\n\n**Department** is the classic company structure: a tree with one top-level department, a head per\ndepartment and any depth below. Employees belong to departments through their `UF_DEPARTMENT`, so\nmoving somebody is an **Employee → Update**, not a department operation.\n\nThe node does not cover the newer `humanresources.*` org structure that Bitrix24 is moving to —\nthose 24 methods answer `ERROR_METHOD_NOT_FOUND` on a portal without it, and there was nowhere to\ncheck them. Adding them later breaks nothing, since they would be new operations.\n\n### Working time\n\n**Working Day** is the timesheet of one person: Open starts the day, Pause puts it on a break, Open\nagain continues it, Close ends it. The API writes into a real timesheet and has no way to remove an\nentry afterwards, so a day opened by mistake stays in the reports. Times other than now need a\nreason, unless the employee has a flexible schedule — that is Bitrix24's own rule, not the node's.\n\n**Work Time Report** is the time control module: a month of an employee with every working day, how\nlong it lasted against the schedule, and the absences recorded in it. The days sit inside `report`\nin the answer, not at the top. **Get Report Access** says whether the module is on at all and whose\nreports the webhook user may read.\n\n**Office Network** holds the address ranges that count as the office. **Set** replaces the whole\nlist — whatever is not in the request stops being the office — so read the current ranges first and\nsend them back together with the new one.\n\n## Bitrix24 Business Processes\n\nBusiness processes of the portal: starting one on a record, seeing what runs, and answering the\ntasks a process puts in front of people. The webhook needs the `bizproc` permission, **and the\nwebhook has to belong to an administrator** — Bitrix24 answers `ACCESS_DENIED` to everyone else on\nmost of these methods.\n\n| Resource | Operations |\n|---|---|\n| **Workflow** | Start, Get Instances, Terminate, Delete |\n| **Task** | Get Many, Complete, Delegate |\n| **Template** | Get Many |\n| **Event** | Send Result, Write Log |\n\n### Naming the record\n\nA process always runs on a document, and Bitrix24 names one with three strings: a module, a PHP\nclass and an ID. The node asks for **Document Type** and **Record ID** instead and writes them out:\n\n| Document Type | What goes to Bitrix24 |\n|---|---|\n| Deal, Lead, Contact, Company | `['crm', 'CCrmDocumentDeal', 'DEAL_777']` |\n| Quote, Invoice | `['crm', 'Bitrix\\Crm\\Integration\\BizProc\\Document\\Quote', 'QUOTE_5']` |\n| Smart Process Item | `['crm', '…\\Document\\Dynamic', 'DYNAMIC_147_1']`, with **Container ID** the process |\n| List Element, News Feed Process | `['lists', 'Bitrix\\Lists\\BizprocDocumentLists', '9']`, with **Container ID** the list |\n| Drive File | `['disk', 'Bitrix\\Disk\\BizProcDocument', '88']`, with **Container ID** the storage |\n\nThree of them carry a container: a smart process item, a list element and a Drive file are only\naddressable together with the process, the list or the storage they live in. **Container ID** shows\nup for those three and is required there.\n\n**Template → Get Many** uses the same picker to answer a narrower question — which templates can run\non deals — and sends the type without a record: `['crm', 'CCrmDocumentDeal', 'DEAL']`.\n\n### Starting and stopping\n\n**Workflow → Start** takes the template ID and the record, and answers a workflow ID: a string like\n`66e412fdc9bd44.36306599`, not a number. Every other Workflow operation takes that string.\n\n**Terminate** stops a process and keeps what it has done, with an optional line for the log.\n**Delete** removes the process and its data altogether. **Get Instances** lists what is running,\nfiltered by template, by starter or by record, and adds `entityType` and `entityId` next to\nBitrix24's own `DEAL_777`.\n\n### Tasks of a process\n\nA running process stops at a person: approve this, acknowledge that, fill in a number. **Task → Get\nMany** reads those, **Complete** answers one, **Delegate** hands several to somebody else.\n\nWhich answers a task takes depends on its kind, and the API does not say which kind it is: an\napproval takes Yes and No, a notice takes Acknowledged, a request for information takes\nAcknowledged and sometimes Cancel. A wrong answer comes back as an error from Bitrix24, not from\nthe node. What a task asks for beyond the answer is in `PARAMETERS.Fields` of Get Many, and those\nvalues go into **Fields (JSON)** of Complete.\n\nComplete answers for the user the webhook belongs to, and only that user's own tasks.\n\n### Answering a waiting process\n\n**Event → Send Result** is the other direction: a process is paused on an automation rule or an\naction that waits for an outside answer, and this hands it back. It needs the event token that the\nrule posted, so the parameter is filled from the workflow input, not typed in.\n\nThose waiting rules and actions are registered by an installed application — `bizproc.robot.add` and\n`bizproc.activity.add` refuse a webhook — so this pair is useful when such an application is already\non the portal. **Write Log** puts a line into the process log through the same token, for a long job\nthat wants to report progress. Both need logging switched on in the template.\n\n## Bitrix24 Lists\n\nUniversal lists: the tables a portal keeps next to the CRM — requests, contracts, registries — with\ntheir elements, fields and sections. The webhook needs the `lists` permission.\n\n| Resource | Operations |\n|---|---|\n| **Element** | Get Many, Create, Update, Delete, Get File URL |\n| **List** | Get Many, Create, Update, Delete, Get Type |\n| **Field** | Get Many, Get Types, Create, Update, Delete |\n| **Section** | Get Many, Create, Update, Delete |\n\n### Naming the list\n\nEvery operation names the list twice. **List Type** is where it lives — universal lists of the\nportal, group lists inside a workgroup, or process lists of the news feed — and then **List ID** or\n**List Code** says which one. Bitrix24 refuses the call when the type does not match the list, and\n**List → Get Type** answers the type when only the ID is known. A self-hosted portal with its own\ninformation block types has **Custom List Type** for them; it needs the list named by ID or code.\n\n### Fields carry the codes\n\nAn element's values live under field codes, not names: `PROPERTY_951`, `PROPERTY_1003`. **Field →\nGet Many** is what gives them, so a workflow that writes elements usually reads the fields first.\nThose codes go into **Fields (JSON)** of Create and Update and into the filter of Get Many\n(`{\"=PROPERTY_951\": 1269}`). A field set as multiple takes an array even for one value.\n\n**Field → Create** fixes the type once and for all: Bitrix24 does not change the type of an existing\nfield, and Update wants the type passed again unchanged. Values of a List field go in as\n**Values of a List Field**, one per line.\n\n### Files of an element\n\n**Element → Get File URL** answers the links of a File or File (Drive) field — paths on the portal\nlike `/bitrix/tools/disk/uf.php?attachedId=103&action=download`, one per value. **Field ID** here is\nthe number without the `PROPERTY_` prefix: `951` for `PROPERTY_951`.\n\n## Bitrix24 Catalog\n\nThe product catalog the CRM sells from: products, their variations and services, prices, sections,\nproperties, units, VAT rates, stores, stock and inventory documents. 148 operations across 26\nresources: every one of the 145 working `catalog.*` methods, plus **Product Image → Download**,\n**Inventory Document → Get** and **Price → Set Product Prices**, which Bitrix24 has no single method for. The webhook needs the `catalog`\npermission, and `crm` for the currency pickers.\n\n| Resource | Operations |\n|---|---|\n| **Product, Variation, Product With Variations, Service** | Create, Get, Get Many, Update, Delete, Get Fields, Download File |\n| **Product Image** | Upload, Get, Get Many, Download, Delete, Get Fields |\n| **Price** | Create, Get, Get Many, Update, Delete, Get Fields, Set Product Prices, Replace Product Prices |\n| **Price Type, Price Type Name** | Create, Get, Get Many, Update, Delete, Get Fields (+ Get Languages) |\n| **Price Type Access** | Create, Get Many, Delete, Get Fields |\n| **Markup** | Get, Get Many, Get Fields |\n| **Rounding Rule** | Create, Get, Get Many, Update, Delete, Get Fields, Get Rounding Types |\n| **Section, Property, Property List Value** | Create, Get, Get Many, Update, Delete, Get Fields |\n| **Property Feature** | Create, Get, Get Many, Update, Get Fields, Get Available |\n| **Property Filter Setting** | Get, Get Many, Set |\n| **Unit of Measure, VAT Rate, Store** | Create, Get, Get Many, Update, Delete, Get Fields |\n| **Unit Ratio, Stock** | Get, Get Many, Get Fields |\n| **Inventory Document** | Create, Get, Get Many, Update, Delete, Delete Many, Conduct, Conduct Many, Cancel, Cancel Many, Get Fields, Get Types, Get Inventory Mode |\n| **Document Item** | Create, Get Many, Update, Delete, Get Fields |\n| **Document Supplier** | Create, Get Many, Delete, Get Fields |\n| **Document Custom Field Value** | Get Many, Update |\n| **Catalog** | Get, Get Many, Get Fields, Is Variations Catalog |\n\n### Which catalog\n\nA portal keeps its products in one catalog and, once a product has variations, the variations in\na second one tied to it (`productIblockId` of the second names the first). **Catalog** can be left\nempty everywhere: the node takes the catalog the CRM uses, or the variations catalog tied to it.\nBitrix24 refuses a product list without it — `Required filter fields: iblockId` — so the node always\nsends one.\n\n### Four kinds of item\n\n**Product**, **Variation**, **Product With Variations** and **Service** are four method families of\none shape. **Product → Get Many** returns every kind that lives in the product catalog, told apart by\n`type`: 1 a simple product, 3 a product with variations, 7 a service. Variations are read with\n**Variation → Get Many**, and **Parent Product ID** narrows them to one product. A product with\nvariations has no price or stock of its own; its variations do.\n\n### Fields and properties\n\n**Fields to Return** left empty reads every field and every property. The list method has no \"all\"\n(`select: [\"*\"]` answers `Required select fields: id, iblockId`), so the node first asks\n`getFieldsByFilter` for the field names — one extra call per Get Many.\n\nProperty values go into **Property Values (JSON)** keyed by property ID or code:\n`{\"258\": \"Oak\", \"COLOR\": [\"Red\", \"Blue\"]}`. A multiple property takes an array, a list property the\nID of its value (**Property List Value → Get Many** with `{\"propertyId\": 258}`). A list property\nwith a single value is the exception: Bitrix24 treats it as a checkbox, reads it as `\"Y\"` or `\"N\"`\nand takes `\"Y\"` to set it. An empty string clears a value, an empty array a multiple one. The\nnode sends every value as `{\"value\": …}`, the only form update takes (see\n[Quirks](#catalog)). **Property → Get\nMany** gives IDs, codes and types; the field descriptions of Get Fields type every property alike,\nso the property list is where a file property (`propertyType` F) shows. Read back, a property holds\n`{\"value\": …, \"valueId\": …}`, or an array of those.\n\nTo find the product an outside system knows, filter Get Many by **External ID**: `{\"xmlId\": \"SKU-1\"}`.\n\n### Prices\n\nThe selling price is not a product field: a product has one price per price type. **Set Product\nPrices** sets several at once: a price of a listed type is changed in place and keeps its ID, a\nmissing one is added, and prices you do not list stay unless **Remove Other Prices** is on. It\nreads the current prices and makes one call per price. **Replace Product Prices** does it in one\ncall through `catalog.price.modify`: the product ends up with exactly the prices listed, and every\none of them gets a new ID. **Purchasing Price** is a product field, the price the item costs to buy in.\n\nA new price type comes with view and buy access for the default customer groups, so **Price Type\nAccess → Create** for one of them answers \"The specified access type for this group already exists\".\n\n### Files and pictures\n\n**Download File** fetches a picture or a file property of an item. **Product Image → Download**\nfetches one image by the public link Bitrix24 gives it. **Upload** adds an image from binary data;\nwithout a type it goes to the gallery (`MORE_PHOTO`).\n\n### Stock and inventory documents\n\n**Stock → Get Many** tells what every store holds and how much is reserved, e.g. of one product\nwith `{\"productId\": 101}`. The API does not write stock directly. With inventory management off\n(**Inventory Document → Get Inventory Mode** answers `false`), the product's **Quantity** field is\nthe stock. With it on, stock moves only through inventory documents: **Create** a document,\nadd products with **Document Item → Create**, then **Conduct**. **Cancel** takes a conducted\ndocument back. `status` of a document is N for a draft, Y once conducted, C when cancelled. With\ninventory management off, documents and their items can be created, changed and deleted, but\nConduct and Cancel answer \"Inventory management has to be enabled to process inventory objects\".\nSuppliers and custom fields work in that mode too.\n\n**Document Supplier → Create** takes a CRM company or contact from the Supplier category: the\ncategory coded `CATALOG_CONTRACTOR_COMPANY` (or `…_CONTACT`) in **CRM → Category → Get Many**. A\ncustom field of documents is made per document type with **CRM → Custom Field Config → Create**,\nmodule `catalog`, entity `CAT_STORE_DOCUMENT_A` for receipts. **Document Custom Field Value** then\nnames it `field` plus the ID that call answered — `field287`, not the `UF_…` code.\n\n## Bitrix24 Event Log\n\nWhat the portal wrote down about itself: sign-ins, password changes and the other actions the event\nlog keeps. Read-only — Bitrix24 has no method that adds an entry. The webhook needs the `main`\npermission and an administrator behind it; for anyone else every method here answers `Access denied`.\n\n| Resource | Operations |\n|---|---|\n| **Entry** | Get Many, Get, Get New |\n| **Field** | Get Many, Get |\n\nThe five methods belong to REST 3.0, which the node addresses and unwraps for you. What shows\nthrough is the error format: it names the field it refused and why.\n\n### Only five fields can be filtered\n\n`id`, `timestampX`, `auditTypeId`, `userId`, `guestId`. A condition on any of the other eight —\n`severity`, `moduleId`, `itemId`, `remoteAddr`, `userAgent`, `requestUri`, `siteId`, `description` —\nis not ignored but fails the whole call: `severity: DTO \"EventLogDto\" in field \"severity\" requires\nattribute \"Filterable\" to perform this request`. The same five are the ones that sort, and **Field →\nGet Many** says so per field in `filterable` and `sortable`.\n\n**Filter** builds the usual conditions: a period, an event type such as `USER_AUTHORIZE`, a user.\n**Extra Conditions (JSON)** takes the REST 3.0 form as it is — an array of `[\"field\", \"operator\",\nvalue]` triples, e.g. `[[\"timestampX\", \">=\", \"2026-09-01T00:00:00+03:00\"]]`.\n\nDates go in as ISO 8601 down to the second. Milliseconds are refused, and a date built in\nJavaScript carries them, so the node cuts them off before the call.\n\n### Get Many reads a period, Get New polls\n\n**Get Many** is the report: a period, a sort order, and paging done for you up to Limit or to\neverything. **Get New** is the poll — it takes the ID the previous run stopped at and answers what\nappeared after it, so a schedule reads every entry once and none of them twice. The ID grows with\nevery entry and never repeats; a time can be the cursor instead when the order of writing matters\nless than the order of events.\n\n## Bitrix24 Consents\n\nThe agreements a portal keeps and the consents people give to them: personal data, newsletters,\nterms of use. The webhook needs the `userconsent` permission, and any user may call these methods.\n\n| Resource | Operations |\n|---|---|\n| **Agreement** | Get Many, Get Text |\n| **Consent** | Create |\n\nAgreements themselves are written and edited in the Bitrix24 interface — the API has no Create or\nUpdate for them, only the three methods above.\n\n### Collecting a consent takes three steps\n\n1. **Agreement → Get Many** finds the agreement by name and tells whether it is switched on:\n `ACTIVE` is `N` for a disabled one, and a disabled agreement should not be shown.\n2. **Agreement → Get Text** returns `TEXT` to display and `LABEL` for the button.\n3. **Consent → Create** stores the answer against the agreement ID and the IP address it came from.\n It answers the ID of the record.\n\nThe form is yours. Bitrix24 hands out the wording and keeps the record; it displays nothing and\nasks no one. **IP Address** is required — Bitrix24 stores whatever it is given and does not check it.\n\n**Substitutions** fill a standard agreement, the kind made from a Bitrix24 template: the company\nname and address, the purpose, the third parties, an e-mail, the button caption. An agreement\nwritten by hand holds arbitrary HTML and ignores them.\n\nA consent, once written, stays: no REST method deletes one.\n\n## Bitrix24 AI\n\nThe AI services a portal sends prompts to. This node connects a service of your own and lists what\nis connected; it runs no prompt. Bitrix24 calls the service itself, when a person uses AI in a CRM\ncard, a chat or an automation rule. The webhook needs the `ai_admin` permission and an\nadministrator behind it.\n\n| Resource | Operations |\n|---|---|\n| **Service** | Get Many, Register, Unregister |\n\n**Register** takes a code, a category — `text`, `image`, `audio` or `call` — and the address of an\nendpoint you host. Bitrix24 checks that address before it saves anything: it has to answer `200`.\nAfterwards Bitrix24 posts prompts to it with a `callbackUrl` and an `errorCallbackUrl`, and expects\nan answer within five seconds — `200` with the result, or `202` and the result posted to the\ncallback later. The link has a lifetime, in `ttl`, after which the person sees nothing. An `image`\nservice has to work that asynchronous way.\n\n**Settings** carries what the service code reads: the model alias shown next to it, whether context\nis counted in tokens or symbols, and the context limit.\n\n**Unregister** removes a service by its code and answers `false`, not an error, when there was\nnothing to remove.\n\n## Bitrix24 Trigger\n\nStarts a workflow when Bitrix24 posts an outgoing webhook.\n\n1. In n8n, copy the trigger's **Production URL**.\n2. In Bitrix24, **Developer resources → Other → Outgoing webhook**: paste the URL, tick the\n events, save.\n3. Copy the **Application token** Bitrix24 shows into the trigger.\n\nIt has to be done by hand. The method that would subscribe the URL automatically, `event.bind`,\nanswers `WRONG_AUTH_TYPE` to inbound webhooks: only an installed application may call it.\n\nRequests without the right application token get `403` and never start the workflow, and the\ntoken is removed from the output. The **Events** list has 196 event codes from the\ndocumentation, the catalog's `CATALOG.PRODUCT.ON.ADD` and the like among them; codes it lacks go\ninto **Other Event Codes**. Events not selected are answered `OK` and dropped.\n\nThe five chat events `ONIMV2…` are in the list, but an outgoing webhook never delivers them:\nBitrix24 keeps them in the event queue of the user who subscribed, and they are read from there\nby the [Bitrix24 Messenger Trigger](#bitrix24-messenger-trigger). The list says so under each of\nthem.\n\nBitrix24 sends only IDs, for example `data.FIELDS.ID` on `ONCRMDEALUPDATE`. **Fetch the Changed\nCRM Record** reads the whole lead, deal, contact, company, quote or smart process item after an\nadd or update event and puts it under `record`. If that read fails, the workflow still starts,\nwith the reason in `recordError`.\n\n## Bitrix24 Messenger Trigger\n\nStarts a workflow on new, edited or deleted messages, reactions and new members in the chats of the\nwebhook user. It polls Bitrix24's event queue on n8n's schedule, so it works on an n8n without a\npublic address and needs no setup in Bitrix24.\n\n- On activation it subscribes the webhook user and skips whatever is already queued, so turning the\n workflow on does not replay the last day.\n- **Dialog IDs** narrows it to some conversations: `chat123` for a group chat, a user ID for a\n private one.\n- The webhook user's own messages and reactions are dropped unless **Include Own Events** is on, so a\n workflow that answers in the same chat does not start itself.\n- A manual test run reads what is queued without confirming it; the active workflow still gets it.\n\nBitrix24 keeps one queue per user. A second workflow, or another application reading the same user,\ntakes events away from this one: use a separate webhook user per listener. Deactivating the workflow\ndoes not unsubscribe; **Messenger → Event Queue → Unsubscribe** does.\n\nAn edit made through the REST API did not reach the queue, while new messages, reactions and\ndeletions did. Edits made in the Bitrix24 apps were not tried.\n\n## Bitrix24 Chatbot Trigger\n\nStarts a workflow on messages to a bot, slash commands and button presses, reactions to the bot's\nmessages, the bot being added to a chat, and a chat opened through a link with `BOT_CONTEXT` data.\nIt polls the bot's event queue on n8n's schedule, so it works on an n8n without a public address.\n\n- **Events** defaults to New Message and Command Called.\n- On activation it checks that the bot keeps its events","readmeFilename":"README.md"}