Actions21
Overview
This node integrates with the GravitySocial API to manage media files within a specified workspace. The "Get Many" operation under the "Media" resource retrieves multiple media files, allowing users to fetch a list of media items associated with their workspace.
Common scenarios where this node is beneficial include:
- Bulk retrieval of media assets for social media management or content auditing.
- Synchronizing media libraries between GravitySocial and other platforms.
- Automating workflows that require processing or analyzing multiple media files at once.
For example, a social media manager could use this node to pull all media files from a workspace to generate reports on usage or to select media for scheduled posts.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace from which to retrieve media files. |
| Per Page Limit | Maximum number of media results to return in one request. Default is 50; minimum is 1. |
Output
The output is a JSON array containing media objects retrieved from the GravitySocial API. Each object represents a media file with its associated metadata as provided by the API.
If the node is used with other operations (not "Get Many"), it may also handle binary data for media uploads, but for the "Get Many" operation, the output is purely JSON data representing media entries.
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 via credentials.
- No additional external dependencies are required beyond standard HTTP requests.
Troubleshooting
- Missing or invalid Workspace UUID: The operation requires a valid workspace UUID. Ensure this property is correctly set; otherwise, the API will reject the request.
- API authentication errors: If the API key or access token is missing or invalid, the node will fail to authenticate. Verify the credentials configuration.
- Limit parameter issues: Setting the limit below 1 or to an excessively high number might cause errors or unexpected behavior. Use reasonable values.
- HTTP errors: The node logs detailed HTTP request and response information on failure. Common HTTP status codes like 401 (Unauthorized), 404 (Not Found), or 422 (Validation Error) indicate issues with credentials, resource identifiers, or request parameters.
- Validation errors: If the API returns validation errors, the node surfaces these with descriptive messages. Check the error details to correct input parameters.
Links and References
- GravitySocial API Documentation (example link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General info on UUIDs