Pipedrive Developer Platform update: App panels got interactive!

Priit Parmann
Priit Parmann Pipedrive Team Posts: 43 PIPEDRIVE TEAM
5 Likes Photogenic First Anniversary First Comment
edited July 2022 in What's New #1

Hi everyone,

We’ve heard both from app creators and our customers that the app panels are too static and that it’s not straightforward to invoke actions to create content for the panels from there. Other pain points were the lack of object and field-specific actions and static panel error state. 

Our latest updates to app extensions aim to address these shortcomings and enable you to provide a better experience to our mutual users.

What changed?

1. Main app action visible on the panel

We brought global app actions closer to users by displaying them straight on the app panel. It’s possible to have one main action which is always visible while the other actions are accessible from a drop-down right next to it. As one app action is shown on the panel by default, make sure it’s the right one for your app! Read more in the docs

Global actions

2. Object-specific actions

Actions can now be defined for the objects shown in the panel (if it’s a multiple-object panel). They should apply to one specific object, as opposed to global app actions, which are broader in nature. For example, a car delivery management app could show orders linked to a deal in the panel and in this case, an object action could be “Cancel order”. Read more

Object actions

3. Field-specific actions

Actions can also be defined for individual fields in the panel. They should be connected to one specific field, mostly for updating or viewing more information about it. Continuing with the previous example, field actions could be “Change manufacturer” and “Edit note”.

Both object and field actions can be either embedded (opens up a modal in Pipedrive) or basic (opens up a new tab, directing to your product) actions. Read more


4. Interactive error state

Previously, the app panel showed just one generic error message when a non-400 HTTP response was received for the panel request. Now, you can define the message and call-to-action button to show users based on the HTTP response status code. For example, when a paid subscription for the installed app has expired you can let the user know about it and prompt them to renew the subscription. Read more


What are the next steps?

  • For some real-life inspiration and examples, try out our Trello Marketplace app
  • Think through the use cases for your app in the context of these updates - can your app’s flows be improved in any way?
  • Have a look at the documentation for instructions on how to apply these changes

If you have feedback, questions or would like further information, please shoot me an email or schedule a quick call.

Priit Parmann
Product Manager

This discussion has been closed.