LINKEDIN_USER: LinkedIn User
A LinkedIn user profile with name, connections, location, current position, and work experience history.
Default definition. This article describes the default
LINKEDIN_USER definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches LINKEDIN_USER.Entity properties
| Property | Value |
|---|---|
| Entity code | LINKEDIN_USER |
| Display name | LinkedIn User |
| Plural | LinkedIn Users |
| Level | 100000 |
Use cases
LinkedIn data entity for user profiles. General panel has two column sections: left (25% width) with user info (name, LinkedIn URL, connections), location (city, country), and current job (position, company); right (100% width) with a relatedlist of LINKEDIN_EXPERIENCE records via SUB|LINKEDIN_USER comboKey. Clickable experience records show ref, name, company, start/end dates.
Fields
User
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
input_url | text (URL) | LinkedIn link | |
connections | text | Connections |
Location
| Field | Type | Required | Notes |
|---|---|---|---|
city | text | City | |
country_code | text | Country |
Job
| Field | Type | Required | Notes |
|---|---|---|---|
position | text | Position | |
current_company_name | text | Company |
Relationships
- Related lists:
LINKEDIN_EXPERIENCE(formatSUB|LINKEDIN_USER).
Creating a LinkedIn User via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "LINKEDIN_USER",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"input_url": "https://example.com",
"connections": "Example",
"city": "Example"
}Listing LinkedIn Users records
# All linkedin users in your tenant
GET /v1/entities/LINKEDIN_USER/SUB