Actions21
Overview
This node interacts with the GravitySocial API to manage social media posts within a specified workspace. Specifically, the Delete Post operation allows users to delete a single post either permanently or by moving it to trash. Additionally, users can specify where the deletion should occur: only within the app, on connected social media platforms, or both.
Common scenarios for this node include:
- Removing outdated or incorrect posts from your social media management app.
- Cleaning up posts that have been published incorrectly by deleting them from both the app and social media platforms.
- Temporarily removing posts by moving them to trash instead of permanent deletion.
Practical example:
- A marketing team wants to delete a scheduled post that is no longer relevant. They use this node to move the post to trash in the app without affecting any social media platforms.
- Another user wants to remove a post entirely from both the app and all linked social accounts to ensure it is no longer visible anywhere.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace containing the post. |
| Post UUID | The unique identifier (UUID) of the post to be deleted. |
| Trash | Boolean flag indicating whether to move the post to trash (true) or permanently delete it (false). |
| Delete Mode | Specifies where to delete the post from: - App Only: Delete only from the app (default). - App and Social: Delete from both the app and social media platforms. - Social Only: Delete only from social media platforms. |
Output
The output JSON contains the response data returned by the GravitySocial API after attempting to delete the post. This typically includes confirmation of deletion or details about the post's new status (e.g., moved to trash).
If the API returns an array or nested data, the node flattens and outputs the relevant data accordingly.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the GravitySocial API via an API key credential configured in n8n.
- The node uses the workspace UUID to target the correct workspace context.
- Proper permissions are needed on the API key to perform delete operations on posts.
Troubleshooting
Common issues:
- Invalid or missing Workspace UUID or Post UUID will cause the request to fail.
- Insufficient permissions on the API key may result in authorization errors.
- Network or API downtime can cause request failures.
Error messages:
Validation Error: Indicates required parameters are missing or invalid. Check that UUIDs are correctly provided.- HTTP errors such as 401 Unauthorized or 403 Forbidden suggest authentication or permission problems.
- If the API responds with a 422 status and validation errors, the node surfaces detailed error messages explaining which fields failed validation.
Resolution tips:
- Verify that the Workspace UUID and Post UUID are correct and exist in the GravitySocial system.
- Ensure the API key credential has delete permissions.
- Use the "Trash" option if you want to avoid permanent deletion.
- Check network connectivity and API service status.
Links and References
- GravitySocial API Documentation (hypothetical link for reference)
- n8n documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.