Actions9
- Upload Actions
- Status & History Actions
- User Actions
Overview
This node interacts with the Upload-Post API to manage social media content uploads and monitor their status and history. Specifically, for the Status & History resource with the Get Upload History operation, it retrieves a paginated list of past upload activities, allowing users to review previous posts made through the platform.
Common scenarios where this node is beneficial include:
- Auditing or reviewing previously uploaded social media posts.
- Tracking upload activity over time for reporting or analytics.
- Debugging or verifying that scheduled or asynchronous uploads were processed correctly.
For example, a user might want to fetch the last 50 uploads to see which posts succeeded or failed, or to gather metadata about those posts for further processing.
Properties
| Name | Meaning |
|---|---|
| Page | Page number for pagination. Indicates which page of the upload history to retrieve. |
| Limit | Number of items per page. Allowed values are 20, 50, or 100. Controls how many records are returned per request. |
Output
The node outputs JSON data representing the upload history retrieved from the Upload-Post API. The structure typically includes:
- A list/array of upload entries, each containing details such as upload timestamps, status, platforms targeted, and possibly identifiers or metadata related to each upload.
- Pagination information may also be included depending on the API response.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Upload-Post API to authenticate requests.
- The node makes HTTP GET requests to the endpoint
https://api.upload-post.com/api/uploadposts/history. - Pagination parameters (
pageandlimit) are sent as query string parameters.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Requesting a page number beyond available pages may return empty results.
- Using unsupported limit values (other than 20, 50, or 100) may cause errors or default behavior.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Timeout or network errors suggest connectivity issues; check network access and API availability.
- Unexpected API responses may require checking if the API has changed or if input parameters are correct.
Links and References
- Upload-Post API Documentation (general reference for API endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics (conceptual)
This summary focuses exclusively on the "Status & History" resource and the "Get Upload History" operation as requested.