Actions21
Overview
This node integrates with the GravitySocial API to manage social media posts within a specified workspace. The Post - Update operation allows users to modify existing posts by updating their content, associated accounts, media attachments, scheduled time, and tags.
Typical use cases include:
- Editing the text or media of a scheduled or draft post before publishing.
- Changing the list of social media accounts where the post will be published.
- Rescheduling a post to a different date and time.
- Updating tags for better categorization or filtering.
For example, a social media manager can automate updates to multiple posts' content or scheduling times in bulk, ensuring campaigns remain timely and relevant without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace containing the post to update. |
| Post UUID | The unique identifier (UUID) of the specific post to update. |
| Update Fields | A collection of fields that can be updated on the post: |
| - Account IDs: Comma-separated list of account IDs to associate with the post. | |
| - Content: The textual content of the post. | |
| - Media URLs: Comma-separated list of media URLs to attach to the post. | |
| - Schedule Date: Date and time to schedule the post. | |
| - Tags: Comma-separated list of tags to assign to the post. |
Output
The node outputs JSON data representing the updated post or posts returned from the GravitySocial API after the update operation. The structure typically includes details such as post identifiers, content, associated accounts, media, scheduling information, and tags.
If multiple posts are updated or returned, the output is an array of such objects.
The node does not output binary data for 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.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Validation Errors (HTTP 422): If required fields are missing or invalid (e.g., malformed UUIDs, incorrect date formats), the API returns validation errors. The node surfaces these with detailed messages indicating which fields failed validation. To resolve, verify all input parameters conform to expected formats and requirements.
Authentication Issues: If the API key or access token is invalid or expired, requests will fail with authorization errors. Ensure the credentials are correctly set up and have necessary permissions.
Network or API Errors: Temporary network issues or API downtime may cause request failures. Retrying after some time or checking API status can help.
Incorrect Property Usage: For example, providing empty strings instead of valid UUIDs for required fields will cause errors. Always provide valid values for required properties.
Links and References
- GravitySocial API Documentation (hypothetical link for reference)
- n8n Documentation on Creating Custom Nodes
- General info on UUID format
This summary is based solely on static analysis of the provided source code and property definitions.