Instagram Bot Development with Bitrix24 Integration

Instagram Bot Development with Bitrix24 Integration

Manual handling of Instagram Direct messages can take up to 3 hours a day. Each message requires reading, responding, and manually entering into CRM. As lead flow grows, managers simply can't keep up, and some leads are lost. We automate this process: the bot responds according to scenarios, qualifies leads, and passes them to Bitrix24. The manager works with the client from CRM without switching windows. Our team has 10+ years in Bitrix24 development and external API integrations, with dozens of integrations for e-commerce, services, and manufacturing. Automation cuts response time from 30 minutes to 5 seconds (10x faster than manual), and the bot handles up to 80% of routine questions. Every lead enters the CRM automatically, eliminating losses. Typical cost for such integration ranges from $2,000 to $5,000, and clients see an average of 30% reduction in support costs, saving $10,000 per year.

Technical Requirements and Limitations of Instagram Messaging API

Instagram Messaging API works through the Meta platform. To get started you need:

• Instagram Business or Creator account linked to a Facebook page.
• Facebook Developer App with Messenger + Instagram products.
• Permissions: instagram_basic, instagram_manage_messages, pages_manage_metadata.
• HTTPS server for webhook.

Official Meta for Developers documentation highlights key limitations:

• Bot messages are only accepted within 24 hours of the user's last message.
• The bot cannot initiate a conversation.
• instagram_manage_messages requires Meta app review.
• Bulk messaging is prohibited.

{
  "entry": [{
    "id": "IG_ACCOUNT_ID",
    "messaging": [{
      "sender": { "id": "IG_USER_IGSID" },
      "recipient": { "id": "IG_ACCOUNT_ID" },
      "timestamp": 1710000000000,
      "message": {
        "mid": "aWdfZAG9...",
        "text": "How much is delivery?"
      }
    }]
  }]
}

Message Processing Flow

Receiving Messages via Webhook

Code for receiving and processing webhook (same as above).

Retrieving the Instagram User Profile

$profile = json_decode(file_get_contents(
    "https://graph.instagram.com/{$igsid}?fields=name,username&access_token=" . IG_ACCESS_TOKEN
), true);
// Returns: name (display name), username (@handle)

This approach is lightweight but does not provide email or phone. We obtain that data through a qualification scenario.

Interaction Scenarios: Automatic Replies and Ice Breakers

Auto-Reply to Story Mentions

When your account is mentioned in Stories, a webhook event messaging_referral with type=STORY_MENTION arrives. The bot can automatically thank:

if ($event['type'] === 'STORY_MENTION') {
    sendIgMessage($igsid, "Thanks for mentioning us in your Story! 🙌 Want to learn about current promotions?");
    logLeadSource($igsid, 'story_mention');
}

Story mentions are warm leads: the user has already interacted with the brand.

Ice Breakers: Questions on First Dialog Open

Via the app API you can set prompts that the user sees when first opening a dialog with the business account:

callMetaApi('me/messenger_profile', 'POST', [
    'platform'     => 'instagram',
    'ice_breakers' => [
        ['call_to_actions' => [
            ['type' => 'postback', 'title' => 'Learn about delivery',     'payload' => 'DELIVERY_INFO'],
            ['type' => 'postback', 'title' => 'Submit a request',        'payload' => 'LEAVE_REQUEST'],
            ['type' => 'postback', 'title' => 'View catalog',     'payload' => 'CATALOG'],
        ]],
    ],
]);

Ice breakers reduce first response time and increase conversion.

Integration with Bitrix24

Lead Qualification Scenario

1. Incoming message.
2. If no state exists — greeting + quick replies.
3. On selecting "I want to order" — request phone/email.
4. Create a lead in Bitrix24 and notify the manager.
5. Reply: "A manager will contact you within an hour."

Dialog states are stored in Redis with key ig_dialog:{igsid}. TTL is 24 hours (Instagram activity window).

Bitrix24 REST API: Creating Leads and Activities

The integration is implemented using Bitrix24's REST API:

function createInstagramLead(string $igsid, string $username, array $data): int {
    return $b24->callMethod('crm.lead.add', [
        'fields' => [
            'TITLE'              => "Instagram: @{$username}",
            'SOURCE_ID'          => 'WEBFORM',
            'SOURCE_DESCRIPTION' => 'Instagram Direct',
            'PHONE'              => !empty($data['phone']) ? [['VALUE' => $data['phone'], 'VALUE_TYPE' => 'WORK']] : [],
            'EMAIL'              => !empty($data['email']) ? [['VALUE' => $data['email'], 'VALUE_TYPE' => 'WORK']] : [],
            'COMMENTS'           => "Instagram: @{$username}\nIGSID: {$igsid}",
            'UF_CRM_IG_IGSID'   => $igsid,
        ],
    ])['result'];
}

// Conversation history as an activity
$b24->callMethod('crm.activity.add', [
    'fields' => [
        'OWNER_TYPE_ID' => 1,
        'OWNER_ID'      => $leadId,
        'TYPE_ID'       => 4,
        'SUBJECT'       => "Instagram Direct: @{$username}",
        'DESCRIPTION'   => implode("\n", $dialogMessages),
    ],
]);

The lead is assigned source "Instagram Direct", allowing channel effectiveness tracking.

Benefits of Automating Instagram Direct

On one project for an e-commerce client, we reduced average response time from 30 minutes to 5 seconds and automated 80% of incoming questions. Automation unloads managers and ensures every lead enters the CRM without manual entry, eliminating loss. Managers continue the dialog from Bitrix24, seeing the full chat history. The cost per lead decreases, and conversion to deal increases.

How We Speed Up Meta Review

Experienced developers prepare documentation and a test account in advance: we provide scenario screenshots and bot operation videos. This cuts verification to 3–5 business days. We ensure your bot complies with platform policies — review passes on the first attempt.

Timeline and Cost

Total: 2–3 weeks including Meta review. Typical investment: $2,000–$5,000, with average annual savings of $10,000.

What's Included in the Work

• Architecture design and dialog flow.
• Webhook server deployment and HTTPS setup.
• Implementation of all scenarios (ice breakers, qualification, story mentions).
• Bitrix24 integration via REST API (leads, activities, notifications).
• API documentation and manager instructions.
• Assistance with Meta review.
• Testing and debugging in sandbox.
• Code warranty and post-launch support.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.