Pipedrive Shut Off Its Channels API. Here Is How to Text from Pipedrive Now
TL;DR
Pipedrive announced on 14 November 2025 that it was retiring its Channels API, and the endpoints went dark on 1 February 2026. Third-party messaging apps can no longer feed conversations into Pipedrive's Messaging inbox, and no replacement was named. Old conversations survive as Notes on the deal. Texting from Pipedrive now runs through Workflow Automations and webhooks, with replies written back as Notes.
On this page
What did Pipedrive shut off, and when?
Pipedrive retired its Channels API on 1 February 2026. It announced the change on 14 November 2025 to focus engineering on its next-generation CRM (Pipedrive developer changelog).
The Channels API was how third-party messaging apps plugged into Pipedrive's Messaging inbox through the Messaging app extension, launched in May 2022. Pipedrive named no replacement.
- POST /v1/channels, which registered a messaging channel
- POST /v1/channels/messages/receive, which pushed incoming messages into the inbox
- DELETE /v1/channels/{id} and the conversation delete endpoint
What survived the Pipedrive Channels API shutdown?
Pipedrive kept your history. Messages that were linked to deals or other records stay in your account as Notes, per the same changelog entry.
What did not survive is the live inbox. A messaging app can no longer register a channel or push new replies into Pipedrive's Messaging tab, so a texting workflow built on it stopped on 1 February.
How do you text leads from Pipedrive after the shutdown?
Texting from Pipedrive now runs outside the Messaging inbox. A Workflow Automation fires a webhook on a deal event, the messaging platform sends, and replies come back to the deal as Notes and Activities.
Developers on Pipedrive's community forum landed on the same pattern: keep sending on your own backend and attach message content to the deal through the Notes API.
| Channels API (before 1 Feb 2026) | Workflow Automations and webhooks (now) | |
|---|---|---|
| Where replies live | Pipedrive's Messaging inbox | Notes and Activities on the deal or person |
| What triggers a send | A rep in the inbox | A deal stage, activity or field change, or a rep |
| Status | Retired, endpoints removed | Supported Pipedrive features |
How does Blue Reacher send iMessage from Pipedrive?
Blue Reacher is one of the messaging platforms built on that pattern, with Pipedrive among its six native CRM integrations. Workflow Automations fire blue-bubble iMessages on deal stages, activities or field changes.
Replies write back to the deal as Notes or stage moves, delivery states post to the record, and STOP is suppressed automatically. Setup is done with you, so no team has to rebuild the Channels workflow.
Pricing is published: $249 per line per month, unlimited iMessages paced at 50 opted-in / 30 cold new contacts a day, and no A2P registration required. The full setup is on the Pipedrive integration page.
What should Pipedrive teams check first?
Pipedrive teams that relied on a Channels-based texting app should check three things before choosing a replacement.
- Find the automations that assumed replies landed in the Messaging inbox, and point them at Notes or Activities instead.
- Export the opt-out list from the old texting app before its access lapses; it is the one record you cannot rebuild.
- Ask any replacement where replies land in Pipedrive, in writing: a Note on the deal, an Activity, or nowhere.
Frequently asked questions
Did Pipedrive remove its messaging integrations?
Pipedrive retired the Channels API, the mechanism messaging apps used to feed the Messaging inbox, on 1 February 2026. It announced the change on 14 November 2025 and named no replacement. Existing conversation history stays in your account as Notes.
Can I still send texts from Pipedrive?
Yes, through Workflow Automations and webhooks rather than the Messaging inbox. A deal event triggers the send in your messaging platform, and replies come back to the deal as Notes and Activities.
What happened to my old Pipedrive message history?
Pipedrive kept it. Messages linked to deals or other records remain in your account as Notes, according to Pipedrive's developer changelog entry on the Channels API deprecation.
Does Blue Reacher work with Pipedrive?
Yes. Pipedrive is one of Blue Reacher's six native CRM integrations. Workflow Automations trigger iMessages on deal events, and replies, delivery states and opt-outs write back to the deal. Setup is done with you during onboarding.
Keep reading
More on crm integrations
Your Automation Tool Will Send That Message Twice
Every workflow tool worth using retries a failed step, and every one of them decides what failed by reading the response. A messaging platform that already sent your text and then timed out returning an answer looks exactly like one that never got the request. So the tool sends again, and your lead reads the same sentence twice in the same thread.
Four Things Vendors Call a CRM Integration
Every texting vendor has a page titled HubSpot Integration. Behind that title sit four different products with four different failure modes, and the one that decides whether your automations run at 2am is where the code lives. Read from six vendors' own pages on 8 September 2026.
The iMessage CRM Integration Guide: Triggers, Two-Way Sync, and Opt-Outs
An iMessage integration is three pipes: triggers going out, replies and delivery states coming back, and opt-outs mirrored everywhere. What each pipe needs, which CRM events to wire first, and where builds go wrong.
Put this on your pipeline
Blue Reacher runs outbound iMessage for B2B sales teams, from your CRM, with setup handled for you.
Book a demo