Actions21
Overview
This node integrates with the GravitySocial API to manage media files within a specified workspace. The "Get" operation for the "Media" resource retrieves detailed information about a specific media file by its UUID. This is useful when you need to fetch metadata or details of a particular media asset stored in your GravitySocial workspace.
Common scenarios:
- Retrieving media file details before attaching it to a post.
- Verifying media attributes such as alt text or file type.
- Fetching media info for audit or reporting purposes.
Practical example:
You have uploaded several images to your social media management platform and want to retrieve the details of one image to confirm its properties before scheduling a post that uses it.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace where the media file resides. |
| Media UUID | The unique identifier (UUID) of the specific media file to retrieve. |
Output
The output is a JSON array containing the media file's data retrieved from the GravitySocial API. The structure typically includes all metadata and attributes associated with the media file, such as its ID, URL, alt text, upload date, and other relevant properties defined by the API.
If multiple items are returned (though for "Get" it should be a single item), they are flattened into the output array.
The node does not output binary data for this operation; it only returns JSON metadata about the media.
Dependencies
- Requires an API key credential for authenticating with the GravitySocial API.
- The node expects the GravitySocial API base URL and access token to be configured in the credentials.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Missing or invalid Workspace UUID or Media UUID: The node requires these identifiers to locate the media file. Ensure they are correctly provided and valid.
- HTTP errors (e.g., 401 Unauthorized): Usually caused by invalid or expired API tokens. Verify the API key credential is correct and has necessary permissions.
- Validation errors (422): If the UUIDs are malformed or do not exist, the API may return validation errors. Check the error message for details on which fields failed.
- Network issues: Timeouts or connectivity problems can cause request failures. Confirm network access to the GravitySocial API endpoint.
- Unexpected response format: If the API changes, the node might fail to parse the response correctly. Review the API documentation or update the node accordingly.
Links and References
- GravitySocial API Documentation (example link, replace with actual)
- n8n HTTP Request Node documentation for understanding request/response handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
This summary focuses exclusively on the "Media" resource with the "Get" operation as requested.