Connect Pipedrive and Telegram
Start a client’s workflow in Pipedrive and act in Telegram, or the other way round, on the client’s own accounts.
Each app by itself: Pipedrive integration and Telegram integration, with how to connect it, its scopes and its limits.
What the pair is used for
- An owner who runs the day from Telegram can get a message in a chat, group or channel the bot is in each time a Pipedrive deal is won, with its title, value and currency.
- Scheduled calls and meetings can post their subject, type, due date and duration to the same chat within seconds of being added.
- A message sent to the client’s Telegram bot can open a Pipedrive deal.
Every way Pipedrive and Telegram join
A workflow starts from a trigger in one app and runs a step in the other, on the client’s accounts. Where the library has a starter for it, it installs that pairing into a client switched off; any other pairing is two steps on the canvas.
From Pipedrive to Telegram
| When this happens in Pipedrive | This runs in Telegram | How fast | Starter |
|---|---|---|---|
| A deal moves to a stage | Send a message | Within seconds | Install the starter |
| A deal moves to a stage | Send a photo | Within seconds | Two steps on the canvas |
| A deal moves to a stage | Send a file | Within seconds | Two steps on the canvas |
| A deal is won | Send a message | Within seconds | Install the starter |
| A deal is won | Send a photo | Within seconds | Two steps on the canvas |
| A deal is won | Send a file | Within seconds | Two steps on the canvas |
| A new deal is created | Send a message | Within seconds | Install the starter |
| A new deal is created | Send a photo | Within seconds | Two steps on the canvas |
| A new deal is created | Send a file | Within seconds | Two steps on the canvas |
| A new contact is added | Send a message | Within seconds | Install the starter |
| A new contact is added | Send a photo | Within seconds | Two steps on the canvas |
| A new contact is added | Send a file | Within seconds | Two steps on the canvas |
| An activity is scheduled | Send a message | Within seconds | Install the starter |
| An activity is scheduled | Send a photo | Within seconds | Two steps on the canvas |
| An activity is scheduled | Send a file | Within seconds | Two steps on the canvas |
From Telegram to Pipedrive
| When this happens in Telegram | This runs in Pipedrive | How fast | Starter |
|---|---|---|---|
| A message is sent to the bot | List people | Within seconds | Two steps on the canvas |
| A message is sent to the bot | Create a person | Within seconds | Two steps on the canvas |
| A message is sent to the bot | Update a person | Within seconds | Two steps on the canvas |
| A message is sent to the bot | Create a deal | Within seconds | Install the starter |
Set up the starter
Send a message in Telegram when an activity is scheduled in Pipedrive
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Pipedrive, for “An activity is scheduled”
- 3Connect the client’s Telegram, for “Send a message”
- 4Fill in Telegram: Chat ID (For example -1001234567890 or @channel)
- 5Switch it on. Within seconds: Pipedrive tells us as it happens.

What it produces
The Telegram step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- Chat ID
- [Telegram: Chat ID]
- Text
- An activity is scheduled in Pipedrive. Subject: Emma Collins Type (call, meeting…): new Due date: 2026-10-21T09:05:00Z Due time: 240 Duration: 240
Setup notes for this pair
- The deal made from a Telegram message is titled with the chat’s title, such as a group’s name. Map the message text into the title if each message is a separate enquiry.
- Only one workflow can listen to a bot. If the client’s bot already starts another workflow, the deal starter needs a second bot, while the Pipedrive notices can post through either.
Field mapping, starter by starter
Each value a starter’s step is given, and where it comes from. Words in brackets are filled in when it runs; change any of it after installing.
Send a message for scheduled activities
Send a message in Telegram when an activity is scheduled in Pipedrive
| Telegram value | Filled from |
|---|---|
| Chat ID | [Telegram: Chat ID] |
| Text | An activity is scheduled in Pipedrive. Subject: [the activity’s subject, from Pipedrive] Type (call, meeting…): [the activity’s type, from Pipedrive] Due date: [the activity’s due date, from Pipedrive] Due time: [the activity’s value, from Pipedrive] Duration: [the activity’s value, from Pipedrive] |
Send a message for new deals
Send a message in Telegram when a new deal is created in Pipedrive
| Telegram value | Filled from |
|---|---|
| Chat ID | [Telegram: Chat ID] |
| Text | A new deal is created in Pipedrive. Deal: [the deal’s title, from Pipedrive] Value: [the deal’s value, from Pipedrive] Currency: [the deal’s currency, from Pipedrive] Status (open, won, lost): [the deal’s status, from Pipedrive] Stage ID: [the deal’s stage id, from Pipedrive] |
Send a message for deal stage moves
Send a message in Telegram when a deal moves to a stage in Pipedrive
| Telegram value | Filled from |
|---|---|
| Chat ID | [Telegram: Chat ID] |
| Text | A deal moves to a stage in Pipedrive. Deal: [the deal’s title, from Pipedrive] Value: [the deal’s value, from Pipedrive] Currency: [the deal’s currency, from Pipedrive] Status (open, won, lost): [the deal’s status, from Pipedrive] Stage ID: [the deal’s stage id, from Pipedrive] |
Send a message for won deals
Send a message in Telegram when a deal is won in Pipedrive
| Telegram value | Filled from |
|---|---|
| Chat ID | [Telegram: Chat ID] |
| Text | A deal is won in Pipedrive. Deal: [the deal’s title, from Pipedrive] Value: [the deal’s value, from Pipedrive] Currency: [the deal’s currency, from Pipedrive] Status (open, won, lost): [the deal’s status, from Pipedrive] Stage ID: [the deal’s stage id, from Pipedrive] |
Send a message for new contacts
Send a message in Telegram when a new contact is added in Pipedrive
| Telegram value | Filled from |
|---|---|
| Chat ID | [Telegram: Chat ID] |
| Text | A new contact is added in Pipedrive. Name: [the contact’s name, from Pipedrive] Organisation ID: [the contact’s org id, from Pipedrive] Owner ID: [the contact’s owner id, from Pipedrive] Label: [the contact’s label, from Pipedrive] Added at: [the contact’s add time, from Pipedrive] |
Create a deal for bot messages
Create a deal in Pipedrive when a message is sent to the bot in Telegram
| Pipedrive value | Filled from |
|---|---|
| Title | [the chat’s title, from Telegram] |
Pipedrive and Telegram and their logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.