Actions21
Overview
This node interacts with the GravitySocial API to manage social media posts within a specified workspace. The Delete Bulk operation under the Post resource allows users to delete multiple posts at once by specifying their UUIDs. Users can choose whether to permanently delete these posts or move them to trash, and also select where the deletion should occur: only in the app, only on social media platforms, or both.
This operation is beneficial when managing large volumes of posts that need to be cleaned up or removed efficiently without handling each post individually. For example, a social media manager might want to bulk-delete outdated or irrelevant posts from a campaign across multiple platforms quickly.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace containing the posts to delete. |
| Post UUIds | A comma-separated list of UUIDs representing the posts to be deleted in bulk. |
| Trash | Boolean flag indicating whether to move the posts to trash (true) instead of permanently deleting (false). |
| Delete Mode | Specifies where to delete the posts from. Options are: - App Only (default): Delete only from the app. - App and Social: Delete from both the app and social media platforms. - Social Only: Delete only from social media platforms. |
Output
The output is a JSON array containing the response data from the GravitySocial API after attempting to delete the specified posts. The structure depends on the API's response but 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:
- Invalid or missing Workspace UUID or Post UUIDs will cause the request to fail.
- Providing malformed or empty Post UUIDs list may result in no action or errors.
- Insufficient permissions or invalid API credentials will lead to authentication errors.
- Network issues or incorrect API endpoint configuration can cause request failures.
Error Messages:
- Validation Error: Indicates that one or more input parameters did not meet the API requirements. Check the error details for specific fields.
- HTTP 401 Unauthorized: Authentication failed; verify the API key credential.
- HTTP 422 Unprocessable Entity: Usually due to invalid data format or missing required fields; review the provided UUIDs and options.
- Request failed: General failure message; check network connectivity and API availability.
Resolution Tips:
- Ensure all required fields are correctly filled.
- Confirm that the API key credential is valid and has necessary permissions.
- Validate the format of the Post UUIDs string (comma-separated, no extra spaces).
- Use the "Trash" option carefully to avoid accidental permanent deletions.
Links and References
- GravitySocial API Documentation (hypothetical link as reference)
- n8n Documentation on Creating Custom Nodes
- General guidance on Handling Bulk Operations in APIs