Actions4
- Account Actions
- Media Actions
- Post Actions
Overview
The Media Upload operation in this node allows users to upload media files to the PostPulse platform. It supports two main upload sources:
- From File: Upload a binary file directly from the workflow's binary data.
- From Public URL: Import media by providing a publicly accessible URL.
This functionality is useful for automating social media management workflows where media assets need to be uploaded or imported before being attached to posts or other content. For example, you can automate uploading images or videos stored in your workflow or import media hosted elsewhere on the internet without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Upload Source | Choose whether to upload a file from the workflow's binary data ("From File") or import media from a public URL ("From Public URL"). |
| Input Binary Field | (Required if "From File" is selected) The name of the binary property in the input data that contains the file to upload. Default is "data". |
| URL | (Required if "From Public URL" is selected) The public URL of the media to import. Example: https://example.com/image.jpg |
| Filename Hint | (Optional, only for "From Public URL") A filename suggestion for the imported media, up to 255 characters. Example: my-image.jpg |
Output
The node outputs JSON data representing the result of the media upload or import operation. This typically includes metadata about the uploaded media such as its ID, status, URLs, or any relevant response fields returned by the PostPulse API.
If the upload source is a binary file, the node consumes binary data but does not output binary data itself; the output is structured JSON describing the uploaded media.
Dependencies
- Requires an API authentication token configured in the node credentials to access the PostPulse API.
- The node communicates with the PostPulse API endpoint at
https://api.post-pulse.com. - No additional external dependencies are required beyond the API key and network connectivity.
Troubleshooting
Common Issues:
- Incorrect binary property name: Ensure the binary property specified matches exactly the name of the binary data field in the input.
- Invalid or inaccessible URL: When importing from a URL, verify the URL is publicly accessible and points directly to a media file.
- API authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
- Filename hint too long: Keep the filename hint under 255 characters to avoid validation errors.
Error Messages:
- Errors related to missing binary data or invalid URL will typically indicate which input parameter caused the failure.
- Authentication failures will return standard API error messages indicating invalid or missing credentials.
- Network or timeout errors may occur if the PostPulse API is unreachable.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring network connectivity.
Links and References
- PostPulse API Documentation (hypothetical link)
- n8n documentation on Working with Binary Data
- General guide on Using HTTP Request Nodes in n8n