Actions21
Overview
This node interacts with the GravitySocial API to manage social media posts within a specified workspace. The "Post - Get Many" operation retrieves multiple posts from a workspace, supporting filtering and pagination. It is useful for scenarios where you want to list or analyze posts based on criteria such as status, keywords, tags, or associated accounts.
Practical examples include:
- Fetching all published posts in a workspace for reporting.
- Retrieving draft posts filtered by specific tags or keywords.
- Paginating through scheduled posts to monitor upcoming content.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace from which to retrieve posts. |
| Per Page Limit | Maximum number of posts to return per request (minimum 1). |
| Filters | Collection of optional filters to narrow down the posts returned: |
| Account IDs | Comma-separated list of account IDs to filter posts by associated accounts. |
| Keyword | Filter posts containing this keyword in their content. |
| Page | Page number for paginated results (default is 1). |
| Status | Filter posts by their status. Options: Draft, Failed, Needs Approval, Only From Trash, Published, Scheduled. Default is Draft. |
| Tags | Comma-separated list of tags to filter posts by. |
Output
The output is an array of JSON objects representing posts retrieved from the GravitySocial API. Each object corresponds to a post and contains its details as provided by the API. The exact structure depends on the API response but typically includes fields like post ID, content, status, associated accounts, tags, scheduling information, and metadata.
No binary data is output 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 API to be configured in the credentials.
- No additional external dependencies are required beyond standard HTTP requests.
Troubleshooting
Common Issues:
- Invalid or missing Workspace UUID will cause the API call to fail.
- Providing invalid filter values (e.g., malformed account IDs or tags) may result in empty responses or errors.
- Pagination parameters out of range might return no results.
Error Messages:
- HTTP errors with status codes (e.g., 401 Unauthorized, 404 Not Found) indicate authentication issues or incorrect resource identifiers.
- Validation errors (HTTP 422) occur if filter parameters do not meet API requirements; the error message will detail which fields are invalid.
Resolution Tips:
- Ensure the Workspace UUID is correct and accessible with the provided API credentials.
- Validate filter inputs for correct formatting (e.g., comma-separated lists without extra spaces).
- Check API credentials and permissions if authentication errors occur.
Links and References
- GravitySocial API Documentation (example placeholder, replace with actual link if available)
- n8n Documentation on Creating Custom Nodes