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 enables interaction with the Lectful Central API, focusing on administrative operations. Specifically, the Admin Login operation under the Authentication resource allows an admin user to authenticate by providing their email and password. Upon successful login, the node receives a Sanctum API token that can be used for subsequent authenticated requests.
Typical use cases include:
- Automating admin authentication workflows in n8n.
- Integrating Lectful Central admin login into larger automation pipelines.
- Programmatically obtaining API tokens for further API interactions without manual login steps.
Example: An admin wants to automate the process of logging into Lectful Central and then perform tenant or blog management tasks using the obtained token.
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 when using Manual Configuration mode explaining credential usage. |
| Base URL Override | Optional base URL to override the stored credential's base URL (without /api/v1). |
| API Key Override | Optional API key to override the stored credential's API key. |
| Admin email address (required for Admin Login). | |
| Password | Admin password (required for Admin Login). |
Output
The node outputs an array of JSON objects, each representing the response from the Lectful Central API for each input item processed.
For the Admin Login operation, the output JSON contains the API response which typically includes the Sanctum API token and any related authentication data returned by the /admin/login endpoint.
No binary data is output by this node.
Dependencies
- Requires access to the Lectful Central API.
- Supports two authentication modes:
- Using stored credentials configured in n8n (an API key credential and base URL).
- Manual configuration by providing base URL and API key directly in the node parameters.
- The node uses HTTP requests with Bearer token authorization headers.
- No additional external libraries beyond standard n8n helper methods are required.
Troubleshooting
Missing or invalid credentials error:
When using "Use Stored Credentials" mode, if credentials are not configured or incomplete, the node throws an error instructing to configure valid credentials or switch to Manual Configuration mode.Manual Configuration missing parameters:
If "Manual Configuration" mode is selected but either Base URL Override or API Key Override is empty, the node will throw an error indicating these are required.Invalid JSON format errors:
Some operations expect JSON strings as input (not relevant for Admin Login), and invalid JSON will cause errors.API request failures:
Network issues, incorrect URLs, or invalid API keys will result in HTTP errors. Check the Base URL and API key correctness.Common error messages:
"Invalid or missing credentials": Ensure credentials are properly set or manual overrides provided."Base URL Override is required when using Manual Configuration mode": Provide the base URL."API Key Override is required when using Manual Configuration mode": Provide the API key.
Links and References
- Lectful Central API Documentation (Assumed, replace with actual URL if available)
- Sanctum API Authentication (for understanding the token mechanism)
If you need details on other resources or operations, feel free to ask!