Actions21
Overview
This node integrates with the GravitySocial API to manage media files within a specified workspace. Specifically, the Media - Delete operation allows users to delete one or more media files by providing their IDs. This is useful for cleaning up unused or outdated media assets in a social media management workflow.
Typical use cases include:
- Automatically removing media files that are no longer needed after posts have been published.
- Bulk deleting multiple media items to maintain an organized media library.
- Integrating media cleanup as part of a larger automation process managing social content.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace where the media files reside. |
| Media IDs | A comma-separated list of media file IDs to be deleted from the specified workspace. |
Output
The node outputs a JSON array containing the response data from the GravitySocial API after attempting to delete the specified media files. The structure typically includes confirmation of deletion or details about any errors encountered.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the GravitySocial API.
- The node expects the base URL and access token for the GravitySocial API to be configured in the credentials.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Common Issues:
- Providing invalid or non-existent media IDs will result in errors or no action.
- Incorrect or missing Workspace UUID will cause the API request to fail.
- Network or authentication issues may prevent successful API calls.
Error Messages:
- Validation errors (HTTP 422) occur if required parameters are missing or malformed. The error message will specify which fields failed validation.
- Authentication errors if the API token is invalid or expired.
- General HTTP errors with status codes and messages are logged for debugging.
Resolution Tips:
- Ensure all media IDs are valid and belong to the specified workspace.
- Verify the Workspace UUID is correct.
- Confirm that the API key credential is properly set up and has necessary permissions.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- GravitySocial API Documentation (hypothetical link based on context)
- n8n Documentation on Creating Custom Nodes
- n8n HTTP Request Helper Reference: httpRequest