Actions33
- Bài Viết Actions
- Blog Actions
Overview
This node interacts with the "Blog" resource of the Sapo platform, allowing users to retrieve detailed information about a specific blog by its ID. It is useful in scenarios where you need to fetch and process blog metadata or content within an automated workflow, such as displaying blog details on a website, syncing blog data with other systems, or performing analytics.
For example, you might use this node to:
- Retrieve the full details of a blog post for display or further processing.
- Automate content management tasks by fetching blog info before updating or archiving.
- Integrate blog data into newsletters or marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| ID Blog | The unique numeric identifier of the blog to retrieve details for. This property is required. |
Output
The node outputs a JSON object containing the detailed information of the specified blog. The structure of this JSON depends on the Sapo API response for a blog entity but typically includes fields such as title, handle (URL slug), commentable status, template suffix, and other blog metadata.
Example output JSON structure (simplified):
{
"id": 123,
"title": "Company News",
"handle": "news",
"commentable": true,
"template_suffix": "alternate",
"created_at": "2023-01-01T12:00:00Z",
"updated_at": "2023-01-10T12:00:00Z"
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Sapo API via an API key credential configured in n8n.
- The node depends on the
SapoApiBaseclass which handles communication with the Sapo backend. - Proper network access to the Sapo API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing blog ID will cause the API call to fail.
- Network connectivity problems can prevent successful API requests.
- Insufficient permissions or invalid API credentials may result in authorization errors.
Error messages:
"Blog not found": The provided blog ID does not exist. Verify the ID is correct."Unauthorized"or"Invalid API key": Check that the API key credential is correctly set up and has sufficient permissions.- Timeout or network errors: Ensure your server or environment can reach the Sapo API endpoint.
To resolve errors, verify input parameters, check API credentials, and ensure stable network connectivity.
Links and References
- Sapo API Documentation (general reference for Sapo API)
- n8n documentation on creating custom nodes