Linked API icon

Linked API

Control your LinkedIn accounts and retrieve real-time data.

Actions27

Overview

The node "Linked API" enables interaction with LinkedIn accounts to retrieve real-time data and perform various LinkedIn-related operations. Specifically, the Fetch Post operation allows users to fetch detailed information about a specific LinkedIn post by providing its URL. This is useful for scenarios such as monitoring engagement on particular posts, extracting content or metadata for analysis, or integrating LinkedIn post data into other workflows.

Practical examples:

  • Automatically retrieving details of a LinkedIn post shared in a marketing campaign to analyze its performance.
  • Fetching post content and comments to display within a custom dashboard.
  • Archiving LinkedIn post data for compliance or record-keeping purposes.

Properties

Name Meaning
Webhook URL The URL where the response from the LinkedIn API will be sent via webhook after execution. It must be a valid endpoint capable of receiving POST requests. Example: https://n8n.your-domain.com/webhook-test/your-webhook-ID
Post URL The full LinkedIn URL of the post you want to fetch information about. Example: https://www.linkedin.com/posts/username_activity

Output

The node outputs JSON data containing detailed information about the specified LinkedIn post. This typically includes post content, author details, timestamps, engagement metrics (likes, comments), and possibly media attachments if present.

If the node supports binary data output (not explicitly shown here), it would likely relate to media files attached to the post (images, videos). In that case, the binary output would contain the raw media data fetched from LinkedIn.

Dependencies

  • Requires an active connection to the LinkedIn API through an API key credential configured in n8n.
  • The node sends requests to the external service at https://api.linkedapi.io/automation.
  • A valid webhook URL must be provided to receive asynchronous responses.
  • Proper network access and permissions to reach both the LinkedIn API and the webhook endpoint are necessary.

Troubleshooting

  • Common issues:

    • Invalid or malformed LinkedIn post URL may cause the operation to fail or return no data.
    • Incorrect or missing webhook URL will prevent the node from receiving the response.
    • API authentication errors if the API key credential is invalid or expired.
    • Network connectivity problems between n8n, LinkedIn API, or the webhook endpoint.

  • Error messages and resolutions:

    • "Invalid post URL" — Verify the LinkedIn post URL format and ensure it points to an existing post.
    • "Webhook not reachable" — Check that the webhook URL is correct, publicly accessible, and able to accept incoming requests.
    • "Authentication failed" — Reconfigure the API key credential with valid credentials.
    • Timeouts or no response — Ensure stable internet connection and that the external services are operational.

Links and References

Discussion