Steps and facts
- Use Configuration โ Bitrix24 in the workspace that owns the customer leads. The workspace owner or admin enters the portal address and chooses Connect Bitrix24.
- Authorize on Bitrix24. Your password stays with Bitrix24. A compatible CatchGrow application must be installed and configured for that portal.
- A local Bitrix24 application serves its own portal. The current local pilot does not provide universal one-click installation for every organization; wider distribution requires a shared app and platform setup.
- If a local app is required, its server installation path is https://catchgrow.ai/api/bitrix24_install.php and its handler is https://catchgrow.ai/api/bitrix24_oauth_callback.php. Grant CRM only. The administrator stores app credentials privately; never submit secrets in this public chat.
- Select only customer-facing CRM fields. The assistant may use fresh permitted facts about the current customer; internal notes and another customer's records must not be exposed.
- Keep export paused until one designated test lead appears once in the correct entity. A Deals pipeline called Leads is not the Lead entity.
- Enable Send existing and new customer leads and save only after confirming the destination; this can send existing leads as well as new ones.
- Products, orders, stock, bookings and existing contact/deal matching are not covered by the current lead-field connector without additional mapping. A sales stage never proves payment or delivery.