Actions21
Overview
This node integrates with the GravitySocial API to manage social media posts within a specified workspace. The "Approve" operation for the "Post" resource allows users to approve a post identified by its UUID, marking it as approved in the system.
Typical use cases include:
- Automating the approval workflow of social media posts before publishing.
- Integrating post approval into larger automation workflows where posts require review.
- Managing content moderation or compliance checks by programmatically approving posts.
For example, after creating or scheduling posts, this node can be used to approve them automatically once certain conditions are met, streamlining the publishing process.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace containing the post. |
| Post UUID | The unique identifier (UUID) of the post to approve. |
Output
The node outputs the JSON response returned by the GravitySocial API after attempting to approve the post. This typically includes details about the approved post or confirmation of the approval action.
The output is structured as an array of JSON objects representing the API response data. If the API returns multiple items, they 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.
- The workspace UUID and post UUID must be provided as input parameters.
- The node makes HTTP requests to the GravitySocial API endpoints.
Troubleshooting
Common issues:
- Invalid or missing workspace UUID or post UUID will cause the request to fail.
- Expired or incorrect API authentication token will result in authorization errors.
- Network connectivity issues may prevent successful API calls.
Error messages:
- Validation errors (HTTP 422) indicate invalid input data; the error message will specify which fields failed validation.
- HTTP status errors (e.g., 401 Unauthorized, 404 Not Found) indicate authentication problems or that the specified post or workspace does not exist.
- The node logs detailed request and response information to help diagnose issues.
Resolution tips:
- Verify that the workspace and post UUIDs are correct and correspond to existing entities.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and API endpoint availability.
- Review error details logged by the node for specific validation or permission issues.
Links and References
- GravitySocial API Documentation (example link, replace with actual if available)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/