PipedreamHQ/pipedream

[ACTION] Linkedin fetch historic posts of authenticated user

Open

#16921 opened on Jun 2, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)JavaScript (7,438 stars) (5,305 forks)batch import
actionblocked-on-limited-apienhancementgood first issuehelp wanted

Description

Is there a specific app this action is for?

Please provide a link to the relevant API docs for the specific service / operation.

Regarding mcp server https://github.com/PipedreamHQ/pipedream/tree/master/components/linkedin/actions, Would it be possible to expand the 'Linkedin' MCP server to also be able to fetch the posts of the authenticated user? In this way, when a user automates his posts, we can make sure the writing is done in the style of the user.

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
apibackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Familiarity with Pipedream componentsUnderstanding of LinkedIn API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue requests a new action to fetch historic LinkedIn posts for the authenticated user. First, examine existing LinkedIn actions in the repository at https://github.com/PipedreamHQ/pipedream/tree/master/components/linkedin/actions for structure and patterns. Then, review LinkedIn's API documentation for retrieving user posts, focusing on the `/rest/posts` endpoint or similar. Consider how the MCP server integrates with the OAuth flow and user authentication. The issue has one assignee and may already be in progress; check for any linked PRs or comments for clarification.