How to Connect Telegram to HubSpot (2026 Guide)

Connecting Telegram to HubSpot can mean four very different things: answering customer chats in Help Desk, messaging a person from their Contact record, running a shared Telegram group from a Deal or Project, or sending messages automatically from workflows. A useful integration should cover the whole conversation - not just fire a one-way notification and disappear.

This guide uses Resonate's Telegram for HubSpot as the worked example because it supports all four patterns in one app. If you only need a single alert in a channel, a generic webhook tool may be enough. If you want Telegram conversations attached to CRM records and able to drive HubSpot automation, follow the setup below.

What you can connect

The distinction matters. Help Desk and CRM-card messaging use a channel-connected Support bot so inbound and outbound messages can remain part of the same HubSpot thread. An outbound-only setup is suited to contact workflow actions; it does not create the linked Inbox threads used by the Contact and Telegram Group cards.

Before you start

You need four things:

1. A HubSpot admin who can install Marketplace apps. Connecting a custom channel to Help Desk requires the appropriate HubSpot permissions. HubSpot's current documentation lists custom channels for eligible Sales Hub or Service Hub Professional and Enterprise accounts.
2. A Telegram bot. Create one by messaging @BotFather, running /newbot, and following the prompts. Telegram will return a bot token. Treat that token like a password: anyone who has it controls the bot.
3. A decision about the bot's role. Choose Support when you want Inbox, Help Desk, Contact-card, or group-thread behavior. Choose outbound-only when you only need supported contact workflow sends.
4. A real Contact and, if you plan to use groups, a test Deal or Project. The app includes an action tester, but the safest launch check is still an end-to-end message using the same records your workflows will enroll.

One Telegram rule shapes the whole setup: a bot cannot start a private conversation with a person. The person must open the bot and tap Start or message it first. That is a Telegram platform rule, not a HubSpot limitation, and it makes this an opt-in channel rather than a cold-messaging tool.

Step 1: install the app and connect HubSpot

Open the Marketplace listing, install the app, and authorize the HubSpot portal you want to use. In the Resonate dashboard:

1. Connect HubSpot through OAuth.
2. Add the bot token you received from BotFather.
3. Give the bot a recognizable name and choose Support or Outbound only.
4. Edit the welcome message so contacts understand who is messaging them and what tapping Start will do.

If you operate several brands, you can connect multiple bots and route each one to its own inbox or use case. Keep the bot names and welcome messages specific; a generic bot called “Notifications” is difficult for both customers and admins to recognize later.

Step 2: use Telegram as a channel in HubSpot Help Desk

HubSpot's custom channels framework is designed to bridge an external messaging service into the Conversations Inbox or Help Desk. Telegram for HubSpot uses that channel layer, so a conversation behaves like a support thread rather than a copied activity note.

After you add a Support bot:

1. In HubSpot, go to Settings → Inbox & Help Desk → Help Desk → Channels.
2. Choose Connect a channel, then select the Telegram app.
3. Select the target inbox, ticket pipeline, stage, priority, and routing rules.
4. Send a message to the bot from a test Telegram account.
5. Open the new thread in Help Desk and reply from HubSpot.

The customer receives that reply in Telegram. Their next message returns to the same thread. The first inbound chat can match an existing Contact or create one, and the thread can create a ticket with the pipeline and assignment rules you configured.

Because Telegram is connected as a channel, agents keep the normal Help Desk context around the conversation:

• contact and ticket properties;
• assignment, routing, SLAs, and ticket status;
• snippets, knowledge-base articles, meeting links, and AI-assisted replies;
• photos, documents, video, and voice notes where the channel supports them;
• one HubSpot history instead of a separate Telegram inbox that nobody else can see.

HubSpot documents the underlying setup in Connect custom channels to Help Desk. An assigned seat may be required for advanced routing and Help Desk features.

Step 3: send Telegram messages from Contact records

For sales and customer-success teams, the fastest path is often the Telegram card on the Contact record. It shows whether the person has started the bot, provides a personal invite link and QR code, displays recent history, and includes a composer for a manual message.

The setup is deliberately contact-specific:

1. Add the Telegram card to the Contact record view through HubSpot's record customization tools.
2. If the contact is not linked, share the personal invite URL or QR code generated on that record.
3. The contact opens the link and starts the bot. That action binds the Telegram chat to the correct HubSpot Contact.
4. Write from the card. The message is delivered through Telegram and remains part of the linked HubSpot conversation.

You do not paste chat IDs into CRM properties. The app resolves the linked Telegram conversation from the Contact record. If the person has never started this bot, the app cannot send the first private message; use the invite link in an opted-in email, form confirmation, portal, or onboarding flow.

Step 4: create Telegram groups from Deals and Projects

One-to-one chat is not enough for a complex sale or implementation. A Telegram group can become a shared deal room: the customer, account owner, implementation lead, and other stakeholders stay in one chat while the CRM record remains the operational source of truth.

From the Telegram Group card on a Deal or Project record, you can create a group or link an existing one, see its status, and send a message without leaving HubSpot. The same card can be added to Company, Ticket, and Contact views.

