GravitySocial icon

GravitySocial

Interact with GravitySocial API

Overview

This node integrates with the GravitySocial API to manage social media accounts and related resources. Specifically, for the Account resource with the Get Many operation, it retrieves a list of social media accounts associated with a specified workspace.

Typical use cases include:

  • Fetching all social accounts linked to a particular workspace for reporting or synchronization.
  • Automating workflows that require bulk processing or analysis of multiple social accounts.
  • Integrating account data into other systems or dashboards.

For example, you might use this node to pull all accounts from a workspace before posting content or generating analytics reports.

Properties

Name Meaning
Workspace UUID The unique identifier (UUID) of the workspace whose accounts you want to retrieve. This is required.

Output

The node outputs an array of account objects in the json output field. Each object represents a social media account retrieved from the GravitySocial API for the specified workspace.

The exact structure of each account object depends on the API response but typically includes details such as account identifiers, names, types, and other metadata.

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 via credentials.
  • The workspace UUID must be provided as input to specify the context for the account retrieval.

Troubleshooting

  • Missing or invalid Workspace UUID: The operation requires a valid workspace UUID. Ensure this property is set correctly; otherwise, the API call will fail.
  • Authentication errors: If the API key or access token is missing, expired, or incorrect, the node will throw authentication errors. Verify your credentials configuration.
  • API rate limits or network issues: Temporary failures may occur due to rate limiting or connectivity problems. Retrying the operation after some time or checking network settings can help.
  • Validation errors: If the API returns validation errors (HTTP 422), the node surfaces detailed messages indicating which fields are invalid. Review these messages to correct input parameters.

Links and References

Discussion