Actions9
- Upload Actions
- Status & History Actions
- User Actions
Overview
This node enables uploading content to various social media platforms through the Upload-Post API. It supports uploading photos, videos, and text posts to platforms like TikTok, Instagram, LinkedIn, Facebook, X (Twitter), Threads, YouTube, and Pinterest. Additionally, it can retrieve upload status and history, manage users, and generate or validate JWT tokens for platform integration.
Common scenarios include:
- Automating social media content publishing across multiple platforms.
- Scheduling posts for future publication.
- Monitoring upload status asynchronously.
- Managing user profiles within the Upload-Post service.
- Integrating Upload-Post functionality into custom platforms via JWT.
Example use cases:
- A marketing team schedules photo and video posts to Instagram, Facebook, and TikTok simultaneously.
- A content manager uploads a text announcement to LinkedIn and X.
- A developer integrates Upload-Post into their own app using generated JWT tokens.
- An analyst retrieves upload history to track past campaigns.
Properties
| Name | Meaning |
|---|---|
| Pinterest Board ID | Target Pinterest board ID; required when Pinterest platform is selected for upload operations. |
Additional relevant properties for the "Upload" resource with "Default" operation (uploadPhotos, uploadVideo, uploadText) include:
| Name | Meaning |
|---|---|
| User | Profile name created in Upload-Post account; identifies the user performing the upload. |
| Platform(s) | List of social media platforms to upload to (e.g., Facebook, Instagram, LinkedIn, Pinterest, etc.). |
| Title / Main Content | Title or main text content of the post; used as fallback description for some video platforms. |
| Scheduled Date | Optional date/time to schedule the post instead of immediate publishing. |
| Upload Asynchronously | Whether to process upload asynchronously and return immediately (true/false). |
| Wait for Completion | Whether to poll upload status until completion or timeout when asynchronous upload is used. |
| Poll Interval (Seconds) | Frequency in seconds to poll the status endpoint when waiting for completion. |
| Timeout (Seconds) | Maximum time in seconds to wait before giving up polling. |
Platform-specific options exist for detailed control over uploads (e.g., Facebook Page ID, LinkedIn visibility, TikTok privacy settings, YouTube video metadata, etc.).
Output
The node outputs JSON data representing the response from the Upload-Post API for each input item. The structure varies by operation but generally includes:
- For upload operations: details about the upload request, including a
request_idif processed asynchronously. - For status queries: current status of an upload request.
- For history queries: paginated list of past uploads.
- For user management: information about created, deleted, or listed users.
- For JWT operations: generated tokens or validation results.
If asynchronous upload is enabled and "Wait for Completion" is true, the node polls the status endpoint and outputs the final upload result.
The node does not output binary data directly but accepts binary inputs for photos, videos, and thumbnails by referencing binary property names.
Dependencies
- Requires an API key credential for the Upload-Post API.
- Network access to
https://api.upload-post.com/api. - Proper configuration of credentials in n8n with the API key.
- Binary data support in n8n for file uploads (photos, videos, thumbnails).
Troubleshooting
- Missing binary data: If a specified binary property for photo/video/thumbnail is not found, a warning is logged. Ensure the binary data exists on the input item under the correct property name.
- Timeouts during synchronous upload: If synchronous upload takes longer than 59 seconds, the node automatically switches to asynchronous mode. Use the returned
request_idwith the "Get Upload Status" operation to check progress. - Invalid or missing API key: Authentication errors occur if the API key credential is not set or invalid.
- Required fields missing: For example, Pinterest uploads require a board ID; Facebook uploads require a page ID.
- Polling timeout: When waiting for completion, if the polling exceeds the configured timeout, the node returns a timeout message.
- Platform-specific restrictions: Some platforms have specific requirements or supported features (e.g., LinkedIn visibility options differ between photo and video uploads).
Links and References
- Upload-Post API Documentation (general reference)
- Social media platform developer docs for upload constraints and metadata (Facebook, Instagram, TikTok, LinkedIn, YouTube, Pinterest, X/Twitter, Threads)
This summary focuses on the "Upload" resource with the default upload operations as requested.