Your problem
My problem is: I got this notice from Pipedrive this week.
After searching in the source code, it appears we are, in fact, still using the /persons/find/ api endpoint (see findByEmail here)
Is there anyone working on updating the Pipedrive plugin to use the search endpoint instead of the find endpoint? I really don’t like the idea of 10% of my api calls failing in less than 2 weeks.
For anyone following this topic, Webmecanik is working on an entirely new Pipedrive sync plugin and hopes to have it done and released open source any moment now.
Does anyone have the Webmecanik plugin working with vanilla Mautic 4? @joeyk do you have it up and running?
I get the following error when trying to run the sync command (mautic:integrations:sync Pipedrive2):
[ERROR] Call to undefined method Mautic\IntegrationsBundle\Event\SyncEvent::getInputOptionsDAO()
I can’t find that function in Mautic source
@kuzmany@npracht Is there any help you can offer? I recall reading about a patch I need to apply.
We need to get up and running on this new plugin as our clients’ Pipedreive and Mautic instances are falling further and further out of sync as requests are failing.
Quick update - I got the sync to run by applying PR 11255 and then adding the following function (a duplicate of getInputOptions()) to app/bundles/IntegrationsBundle/Event/SyncEvent.php:
public function getInputOptionsDAO(): InputOptionsDAO
{
return $this->inputOptionsDAO;
}
I have fields syncing, but have not tested activities yet. I’d still appreciate some help pointing me in the right direction of any additional patch that should be correctly applied.
One more note: Out of the box, Pipedrive does not have the first and last name fields needed to sync with this plugin and you have to reach out to Pipedrive support to enable them if you have not done so already.
Simply start a support chat and ask, “Could you please enable first and last name default fields?” and they will happily do so.