Typical uses include:

• a Deal group for quote changes, security questions, and close-plan updates;
• a Project group for onboarding milestones, launch approvals, and handoffs;
• a Ticket group for an incident that involves the customer and several specialists;
• a Company group for an ongoing account or partner relationship.

The group can also receive automatic workflow messages. For example, a Deal workflow can post when legal approves a contract, and a Project workflow can announce that the launch checklist moved to the next stage.

For full two-way group capture, disable Group Privacy for the bot in BotFather before launch. With privacy mode enabled, Telegram limits which group messages a bot can see. Projects must also be activated in HubSpot, and the app needs permission to access them.

Step 5: send Telegram messages automatically with workflows

The integration publishes five workflow actions. Three are contact-only customer actions, one sends to a CRM-linked group, and one is reserved for employees.

All message fields can use HubSpot data tokens, so a workflow can include the contact name, appointment time, Deal amount, Project status, owner, or any other available property. The actions resolve the linked chat or group; the workflow builder does not need a Telegram chat ID.

Customer automation examples

• Send an order update when fulfillment status changes.
• Ask a lead whether they want pricing, a demo, or support.
• Confirm an appointment and offer a reschedule path.
• Send a contract, ticket, invoice, or product image.
• Post a stage change into a Deal or Project group.

Employee notification examples

The internal action is separate on purpose. It can notify a selected teammate, derive the recipient from the enrolled record's owner, send to an internal Telegram group, or combine recipients - up to ten per alert. Customers never receive these messages.

Useful triggers include:

• a high-value Deal is created or changes stage;
• a new lead needs immediate assignment;
• a Ticket approaches an SLA deadline;
• an important customer submits a low satisfaction score;
• a payment fails or a renewal enters a risk stage.

This separation prevents a common automation mistake: reusing one notification action for both internal and external audiences and eventually sending operational notes to a customer.

The key feature: wait for a response inside a workflow

Most messaging actions are fire-and-forget. Send Telegram message with buttons changes the pattern: it sends up to three inline buttons and pauses that Contact's workflow enrollment for up to 24 hours.

When the person taps a button, the app returns the button number, label, and value to HubSpot. The same enrollment resumes, and the next branch can use that action output immediately. If no button is tapped before the window closes, the action returns a no-response outcome instead of leaving the Contact stuck forever.

By chaining button messages, branches, property updates, tasks, tickets, and follow-up messages, you can build a complete button-driven Telegram bot inside HubSpot's workflow editor. Qualification, appointment management, onboarding checklists, renewal choices, and support triage can all live in the same automation engine as the rest of your CRM.

The qualifier is important: this action waits for an inline button tap, not arbitrary free text. It is a guided decision bot, not an open-ended AI chatbot. Each step can offer up to three choices, and you can chain additional steps when a flow needs more depth. HubSpot supports branches based on a previous action output, which is how the selected Telegram response becomes workflow logic.

Optional: connect a personal Telegram account

Not every customer conversation starts with a company bot. Founders, consultants, and account managers often work from personal Telegram DMs. The app can connect a Telegram Business account so those messages arrive in HubSpot and replies written in the inbox are delivered as that person rather than as the support bot.

This is useful for relationship-led sales and account management, but keep ownership clear. Decide whose account is connected, which inbox receives the chats, and how the team should handle a conversation when that person is unavailable.

Launch checklist

Before you turn on a production workflow, check the full path:

1. Opt-in: the test contact has started the correct bot.
2. Identity: the Telegram chat is linked to the intended HubSpot Contact.
3. Permissions: the app can access the records, inbox, and Projects you plan to use.
4. Cards: Telegram and Telegram Group cards are added to the correct record views.
5. Routing: a real inbound chat reaches the expected inbox, pipeline, and owner.
6. Customer action: a workflow message resolves tokens and reaches the contact.
7. Response: every button path works, including no response after the waiting window.
8. Internal action: the employee alert reaches only the intended teammate or group.
9. Group privacy: BotFather privacy settings allow the level of group sync you expect.
10. Failures: the workflow has a visible fallback for an unlinked contact, missing group, or inaccessible file URL.

The built-in action tester is useful for checking message configuration, timing, and raw outputs against a real Contact or Deal. Test the 24-hour wait/resume path in an actual workflow as well; the tester sends button messages but does not replace a complete enrollment test.

Which connection should you start with?

• Start with Help Desk when Telegram is primarily a customer-support channel.
• Start with the Contact card when sales or customer success needs occasional one-to-one messages.
• Start with Deal and Project groups when customers collaborate with several people over a longer lifecycle.
• Start with workflow actions when the main goal is automation, employee alerts, or guided button-driven bots.

You can add the other capabilities later. They share the same HubSpot records and Telegram identities, so you do not need a separate integration for every use case. Review the full feature set on the Telegram for HubSpot app page.

Related reading

• Telegram and Notion actions in HubSpot workflows
• Free HubSpot workflow library
• How to route leads in HubSpot
• HubSpot integration services

Frequently asked questions