Case Study: HubSpot x Telegram | Solved for Fibonacci

Inside Fibonacci: Turning Telegram Chats Into Sales Pipelines

Fibonacci Market is a crypto market-making and liquidity solutions company. They work with token founders and exchanges to stabilize token prices, manage order books, and keep liquidity flowing across markets.

For Fibonacci, Telegram is where business happens. Every investor chat, deal negotiation, and client update flows through it because in crypto, speed and trust matter more than anything else.

But as the team grew, so did the chaos. Deals moved forward on Telegram, yet none of those conversations lived inside their CRM. Sales leaders had no visibility into what was being discussed, who was engaged, or how close a deal was to closing. Reporting was incomplete, and managers had to rely on word-of-mouth updates.

If you’re growing, you need your Telegram to talk to your HubSpot so your business can finally make sense of what’s happening. And that’s exactly what we helped Fibonacci do.

What Led Fibonacci to HubSpot

For Fibonacci, Telegram was the backbone of every client relationship. But running a sales organization on a messaging app created a unique set of technical challenges that held them back.

No API-driven visibility into conversations

Group and 1:1 chats were happening constantly, but there was no native way to capture them in HubSpot. Messages were siloed inside Telegram, making it impossible to link them with deals or contacts.

Unstructured lifecycle mapping

Since conversations drove the deal cycle, there was no structured way to push a deal from “First Contact” to “Agreement Signed.” Everything was buried in chat threads, with no backend logic to sync with a pipeline.

Data and reporting blind spots

Telegram doesn’t provide out-of-the-box reporting for business use. Managers had no metadata (timestamps, user IDs, status changes) that could be pulled into HubSpot. This made forecasting and team accountability technically unworkable.

Manual, error-prone workarounds

Reps copied messages into spreadsheets or notes, but this was not scalable. The absence of an automated sync meant data was often incomplete or outdated by the time it reached HubSpot.

Scaling complexity

As Fibonacci took on multiple token projects, these gaps multiplied. Without automation, every new group or client added exponential overhead to an already fragile setup.

Fibonacci didn’t just need a CRM migration. They needed a technical bridge between Telegram and HubSpot that could capture, structure, and report on every conversation at scale.

How We Built It

The goal was to make Telegram and HubSpot work as one system. We used Firebase Cloud Functions, Firestore, GramJS, and a React-based HubSpot UI Extension to create a real-time sync between the two platforms.

1. Build a Secure Login Mechanism

We started by allowing users to log into Telegram directly from HubSpot.

• Used GramJS (MTProto API) to initiate OTP login.
  
  
• Built /sendCode and /telegramLogin Firebase endpoints to verify OTP and 2FA.
  
  
• Stored sessions securely in Firestore (telegramUsers.sessions).
  
  

Each rep could connect their Telegram once and have their chats auto-synced under their HubSpot account, eliminating the need to switch apps.

2. Sync Chats Automatically

A scheduled Firebase Function retrieved active sessions, fetched group and personal chats from Telegram, and pushed them into HubSpot.

• Created custom objects:
  
  
  • Group Chat (group_chat_id, name, participants, type)
    
    
  • Messages (message_id, text, sender, timestamp)
    
    
• Linked objects to Contacts and Deals using HubSpot associations.
  
  

Every 1:1 and group chat now lived inside HubSpot, tied to the right contact and deal record.

3. Build a Chat Interface Inside HubSpot

Using the HubSpot CRM UI Extension SDK, we built a React chat-box component to send and receive Telegram messages.

• /telegram/getMessages → fetch history
  
  
• /telegram/sendMessage → post replies
  
  
• Real-time updates synced both ways via Firebase Functions
  
  

Reps could talk to clients without leaving HubSpot, while every message got logged automatically.

4. Define the Pipeline and Ownership Logic

We implemented Fibonacci’s internal MM pipeline inside HubSpot with clear stages:
Unsorted Leads → First Contact → Negotiation → Offer Sent → Agreement Signed → Payment Received

Each message was tagged by stage, contact, and owner (matched by Telegram phone number).

The sales team could now track deal progress end to end and report on where each conversation stood.

5. Ensure Security and Reporting Integrity

• Encrypted Telegram sessions in Firestore
  
  
• Stored HubSpot Private App token in Firebase environment variables
  
  
• Used HTTPS for all communication
  
  
• Pre-computed analytics for message count, response times, and stage velocity
  
  

The integration wasn’t just functional. It was safe, scalable, and built for long-term insight.

From Invisible to Visible: The Results

In just two months, Fibonacci turned an untrackable Telegram sales process into a fully visible HubSpot pipeline.

• 100% visibility into every 1:1 and group chat inside HubSpot
  
  
• Faster deal cycles as reps moved directly from chats to signed agreements
  
  
• Centralized pipeline tracking every stage from first contact to payment
  
  
• Zero manual updates with messages syncing automatically
  
  
• Accurate reporting with real data on deals, engagement, and performance
  
  

Telegram stayed where the sales happened. HubSpot became where the results were tracked.

Want your team to close deals as fast as they chat?

Book a call with us for a free audit!