topic Re: Linkedin field for Contact in APIs & Integrations

Linkedin field for Contact

mmaddiona — Wed, 25 Jan 2023 14:51:32 GMT

The linkedin field for the Contact entity exists: "hs_linkedinid".

I can query it and see data:

Why I can't find the Linkedin field property in Settings/All properties for Contact Entity?

Re: Linkedin field for Contact

tominal — Wed, 25 Jan 2023 19:01:42 GMT

That's strange. I'll be following this thread to find out what happens. Have you tried contacting HubSpot support on your account?

Re: Linkedin field for Contact

mmaddiona — Thu, 26 Jan 2023 06:50:57 GMT

No, I didn't. But I have seen that field in the past.

Re: Linkedin field for Contact

tominal — Thu, 26 Jan 2023 18:03:51 GMT

Well let me know if you don't open a ticket because I will. That's strange.

Re: Linkedin field for Contact

mmaddiona — Fri, 27 Jan 2023 08:57:02 GMT

Ok please, you can proceed, keep me updated 😉

Thank you

Re: Linkedin field for Contact

Jaycee_Lewis — Fri, 27 Jan 2023 20:40:12 GMT

Hey, y'all 👋 I don't have the underling why here. Sorry, no magic. But I did a bit more digging using the Properties and Contact endpoints. Here's what I can contribute to the investigation so far:

This property is set as "hidden", but it is write-able. This is why it doesn't show up in the UI.
If it wasn't hidden in the UI it would live in the Contacts > Social Media Information group.
You can make a PATCH request to the Update a Contact endpoint and add a value:
curl --request PATCH \ --url https://api.hubapi.com/crm/v3/objects/contacts/901 \ --header 'authorization: Bearer YOUR_ACCESS_TOKEN' \ --header 'content-type: application/json' \ --data '{ "properties": { "hs_linkedinid": "BigBobBelcher" } }'HTTP 200 { "id": "901", "properties": { "createdate": "2022-11-03T21:42:31.255Z", "hs_created_by_user_id": "10233975", "hs_is_contact": "true", "hs_is_unworked": "true", "hs_linkedinid": "BigBobBelcher", "hs_object_id": "901", "hs_pipeline": "contacts-lifecycle-pipeline", "hs_updated_by_user_id": "10233975", "lastmodifieddate": "2023-01-27T19:09:21.226Z", "lifecyclestage": "lead", "notes_last_updated": "2023-01-27T17:49:48.590Z" }, "createdAt": "2022-11-03T21:42:31.255Z", "updatedAt": "2023-01-27T19:09:21.226Z", "archived": false }
Verified it updated using the Read endpoint:
Response
HTTP 200 { "id": "901", "properties": { "createdate": "2022-11-03T21:42:31.255Z", "hs_linkedinid": "BigBobBelcher", "hs_object_id": "901", "lastmodifieddate": "2023-01-27T19:09:21.226Z" }, "createdAt": "2022-11-03T21:42:31.255Z", "updatedAt": "2023-01-27T19:09:21.226Z", "archived": false }

Things the documentation doesn't tell us:

why this property is hidden is the UI
future plans for this property

Hey, @tominal please let us know if support provides any additional details.

Best,

Jaycee

Re: Linkedin field for Contact

mmaddiona — Sat, 28 Jan 2023 10:52:47 GMT

Thank you @Jaycee_Lewis, really helpful.
This is weird! 😄

Re: Linkedin field for Contact

tominal — Mon, 30 Jan 2023 20:30:43 GMT

Hey @Jaycee_Lewis and @mmaddiona,

I received a reply from support regarding this. @mmaddiona, are you sure you remember seeing this property on contact records? There are two native properties created on company records in regards to LinkedIn that you may be thinking about.

Either way, you will have to create a separate contact property to house your LinkedIn URLs.

Hope that helps!

Re: Linkedin field for Contact

mmaddiona — Tue, 31 Jan 2023 07:10:12 GMT

Probably I confused the Account LinkedIn property, with the Contact one. I always use these properties via API with Crono (https://crono.one) that we are developing.

It's weird that I have to create another property when there is this that is hidden.

Thank you for your support!