Actions21
Overview
This node integrates with the GravitySocial API to manage tags within a specified workspace. Specifically, the "Delete" operation for the "Tag" resource allows users to delete a tag by its unique identifier (UUID) from a given workspace.
Common scenarios where this node is beneficial include:
- Automating tag cleanup in social media management workflows.
- Removing obsolete or incorrect tags programmatically.
- Integrating tag deletion as part of larger content or account management automation.
For example, a user might set up an automation that deletes tags no longer associated with any posts or campaigns, ensuring the workspace remains organized.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The UUID of the workspace where the tag exists. This identifies the workspace context. |
| Tag UUID | The UUID of the tag to be deleted. This uniquely identifies the tag within the workspace. |
Output
The node outputs the JSON response returned by the GravitySocial API after attempting to delete the tag. The structure typically includes confirmation of deletion or details about the deleted tag. If the API returns an array or nested data under a data property, those are flattened into the output array.
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 from the configured credentials.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Common issues:
- Invalid or missing Workspace UUID or Tag UUID will cause the API request to fail.
- Network or authentication errors if the API key is invalid or expired.
- Attempting to delete a tag that does not exist or has already been deleted.
Error messages:
- Validation errors (HTTP 422) may occur if required parameters are missing or malformed. The error message will include details about which fields failed validation.
- HTTP errors with status codes like 401 (Unauthorized) indicate credential problems.
- Other HTTP errors (e.g., 404 Not Found) suggest the tag or workspace UUIDs are incorrect.
Resolution tips:
- Verify that the Workspace UUID and Tag UUID are correct and exist in the GravitySocial system.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and API endpoint accessibility.
- Review detailed error messages logged by the node for specific validation issues.
Links and References
- GravitySocial API Documentation (hypothetical link)
- n8n documentation on creating custom nodes
- General REST API best practices for error handling and authentication