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

Actions18

Overview

This node enables users to create social media posts across multiple platforms simultaneously using the LATE social media management platform. It supports scheduling posts for future publication, immediate publishing, or saving drafts. The node is useful for social media managers and marketers who want to automate posting workflows across various networks such as Twitter/X, Instagram, Facebook, LinkedIn, TikTok, YouTube, and Threads.

Practical examples include:

  • Scheduling a marketing campaign post to go live on all selected platforms at a specific time.
  • Publishing breaking news immediately across all social channels.
  • Saving draft posts to review and edit later before publishing.

Properties

Name Meaning
Content The main text content of your post, used across all selected platforms. Supports emojis and hashtags. Note platform-specific character limits (e.g., Twitter: 280, LinkedIn: 3000).
Platforms An array specifying which platforms to post to. Each entry requires a platform name (e.g., twitter, instagram) and an account ID. Account IDs can be retrieved from a separate operation listing social accounts.
Scheduled For Date and time when the post should be published. Leave empty to publish immediately. Must be a future date/time. Use with Timezone for accurate scheduling.
Timezone Timezone for the scheduled post, e.g., "America/New_York". Defaults to UTC if not specified. Ensures correct timing across different regions.
Publish Now Boolean flag to publish the post immediately, ignoring any scheduled time.
Is Draft Boolean flag to save the post as a draft instead of publishing or scheduling. Drafts do not count toward upload limits and can be edited later.
Visibility Controls who can see the post. Options are Public (visible to everyone), Private (only followers/connections), and Unlisted (not shown in public feeds but accessible via direct link). Not all platforms support all options; platform defaults apply.
Tags Array of tags/keywords for the post, primarily used by YouTube for search optimization. Limited to about 15 tags and 500 characters total.
Media Items Array of media files (images, videos, GIFs) to attach to the post. Files must be uploaded beforehand, and their URLs provided here. Supports large files up to 5GB each.
Platform Specific Data Advanced settings tailored to individual platforms, such as TikTok privacy options, Instagram story types, Twitter threads, or YouTube first comments. Nested inside each platform's data object.

Output

The node outputs JSON data representing the result of the post creation request. This typically includes confirmation details such as post IDs, status, timestamps, and any error messages if applicable.

If media files are involved, the output may reference URLs or identifiers confirming successful attachment.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the LATE platform.
  • The node communicates with the LATE API endpoint at https://getlate.dev/api/v1.
  • Users must have valid social media account IDs configured within LATE to specify target platforms.
  • Proper timezone handling depends on standard timezone names being used.

Troubleshooting

  • Scheduling errors: If the scheduled date/time is in the past or improperly formatted, the API may reject the request. Ensure future dates and valid timezone strings.
  • Invalid platform/account IDs: Posts will fail if the specified platform or account ID does not exist or is not linked correctly. Verify account IDs via the 'Social Accounts > List' operation.
  • Unsupported visibility options: Some platforms may ignore unsupported visibility settings, leading to unexpected post visibility. Check platform documentation for supported options.
  • Media upload issues: Large files or incorrect URLs in media items may cause failures. Confirm files are uploaded successfully before referencing them.
  • Authentication failures: Ensure the API key credential is valid and has necessary permissions.

Common error messages usually relate to invalid parameters, authentication failure, or rate limiting. Reviewing the API response message helps identify the exact issue.

Links and References

Discussion