Good day everyone,
We just got notified that Channel API would be deprecated from 1st Feb. 2026. We are using it for our Whatsapp integration app so it will affect us heavily. We don’t see there’s any recommendation for alternatives from Pipedrive. Does anyone have suggestions on this topic?
We’re affected too — best options are checking Pipedrive Marketplace for WhatsApp connectors, or using middleware like Zapier/Make with WhatsApp Business API providers (Twilio, 360dialog, etc.) until Pipedrive announces an official alternative
The frustrating part here is that Pipedrive’s deprecation notice (https://developers.pipedrive.com/changelog/post/breaking-change-deprecation-of-channels-api) literally says “transition to an alternative solution” without actually naming one. And the Messaging App Extension tutorial still references the Channel API endpoints under the hood, so thats not a clean migration path either.
If your app is primarily about logging WhatsApp conversations on deals/contacts, one workaround is switching to the Notes API (POST /v1/notes) to attach message content directly to deals or persons. You lose the Messaging Inbox UI but at least the conversation history stays linked to the right records. For the actual WhatsApp send/receive you’d keep that on your own backend through the WhatsApp Business API and just push the data into Pipedrive via REST.
We’ve had to work around similar CRM API deprecations at Stacksync and the pattern is usually the same: move the messaging layer to your own infrastructure and use the CRM purely as the data store. Not ideal but more stable than depending on endpoints that keep getting pulled.