GravitySocial icon

GravitySocial

Interact with GravitySocial API

Actions21

Overview

This node integrates with the GravitySocial API to manage tags within a specified workspace. The "Tag: Get" operation retrieves detailed information about a specific tag identified by its UUID in a given workspace. This is useful for workflows that need to fetch metadata or properties of tags for further processing, reporting, or conditional logic.

Common scenarios:

  • Fetching tag details to display or log them.
  • Using tag information to filter or categorize posts or media.
  • Validating tag existence before performing updates or deletions.

Practical example:
A social media manager wants to automate content categorization by fetching tag details and then routing posts based on tag color or name. This node can retrieve the tag data needed for such decisions.

Properties

Name Meaning
Workspace UUID The unique identifier (UUID) of the workspace where the tag exists.
Tag UUID The unique identifier (UUID) of the tag to retrieve.

Output

The node outputs JSON data representing the tag object retrieved from the GravitySocial API. The structure typically includes fields such as the tag's UUID, name, color (hex format), creation date, and other metadata related to the tag.

If multiple tags were requested (not applicable here since this is a single get operation), the output would be an array of such objects.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the GravitySocial API via an API key credential.
  • The node expects the API base URL and access token to be configured in the credentials.
  • The workspace UUID must be provided to scope the request correctly.
  • Network connectivity to the GravitySocial API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Workspace UUID or Tag UUID will cause the API request to fail.
    • Expired or incorrect API authentication token will result in authorization errors.
    • Network issues or API downtime may cause request failures.

  • Error messages:

    • Validation Error: If the UUIDs are malformed or do not exist, the API may return validation errors indicating which fields are invalid.
    • HTTP 401 Unauthorized: Indicates problems with the API key or token; verify credentials.
    • HTTP 404 Not Found: The specified tag or workspace does not exist; check UUID values.
    • Request failed: General network or server error; retry or check API status.

  • Resolution tips:

    • Double-check UUID inputs for correctness.
    • Ensure the API key credential is valid and has required permissions.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.
    • Review debug logs printed by the node for request and response details.

Links and References

Discussion