GravitySocial icon

GravitySocial

Interact with GravitySocial API

Overview

This node integrates with the GravitySocial API to manage tags within a specified workspace. The "Get Many" operation for the "Tag" resource retrieves multiple tags associated with a given workspace UUID. This is useful for workflows that need to list, filter, or process tags in bulk, such as syncing tags with other systems, generating reports, or automating tag-based content categorization.

Practical example:
A social media manager wants to fetch all tags from a specific workspace to analyze tag usage trends or to update another platform with the current tag list automatically.

Properties

Name Meaning
Workspace UUID The UUID of the workspace to query tags from. This is required to specify the context for retrieving tags.

Output

The output is a JSON array containing tag objects retrieved from the GravitySocial API. Each object represents a tag with its properties (such as UUID, name, color, etc.) as returned by the API.

  • If multiple tags exist, each will be an element in the array.
  • The node does not output binary data for this operation.

Example output structure (simplified):

[
  {
    "uuid": "tag-uuid-1",
    "name": "Tag Name 1",
    "hex_color": "#ff0000"
  },
  {
    "uuid": "tag-uuid-2",
    "name": "Tag Name 2",
    "hex_color": "#00ff00"
  }
]

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 in the credentials.
  • No additional external dependencies are needed beyond standard HTTP requests.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace UUID: The API call will fail if the workspace UUID is not provided or incorrect.
    • Authentication errors: Ensure the API key credential is valid and has proper permissions.
    • Network or API downtime: Temporary failures may occur if the GravitySocial API is unreachable.
  • Error messages:

    • Validation errors (HTTP 422) indicate invalid input parameters; check the workspace UUID format.
    • HTTP status errors (e.g., 401 Unauthorized) suggest authentication problems.
    • Unexpected response formats or empty results may indicate no tags exist for the workspace.
  • Resolution tips:

    • Verify the workspace UUID is correct and accessible.
    • Confirm API credentials are up to date.
    • Use the node's error output to inspect detailed error messages and adjust inputs accordingly.

Links and References

Discussion