LATE icon

LATE

Schedule and manage social media posts across multiple platforms with LATE - the professional social media management platform supporting Twitter/X, Instagram, Facebook, LinkedIn, TikTok, YouTube, and Threads
Join our community

Actions18

Overview

This node integrates with the LATE social media management platform, enabling users to list social media posts managed within LATE. Specifically, the "Posts - List" operation fetches a paginated list of posts filtered by status and platform. This is useful for monitoring, reporting, or further processing posts across multiple social media channels such as Twitter, Instagram, Facebook, LinkedIn, TikTok, YouTube, and Threads.

Practical examples include:

  • Retrieving all published posts on Instagram for analytics.
  • Fetching scheduled posts on LinkedIn to prepare reminders or notifications.
  • Listing failed posts on Twitter to trigger error handling workflows.

Properties

Name Meaning
Page Page number of the results to retrieve (pagination).
Limit Number of posts per page to return, with a maximum of 100 posts per request.
Status Filter posts by their status. Options: All, Draft, Scheduled, Published, Failed.
Platform Filter posts by social media platform. Options: All, Twitter, Instagram, Facebook, LinkedIn, TikTok, YouTube, Threads.

Output

The node outputs a JSON array of post objects corresponding to the requested page, limit, status, and platform filters. Each post object typically contains details such as post content, status, scheduled time, platform, and other metadata managed by LATE.

If the node supports binary data output (e.g., media attachments), it would be included alongside the JSON data, but this is not explicitly indicated in the provided code snippet.

Dependencies

  • Requires an API key credential for authenticating with the LATE platform API.
  • The node communicates with the LATE API at https://getlate.dev/api/v1.
  • Proper configuration of the API credential within n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Requesting a page number beyond available pages may return empty results.
    • Exceeding the maximum limit of 100 posts per page may result in errors or truncated responses.
    • Filtering by unsupported status or platform values will likely return no results.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; reconfigure credentials.
    • Rate limiting errors from the API suggest too many requests in a short time; implement retry logic or reduce request frequency.
    • Validation errors on input properties (e.g., negative page number) should be corrected by providing valid values.

Links and References

Discussion