Pipedrive - deal stage updated trigger

(Szymon) #1

Hi,

I’m trying to add some automation to Pipedrive by adding new tasks whenever a deal stage is updated. I can create a trigger easily, but the trigger itself is bound to the stage, so if I want to automate 5 stages (and I have many more), I have to build 5 separate triggers. Is there any way to create an universal, catch-all-deal-stages trigger (e.g. using webhooks)?

Cheers,
Szymon

(Kellsey Shaw) #2

Hi there,

PipeDrive has Push Notifications that would allow you to send a webhook to Flow XO rather than us looking for updates. That would allow you to trigger the flow on various stages. :thumbsup:

1 Like
(Szymon) #3

cool, that’s what I thought, thanks!

(Szymon) #4

Hi,

thanks, that’s what we’ll do.

One more question regarding Pipedrive, quite crucial to our integration:
You mention that “We support a maximum of 85 custom fields.” -> are you going to raise that limit in the foreseeable future? We’re already above that number and that hurts our ability to handle our automation using Flow XO… Sorting the fields won’t help, we’re holding crucial customer data there and we need all of it.

(Kellsey Shaw) #5

Hi,

We don’t have any plans to increase the limit currently sorry.

(Szymon) #6

Do you imagine any way that I could work around this?

(Kellsey Shaw) #7

If the Push notification sends your fields, the field limit wouldn’t be an issue anymore as the restriction only applies to the PipeDrive integration and not the webhooks service that would receive a push notification :slight_smile:

You’d have to double check with PipeDrive to see what’s sent with the Push Notification

(Szymon) #8

Ok, so that’s a hope! I’m sure that all custom fields are sent through the Push Notification, I checked that already.

What about the other end - when I create a new Pipedrive Person through Flow XO - does the 85 field limit exist on this end? (i.e. will I be able to assign values to e.g. 100 fields that I have received via webhooks?)

(Kellsey Shaw) #9

Hi,

This field limit does apply to adding a person as well. The field limit is across the board on all PipeDrive methods in our integration. :slight_frown: