Integrate a messaging service directly into Pipedrive with our new Messaging app extension. To enable apps to do this, we’ve created a deep integration point with our Messaging inbox inside the Leads Inbox of Pipedrive.

By using the messaging extension, app users can send, view and delete messages right inside Pipedrive, whilst all of their communications are synced with the messaging service. Apps with messaging extension can also be shared company-wide.

The extension and its access to Messaging inbox go through a manifest-based connection and public API endpoints. This makes the extension controllable from the provider’s side (user action done in service), the user’s side (action done in Pipedrive, sent to messaging service) and the app’s side (action done by app to mimic service conditions in Pipedrive).

With this extension, we’ve added a couple of new things:

In Developer Documentation

You can find a complete overview of Messaging app extension, how to implement the manifest and custom error codes as well as troubleshooting.

In API Reference

We’ve added the Channels API with 4 new endpoints. The endpoints enable you to manage and interact with the channel’s conversations, participants and messages inside the Pipedrive Messaging inbox. Apps can call these endpoints to forward received messages and conversations from the messaging provider service to Pipedrive.

• POST /v1/channels
• POST /v1/channels/messages/receive
• DELETE /v1/channels/{id}
• DELETE /v1/channels/{channel-id}/conversations/{conversation-id}

In OAuth Scopes

We’ve added the Messengers integrations access scope, which is key to building the Messaging app extension. By enabling this scope for your app, users can now grant your app access to their data for connection building between messaging channels. This scope also covers all Channels API endpoints mentioned above.