# LinkedIn Get Post

<!-- meta: type=linkedin-get-post; location=Social › LinkedIn; category=Step (action); platforms=Joomla and WordPress (where applicable) -->

## Overview

Fetches a LinkedIn post by URN or share ID (commentary, lifecycle state, author).

When the flow reaches this step, JOrchestrator executes **LinkedIn Get Post** against your linked site or an external integration, using the field values you set on **General** and **Design**. Downstream steps can read the output payload fields defined for this node.

## Why use this node

LinkedIn Get Post is a **action step** in the **Social › LinkedIn** group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add **LinkedIn Get Post** to a flow:

- Automate "LinkedIn Get Post" as part of a larger Joomla or WordPress workflow
- Replace manual linkedin work with a repeatable, logged flow step
- Chain with triggers, logic, and messaging nodes on the same canvas

## Example workflows

Common patterns on the canvas:

1. **Trigger or Webhook** → upstream steps → **LinkedIn Get Post** → **Send Email** or CMS update
2. **Scheduled trigger** → **LinkedIn Get Post** → **Debug** (while testing) → production action

## How to set it up

Post ID on the Design tab.

## Good to know

Requires r_organization_social or r_member_social on the access token.

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **General** | Canvas label and read-only node ID |
| **AI** | Optional assistant to help draft settings from plain language |
| **Design** | Node-specific configuration fields |

### System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `_nodeId` | Node ID | `node-id` | No | — | — |
| `_payloadFields` | Available Fields | `payload-panel` | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `postId` | Post ID | `payload-text` | **Yes** | — | {{linkedin_post.postId}} or urn:li:share:… |

### CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under **Node Configuration**, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

## Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as
`{{linkedin_get_post.success}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `success` | boolean | Whether the operation completed successfully. |
| `postId` | string | Text value from this node's output. |
| `text` | string | Text value from this node's output. |
| `lifecycleState` | string | Text value from this node's output. |
| `createdAt` | string | Text value from this node's output. |
| `author` | string | Text value from this node's output. |
| `message` | string | Human-readable status, error, or result summary. |

## Validation rules

- **Post ID** (`postId`) must be filled before the flow can be saved.

## Related nodes

Other steps in the same area of the palette:

- **LinkedIn Delete Post** (`linkedin-delete-post`) — Social › LinkedIn
- **LinkedIn List Posts** (`linkedin-list-posts`) — Social › LinkedIn
- **LinkedIn Organization Info** (`linkedin-organization-info`) — Social › LinkedIn
- **LinkedIn Post** (`linkedin-post`) — Social › LinkedIn