Actions21
Overview
This node integrates with the GravitySocial API to manage social media posts within a workspace. Specifically, the Post - Schedule operation allows users to schedule an existing post for publishing at a later time or optionally publish it immediately.
Typical use cases include:
- Scheduling social media posts in advance to maintain consistent content delivery.
- Quickly publishing a post immediately if needed by overriding the scheduled time.
- Automating social media workflows by integrating scheduling into broader automation pipelines.
For example, a marketing team can prepare posts ahead of time and use this node to schedule them for optimal engagement times. Alternatively, if a breaking news update arises, they can use the "Post Now" option to publish instantly.
Properties
| Name | Meaning |
|---|---|
| Workspace UUID | The unique identifier (UUID) of the workspace where the post exists. |
| Post UUID | The unique identifier (UUID) of the post to be scheduled. |
| Post Now | Boolean flag indicating whether to publish the post immediately instead of waiting for the scheduled date and time. |
Output
The node outputs the JSON response returned by the GravitySocial API after attempting to schedule the post. This typically includes details about the scheduled post such as its status, scheduled time, and any metadata returned by the API.
If the API returns an array or nested data under a data property, the node flattens and outputs that array. Otherwise, it outputs the raw JSON object.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the GravitySocial API via an API key credential configured in n8n.
- The node expects the API base URL and access token from the credentials.
- The workspace and post UUIDs must exist and be valid in the GravitySocial system.
Troubleshooting
- Invalid UUIDs: If the workspace or post UUIDs are incorrect or do not exist, the API will return errors. Verify these IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- HTTP 422 Validation Errors: These occur if required parameters are missing or invalid. The error message will include details on which fields failed validation.
- Network Issues: Connectivity problems to the GravitySocial API endpoint will cause request failures.
- Unexpected API Responses: If the API changes or returns unexpected data, the node may fail or produce incomplete output.
To resolve errors:
- Check the exact error message logged by the node.
- Confirm all required properties are set correctly.
- Validate API credentials and permissions.
- Review GravitySocial API documentation for any updates or changes.
Links and References
- GravitySocial API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation: Creating Custom Nodes
- General info on scheduling social media posts: Social Media Scheduling Best Practices