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 interacts with the Lectful Central API to perform administrative operations related to payment methods, among many other resources. Specifically, the List Payment Methods operation retrieves a paginated list of all payment methods configured in the Lectful system.
This node is beneficial for automating workflows that require managing or auditing payment methods, such as syncing payment options with other systems, generating reports on available payment methods, or integrating payment method data into customer-facing applications.
Practical example:
You can use this node to fetch all active payment methods from your Lectful Central account and then update your e-commerce platform or CRM with the latest payment options available to customers.
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 overrides |
| Base URL Override | Optional base URL to override the credential setting (without /api/v1) when using manual mode |
| API Key Override | Optional API key to override the credential setting when using manual mode |
These properties control how the node authenticates requests to the Lectful Central API.
For the List Payment Methods operation specifically, the following input parameters are used:
| Name | Meaning |
|---|---|
| Page | Page number for pagination (default: 1) |
| Per Page | Number of items per page (default: 15) |
| Search | Optional search term to filter payment methods by name or other criteria |
Output
The node outputs an array of JSON objects representing payment methods retrieved from the Lectful Central API.
Each item in the output json field corresponds to a payment method object returned by the API. The structure typically includes fields such as:
id: Unique identifier of the payment methodname: Name of the payment method (e.g., Credit Card, Bank Transfer)code: Unique code for the payment method (e.g., credit_card, bank_transfer)description: Description of the payment methodis_active: Boolean indicating if the payment method is currently activeis_online: Boolean indicating if the payment method supports online paymentsrequires_reference: Boolean indicating if the payment method requires a reference number
No binary data output is produced by this operation.
Dependencies
- Requires access to the Lectful Central API.
- Requires either stored credentials configured in n8n or manual entry of the base URL and API key.
- The node uses HTTP Bearer token authentication with the provided API key.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Missing or invalid credentials: If neither stored credentials nor manual overrides are properly set, the node will throw an error indicating missing or invalid credentials. Ensure you have configured valid API credentials or provide them manually.
- Base URL or API key missing in manual mode: When using manual configuration, both the Base URL Override and API Key Override must be provided; otherwise, the node will error out.
- API request failures: Network issues, incorrect API keys, or insufficient permissions may cause API calls to fail. Check the API response messages logged by the node for details.
- Pagination parameters: Providing invalid values for
pageorperPagemay result in unexpected results or errors. Use positive integers.
Links and References
- Lectful Central API Documentation (Assumed URL, replace with actual if known)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP requests)