Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector improvement: Pipedrive - deal change history

Completed
Alexander Novikov User

Hello there! 

We tried pipedrive connector and came to conclusion that the Fivetran implementation is missing one critical piece of data available via API of pipedrive. 

Pipedrive as a tool has in its core 'deals' object and bring value through allowing users to change the state of the deals. It makes both 'deals' and 'deal changes' crucial for analysis. 

Fivetran connector replicates deal table and also allows tracking of the changes using 'History' feature since the moment of the integration. Such implementation could have been ok if pipedrive didn't allow to fetch the history of deal changes. But pipedrive allows and it is strange that these data is not used by Fivetran.

Here is an example of implementation on github: https://github.com/singer-io/tap-pipedrive/blob/master/tap_pipedrive/streams/dealflow.py

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Ray User

    Hi Alexander & Pierre,

    Thanks for raising this issue! You're correct that our original implementation of the deal_history table was based on point-in-time syncs of the deals object. Your feedback has been noted, and as of earlier this month, we have updated the Pipedrive connector to make use of the aforementioned Deal Flow endpoint to provide a more complete & incremental history to the deal_history table. 

    With this new approach, your DEAL_HISTORY table will:

    • Support Fivetran History Mode with the addition of the _fivetran_active, _fivetran_start, and _fivetran_end columns to help you identify exactly when a version of the deal was current.
    • Contain historical data reconstructed from the Deal Flow endpoint. Rather than providing that data in an audit format, we will provide the full record.
    • Contain incremental updates based on webhooks.
    • Support deletes using webhooks.

    If you haven't already done so, updating to the improved deal_history table will require first dropping the existing deal_history table, then syncing it again. All Pipedrive connections will automatically have the improved deal_history table.

    All the best,

    Ray Harris

    Product Manager, Sales & Customer Success Analytics
  • Pierre de Poulpiquet User

    https://fivetran.com/docs/applications/pipedrive

     

    The DEAL_HISTORY table seems to sync what you need, doesn't it? (I think it was added after your Feature request).

  • Alexander Novikov User

    Hey Pierre de Poulpiquet! 
    Thanks for reply here, but the given table was there when I submitted my request. 

    DEAL_HISTORY table indeed has historical data, but it is done with workaround - via'History' feature of Fivetran (storing new states of the deals as new lines after syncs). You can see below the excerpt of Fivetran documentation on pipedrive connector.

    And my request is about fetching the holistic historical data from pipedrive as it is available there.