<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[fresite team blog]]></title><description><![CDATA[fresite team blog]]></description><link>https://fresite.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 18:36:16 GMT</lastBuildDate><atom:link href="https://fresite.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Connecting a website and a Telegram bot to amoCRM or Bitrix24]]></title><description><![CDATA[Most small businesses already run a CRM (amoCRM or Bitrix24), while the website and the Telegram bot live separately and leads get copied by hand. Here is…]]></description><link>https://fresite.hashnode.dev/connecting-a-website-and-a-telegram-bot-to-amocrm-or-bitrix24</link><guid isPermaLink="true">https://fresite.hashnode.dev/connecting-a-website-and-a-telegram-bot-to-amocrm-or-bitrix24</guid><dc:creator><![CDATA[fresite team]]></dc:creator><pubDate>Sat, 21 Nov 2026 06:32:32 GMT</pubDate><content:encoded><![CDATA[<p>Most small businesses already run a CRM (amoCRM or Bitrix24), while the website and the Telegram bot live separately and leads get copied by hand. Here is a practical way to connect them.</p>
<h2>1. Decide what gets created</h2>
<p>A request from the site or the bot should become a lead or a deal in the CRM you already use. Decide up front: lead or deal, which contact fields, which pipeline stage.</p>
<h2>2. What to pass</h2>
<p>Usually: name, contact method, source (<code>site</code> or <code>bot</code>), and the request text. If the site has a quiz, calculator or cart, pass the chosen answers or the order contents as a comment or custom fields.</p>
<h2>3. How it works technically</h2>
<ul>
<li>The website form and the bot's handler both send a JSON payload to one small backend endpoint.</li>
<li>The backend validates the data, adds the source tag and calls the CRM REST API (amoCRM API v4 or Bitrix24 <code>crm.lead.add</code>) with a webhook or OAuth token.</li>
<li>Store the CRM response id, so retries do not create duplicates (idempotency key = request id).</li>
<li>If the CRM is unavailable, queue the request and retry; notify a manager in Telegram meanwhile.</li>
</ul>
<pre><code class="language-json">{
  "name": "Anna",
  "contact": "@anna_tg",
  "source": "bot",
  "comment": "Needs an online booking site",
  "request_id": "b-10231"
}
</code></pre>
<h2>4. Limits</h2>
<p>Capabilities depend on your CRM plan and settings. Complex scenarios (custom pipelines, two-way sync of all fields) are better discussed separately. The CRM subscription itself is paid by you.</p>
<h2>About us</h2>
<p>We are the fresite team (fresite.ru): we build websites, Telegram bots, CRM integrations and other tools for small businesses in Russia. Development costs 0 RUB; only support is paid, from 6,900 RUB/month. We host projects on our own servers, so you don't need to buy hosting. Send a request: <a href="https://fresite.ru/?utm_source=hashnode.com&amp;utm_medium=post">https://fresite.ru/?utm_source=hashnode.com&amp;utm_medium=post</a> (free, no obligation).</p>
]]></content:encoded></item></channel></rss>