Question: API to send emails with tracking

Ted Youn
Ted Youn Community Driver Posts: 135
10 Comments Second Anniversary Photogenic Community Driver

Greetings,

I'm wondering whether Pipedrive provides an API to send emails with tracking.

(Some clients wants an automated email sending with tracking features.)

0
0 votes

· Last Updated -

Comments

  • Jason Prosnitz
    Jason Prosnitz Posts: 18
    edited February 2021 #2

    this is a great suggestion @Mike van der Valk 

    Frankly I’d love to see the API opened up for emails (so I could automate sending messages from other tools but via Pipedrive to track it both historically and with the opened/tracking flags), files/docs (namely being able to attach a pdf to an entity for example) and invoicing (which as I’ve said needs a lot of work as it stands, so after the team has built the feature out a bit more completely).

  • Mike van der Valk
    Mike van der Valk Posts: 4,381 PIPEDRIVE PRODUCT MANAGER
    2500 Comments Third Anniversary 25 Likes First Answer
    edited November 2020 #3

    Thanks @Ted Youn and @Jason Prosnitz for sharing this, I've passed it on to our team for potential updates in the future.

  • Mike van der Valk
    Mike van der Valk Posts: 4,381 PIPEDRIVE PRODUCT MANAGER
    2500 Comments Third Anniversary 25 Likes First Answer
    edited February 24 #4

    Hey @Ted Youn and @Jason Prosnitz the technical team got back to me. They mentioned that we're making some big changes on the technical side so API endpoints will change a lot in the coming weeks/months. It makes therefore sense not to release these API's publicly now but only when we've made those changes and improved our platform.

  • Jason Prosnitz
    Jason Prosnitz Posts: 18
    edited February 2021 #5

    Hey @Ted Youn and @Jason Prosnitz the technical team got back to me. They mentioned that we're making some big changes on the technical side so API endpoints will change a lot in the coming weeks/months. It makes therefore sense not to release these API's publicly now but only when we've made those changes and improved our platform.

    @mike Would love to see some of that information in "What's planned?" ;)  

  • Mike van der Valk
    Mike van der Valk Posts: 4,381 PIPEDRIVE PRODUCT MANAGER
    2500 Comments Third Anniversary 25 Likes First Answer
    edited December 2020 #6

    Hey @Ted Youn and @Jason Prosnitz the technical team got back to me. They mentioned that we're making some big changes on the technical side so API endpoints will change a lot in the coming weeks/months. It makes therefore sense not to release these API's publicly now but only when we've made those changes and improved our platform.

    There are still a lot of decisions to make on our end but we're looking at replacing the system that syncs our emails. At start not much will change for the user besides a more stable, quicker and reliable email service. After it's been replaced we can think about making endpoints public and improving the services in general.

  • Jason Prosnitz
    Jason Prosnitz Posts: 18
    edited February 2021 #7

    Hey @Ted Youn and @Jason Prosnitz the technical team got back to me. They mentioned that we're making some big changes on the technical side so API endpoints will change a lot in the coming weeks/months. It makes therefore sense not to release these API's publicly now but only when we've made those changes and improved our platform.

    Regardless - this is welcome news. My experience as a new user with the email syncing has certainly had it's peaks and valleys for sure. It's very finicky as it stands. Thanks!

  • Cedrick Ward
    Cedrick Ward Posts: 7
    edited December 2020 #8

    Hey @Ted Youn and @Jason Prosnitz the technical team got back to me. They mentioned that we're making some big changes on the technical side so API endpoints will change a lot in the coming weeks/months. It makes therefore sense not to release these API's publicly now but only when we've made those changes and improved our platform.

    I created my own post on this question. I suppose I should have looked first to find more information. Looking forward to new developments on this!