LinkedIn field should be default field to get the same API ID for all clients.

Martin Pecha_2338
Martin Pecha_2338 Posts: 175
100 Comments Second Anniversary 5 Up Votes 5 Likes
edited July 2022 in Ideas and Product Feedback #1

Hi, I have a suggestion, that there should be a default field named LinkedIn in Pipedrive. I sometimes automate processes via API on behalf of other Pipedrive users from different companies and it bothers me, that there is no default LinkedIn field. I have to manually find the custom field and it creates an issue when I automate processes for other people.

Tagged:
0
Up
0 votes

· Last Updated -

Comments

  • Mike van der Valk
    Mike van der Valk Posts: 4,052
    2500 Comments 100 Likes Third Anniversary 5 Answers
    PRODUCT MANAGER
    edited February 2022 #2

    Thanks for sharing @Martin Pecha I've not heard this request before but I've added the "feedback & feature suggestion" tag to your post so our team sees it.

    We do want to avoid having too many default fields that are not used by all our users. Not all business and Pipedrive users use LinkedIn where they do need things like, name, phone, email, address, etc.. 

    Nonetheless, I'll let our team take a look perhaps they don't agree with me 😄

  • Martin Pecha_2338
    Martin Pecha_2338 Posts: 175
    100 Comments Second Anniversary 5 Up Votes 5 Likes
    edited September 2020 #3
    Mike van der Valk said:

    Thanks for sharing @Martin Pecha I've not heard this request before but I've added the "feedback & feature suggestion" tag to your post so our team sees it.

    We do want to avoid having too many default fields that are not used by all our users. Not all business and Pipedrive users use LinkedIn where they do need things like, name, phone, email, address, etc.. 

    Nonetheless, I'll let our team take a look perhaps they don't agree with me 😄

    thanks - I would only want to have default field name "LinkedIn" so I can find it via API and do not have to map custom fields "LinkedIn" of people as everyone has different custom API key to this field

  • Mike van der Valk
    Mike van der Valk Posts: 4,052
    2500 Comments 100 Likes Third Anniversary 5 Answers
    PRODUCT MANAGER
    edited September 2020 #4
    Mike van der Valk said:

    Thanks for sharing @Martin Pecha I've not heard this request before but I've added the "feedback & feature suggestion" tag to your post so our team sees it.

    We do want to avoid having too many default fields that are not used by all our users. Not all business and Pipedrive users use LinkedIn where they do need things like, name, phone, email, address, etc.. 

    Nonetheless, I'll let our team take a look perhaps they don't agree with me 😄

    Gotcha, what I was trying to say is that if we do that all our users would get this field that they potentially don't need. So the team will need to look into if this is a common enough field to make default to not overcloud the accounts of other users.

  • Martin Pecha_2338
    Martin Pecha_2338 Posts: 175
    100 Comments Second Anniversary 5 Up Votes 5 Likes
    edited September 2020 #5
    Mike van der Valk said:

    Thanks for sharing @Martin Pecha I've not heard this request before but I've added the "feedback & feature suggestion" tag to your post so our team sees it.

    We do want to avoid having too many default fields that are not used by all our users. Not all business and Pipedrive users use LinkedIn where they do need things like, name, phone, email, address, etc.. 

    Nonetheless, I'll let our team take a look perhaps they don't agree with me 😄

    got it, totally understandable

Categories