SkillFoxx

Bitrix24 Open Lines chatbot skill

bitrix24-open-lines-bot

A Claude Code skill with real-portal-verified imbot.v2 and imopenlines details: bot registration, the event contract, and handoff to an operator

  • 0 ★ on the repository
  • Last commit
  • MIT
Skill

Minimal access

Why this level

  • Only reference knowledge for the agent; the skill itself makes no requests
All reasons and checks
Russian stack

svjszn/bitrix24-openlines-skillAuthor:soajv

Install

Services

Manual install

git clone https://github.com/soajv/bitrix24-openlines-skill.git && cp -r bitrix24-openlines-skill/skills/bitrix24-open-lines-bot ~/.claude/skills/

Copy the skill folder into your Claude Code skills directory.

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • Only reference knowledge for the agent; the skill itself makes no requests

This is third-party code. Review the repository files before installing.

What it does

The skill gives an agent the knowledge to embed a chatbot into an already-existing Bitrix24 Open Line via imbot.v2.Bot.register, rather than registering a new channel type through imconnector, which needs an OAuth app and rejects webhook auth with WRONG_AUTH_TYPE. It explains why imopenlines.config.update with WELCOME_BOT_ID does not attach a bot to the line, since that is a separate, older greeting feature. It covers the real nested registration response shape, how to make it idempotent across restarts, the ONIMBOTV2MESSAGEADD incoming event contract with its auth.application_token check, and the calls to reply and hand a session off to an operator.

Who it is for. For developers building a chatbot inside a Bitrix24 Open Line with the help of an AI agent.

Good fit when

  • You are embedding a bot into an already-configured Open Line
  • You are confused why WELCOME_BOT_ID does not attach the bot to the line
  • You need the imbot.v2 event contract and operator handoff

Not a fit when

  • You need to register a brand-new channel or connector type: that needs a full OAuth app
  • You need general Bitrix24 auth basics: there is a related foundational skill for that

Example request

Register a bot in a Bitrix24 Open Line via imbot.v2 and set up handing the dialog off to an operator

Limitations

This is a knowledge file for an agent, not a ready bot or library; the repo has no bot code of its own. It relies on the related bitrix24-rest-api skill for basic auth. The facts are dated September 2026 and were verified against one real portal.

How to disable. Delete the skills/bitrix24-open-lines-bot folder from your agent's skills directory.

FAQ

Can I add a new channel with just a webhook?

No, the whole imconnector.* group rejects webhook auth with WRONG_AUTH_TYPE; you need a full OAuth app or manual setup in the UI.

Why doesn't the bot respond after setting WELCOME_BOT_ID?

Because that is a separate, older greeting feature that never fires ONIMBOTV2MESSAGEADD; you need imbot.v2.Bot.register with isSupportOpenline.

Discussion

No questions or reviews yet.

All Bitrix24 tools

Bitrix24 REST API skill

bitrix24-rest-api

Russian stack

A Claude Code skill with real-portal-verified Bitrix24 REST API gotchas: auth modes, errors hidden under HTTP 200, retries and rate limits

SkillMinimal access
Russian stack

A Bitrix24 REST skill split into capability packs with a method allowlist, risk confirmations and an audit log

SkillBroad access26

Bitrix24 BI-connector Claude Code skill

Bitrix24 BI-connector — Claude Code skill

Russian stack

A Claude Code skill for Bitrix24 BI-analytics: list tables, describe columns and pull rows with natural-language filters

SkillExtended access9

Bitrix24 for OpenClaw

OpenClaw Bitrix24

Russian stack

OpenClaw plugin and skill: the agent chats in Bitrix24 Messenger and works with CRM, tasks, calendar and drive

PluginBroad access12
Russian stack

Bitrix24 as mission control for AI dev agents: a kanban task conveyor, shared memory and one-button phone acceptance

SkillBroad access1
Russian stack

A Claude Code and Codex skill for 1C-Bitrix and on-premise Bitrix24 development: check the project core first, then answer

SkillExtended access22

README in short

The README explains this is a knowledge file, not a bot framework, and covers two integration paths for Open Lines: a bot inside an existing line via imbot.v2, or a new channel type via imconnector. It lists the WELCOME_BOT_ID trap, the real registration response shape, safe zero-side-effect ways to check webhook permissions, the event contract and reply/handoff calls, and a generic pattern for wiring the flow into an LLM conversation loop.

README badge

Original SKILL.md

---
name: bitrix24-open-lines-bot
description: How to build a chatbot that answers inside an existing Bitrix24 Open Line — registration via imbot.v2, the incoming event contract, replying, and handing off to a human operator. Load this before building or debugging the Bitrix24 text-channel sales agent.
---

# Bitrix24 Open Lines chatbot

Source: official Bitrix24 REST API docs, verified Sep 2026. See bitrix24-rest-api skill first for general auth and retry conventions this builds on.

## The two integration paths — pick the right one

- A bot that answers inside an already-existing Open Line — register via imbot.v2.Bot.register with isSupportOpenline: true. This is almost certainly what is meant by a text agent in Open Lines.
- A brand-new channel type — requires imconnector.register plus imconnector.activate and imconnector.connector.data.set. Heavier, and not needed just to add an AI responder to an existing line.

Confirmed empirically: the entire imconnector.* family rejects inbound-webhook auth outright with WRONG_AUTH_TYPE.

Report a problem