Actions21
Overview
This node integrates with the GravitySocial API to manage social media posts and related resources such as accounts, media, and tags. Specifically, for the Post resource and the Add to Queue operation, it allows users to add an existing post to a publishing queue within a specified workspace.
Typical use cases include automating social media workflows where posts are prepared in advance and then queued for publishing at optimal times. For example, a marketing team can create multiple posts and programmatically add them to a queue to be published sequentially without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace where the post exists and will be queued. |
| Post UUID | The unique identifier (UUID) of the post that should be added to the publishing queue. |
Output
The node outputs the JSON response returned by the GravitySocial API after adding the post to the queue. This typically includes details about the queued post or confirmation of the action.
- The output is a JSON array containing one or more objects representing the API response.
- 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 GravitySocial API base URL and access token to be configured via credentials.
- The workspace UUID and post UUID must be valid and correspond to existing entities in the GravitySocial system.
Troubleshooting
- Invalid UUIDs: If the workspace UUID or post UUID is incorrect or does not exist, the API will return an error. Verify these values before running the node.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- HTTP Errors: Network issues or API downtime may cause request failures. Check connectivity and API status.
- Validation Errors: The node logs detailed validation errors if the API rejects the request due to invalid data.
- Common Error Messages:
Validation Error: Indicates required parameters are missing or malformed.HTTP 401 Unauthorized: Authentication failed; check API credentials.HTTP 404 Not Found: The specified post or workspace does not exist.
To resolve errors, review the error messages logged by the node, verify input parameters, and confirm API credentials.
Links and References
- GravitySocial API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes
- General info on UUIDs