Actions63
- Authentication Actions
- Tenant Management Actions
- Blog Management Actions
- Image Management Actions
- BuilderX AI Integration Actions
- Form Submissions Actions
- Subscription Management Actions
- Subscription Operations Actions
- Product Family Management Actions
- Feature Management Actions
- Invoice Management Actions
- Payment Management Actions
- Payment Method Management Actions
- Coupon Management Actions
- Health Checks Actions
Overview
This node integrates with the Lectful Central API to perform administrative operations, including managing blog posts. Specifically, the Create Blog Post operation allows users to create a new blog post by providing a title, slug, and content. This is useful for automating content publishing workflows, such as creating blog entries from external data sources or scheduled triggers.
Practical examples:
- Automatically publish new blog posts when a form submission is received.
- Create blog posts based on data from other systems like CRMs or CMS platforms.
- Schedule blog post creation as part of a content marketing automation workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication Mode | Choose how to authenticate with the Lectful Central API: - Use Stored Credentials - Manual Configuration (provide base URL and API key manually) |
| Credentials Note | Notice shown only in Manual Configuration mode explaining that credentials can be left empty if overrides are provided. |
| Base URL Override | Optional base URL to override the credential setting (without /api/v1). Used only in Manual Configuration mode. |
| API Key Override | Optional API key to override the credential setting. Used only in Manual Configuration mode. |
| Title | The blog post title (required). |
| Slug | The blog post slug, a URL-friendly version of the title (required). |
| Content | The main content/body of the blog post (required). |
Output
The node outputs an array of JSON objects representing the response from the Lectful Central API after creating the blog post. The JSON structure corresponds to the created blog post's details as returned by the API, typically including fields like the post ID, title, slug, content, timestamps, and any metadata the API provides.
No binary data output is involved in this operation.
Example output snippet (conceptual):
{
"id": 123,
"title": "My New Blog Post",
"slug": "my-new-blog-post",
"content": "This is the content of the blog post.",
"created_at": "2024-06-01T12:00:00Z",
"updated_at": "2024-06-01T12:00:00Z"
}
Dependencies
- Requires access to the Lectful Central API.
- Requires either stored API credentials configured in n8n or manual entry of the base URL and API key.
- The node uses HTTP requests with Bearer token authentication.
- No additional external libraries beyond standard HTTP request helpers in n8n.
Troubleshooting
- Missing or invalid credentials: If using stored credentials, ensure they are properly configured with a valid base URL and API key. If using manual mode, both Base URL Override and API Key Override must be provided.
- Invalid input parameters: Title, Slug, and Content are required. Missing these will cause errors.
- API errors: The node logs detailed error messages from the API. Common issues include authorization failures, invalid slugs, or content validation errors.
- JSON parsing errors: Not applicable here since inputs are strings; however, malformed inputs might cause API rejection.
- To resolve credential issues, verify API keys and URLs outside n8n first.
- For slug-related errors, ensure the slug is URL-friendly (e.g., lowercase, no spaces).
Links and References
- Lectful Central API Documentation (hypothetical link, replace with actual if available)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
If you need summaries for other resources or operations, feel free to ask!