← Back to Skills Marketplace
13925
Downloads
47
Stars
0
Active Installs
20
Versions
Install in OpenClaw
/install linkedin-api
Description
LinkedIn API integration with managed OAuth. Share posts, manage profile, and access LinkedIn features. Use this skill when users want to share content on LinkedIn, get profile/organization information, or interact with LinkedIn's platform. Advertising features (campaigns, ad accounts) require additional OAuth scopes — verify granted scopes before use. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a LinkedIn connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a LinkedIn action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with LinkedIn examples; they add no LinkedIn capability - LinkedIn is not an event source, a trigger cannot read LinkedIn data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to let Maton access LinkedIn on your behalf. Confirm the exact account, scopes, post or ad payload, budget, media file, automation schedule, and destination URL before approving any write or persistent automation, and revoke unused connections when finished.
Capability Assessment
Credentials
The skill needs network access, a Maton account, OAuth connection state, and sometimes direct LinkedIn pre-signed media uploads; those are disclosed and scoped, but they can expose business or personal LinkedIn data if misused.
Install Mechanism
Installation uses pinned Maton CLI and SDK packages via npm, Homebrew, or pip; this is expected for the integration, though users should only install from the documented Maton sources and review upgrades deliberately.
Instruction Scope
The skill repeatedly limits default behavior to read/list calls, requires explicit user approval for writes, connection creation, deletion, hosted functions, trigger destinations, and local event execution, and treats third-party content as untrusted data.
Persistence & Privilege
OAuth tokens, hosted functions, triggers, and destinations can persist beyond one session, but the artifact clearly describes credential handling, approval requirements, network-policy limits, and cleanup expectations.
Purpose & Capability
The stated purpose is LinkedIn access for profile, posts, organizations, advertising, media uploads, and related automation; the documented API, OAuth, upload, function, and trigger capabilities fit that purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install linkedin-api - After installation, invoke the skill by name or use
/linkedin-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.7
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.6
- Removed the file skill-card.md.
- No changes to core functionality or documentation structure.
- Housekeeping update to remove unused sample files.
v1.2.5
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.4
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.3
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.2
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.10
- Updated LinkedIn API version requirement from `202506` to `202606` in all references and headers.
- Removed the sample file `skill-card.md` from the project.
v1.0.9
- Removed the skill-card.md file from the repository.
- Documentation updated: clarified that advertising features (campaigns, ad accounts) require additional OAuth scopes and users should verify their granted scopes before use.
- Enhanced security and permissions guidelines to include explicit multi-step user confirmation for write operations, especially for advertising calls that carry financial impact.
- Updated the description to reflect new requirements regarding advertising features and OAuth scopes.
v1.0.8
- Removed the redundant or outdated file: skill-card.md.
- No changes to the API, configuration, or skill usage.
- No user-facing feature or documentation changes.
v1.0.7
- Updated all LinkedIn API base URLs from `gateway.maton.ai` and `ctrl.maton.ai` to `api.maton.ai`.
- All code examples and connection management instructions now use the new `api.maton.ai` endpoints.
- Removed the LICENSE.txt file from the skill package.
- Improved and clarified instructions on specifying the correct LinkedIn connection, especially when multiple accounts are authorized.
- Added security and permissions section, emphasizing user approval for write operations.
v1.0.6
- No changes detected in this release.
- Version number incremented to 1.0.6.
v1.0.5
- No code or documentation changes detected in this version.
- Version number updated to 1.0.5.
v1.0.4
- No user-facing changes in this release.
- Version bump to 1.0.4 with no file modifications detected.
v1.0.3
- Updated LinkedIn API endpoints from `/v2/` to `/rest/` and revised documentation to match the current LinkedIn REST API.
- Changed required protocol/version header from `X-Restli-Protocol-Version: 2.0.0` to `LinkedIn-Version: 202506`.
- Updated example code and API references to use new REST endpoints and adjusted request/response formats.
- Revised image upload process and endpoints for compatibility with the LinkedIn REST API.
- Clarified media sharing, profile retrieval, and post creation documentation under latest API specifications.
v1.0.2
- Added explicit Clawdbot metadata, including required environment variable MATON_API_KEY.
- No changes to functionality or user-facing features.
v1.0.1
- No file changes were detected in this version.
- Documentation, API usage, and functionality remain unchanged from the previous release.
v1.0.0
Initial release of LinkedIn API integration with managed OAuth.
- Share posts, manage profiles, access organization info, run ad campaigns, and upload media to LinkedIn through a unified API gateway.
- Supports OAuth connection management via a dedicated control interface.
- Provides detailed examples for making authenticated requests and handling multiple connections.
- Includes guides for posting text, articles, and images to LinkedIn.
- Requires a valid Maton API key and network access for all operations.
Metadata
Frequently Asked Questions
What is LinkedIn?
LinkedIn API integration with managed OAuth. Share posts, manage profile, and access LinkedIn features. Use this skill when users want to share content on LinkedIn, get profile/organization information, or interact with LinkedIn's platform. Advertising features (campaigns, ad accounts) require additional OAuth scopes — verify granted scopes before use. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a LinkedIn connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a LinkedIn action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with LinkedIn examples; they add no LinkedIn capability - LinkedIn is not an event source, a trigger cannot read LinkedIn data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 13925 downloads so far.
How do I install LinkedIn?
Run "/install linkedin-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is LinkedIn free?
Yes, LinkedIn is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does LinkedIn support?
LinkedIn is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created LinkedIn?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.7.
More Skills