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
The "Delete Payment" operation in the Lectful Central node allows users to delete a specific payment record from the Lectful Central system via its API. This operation is useful for administrative tasks such as removing erroneous or duplicate payments, managing refunds, or cleaning up payment data.
Typical scenarios include:
- Removing a payment that was entered by mistake.
- Deleting payments associated with cancelled invoices.
- Maintaining accurate financial records by removing outdated or invalid payments.
Example use case:
- An admin wants to delete a payment with ID 12345 because it was duplicated. They configure this node to perform the "Delete Payment" operation and provide the payment ID to remove it from the system.
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 stored credential's base URL (without /api/v1). |
| API Key Override | Optional API key to override the stored credential's API key. |
| Resource | The resource to operate on; here fixed to "Payment Management". |
| Operation | The operation to perform; here "Delete Payment". |
| Payment ID | The ID of the payment to delete (required). |
Output
The node outputs an array of JSON objects corresponding to each input item processed. For the "Delete Payment" operation, the output JSON contains the response from the Lectful Central API after attempting to delete the specified payment.
- If successful, the response typically confirms deletion (often an empty object or success message).
- If an error occurs, the output JSON will contain an
errorfield with the error message if "Continue On Fail" is enabled.
No binary data 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 API key must have sufficient permissions to delete payments.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Missing or Invalid Credentials: If neither stored credentials nor manual overrides are provided correctly, the node will throw an error indicating missing or invalid credentials. Ensure credentials are properly set or manual parameters are filled.
- Missing Payment ID: The payment ID is required. Omitting it will cause the node to fail.
- API Errors: The API may return errors if the payment ID does not exist, or if the payment cannot be deleted due to business rules (e.g., linked to active invoices). These errors will be surfaced in the node output.
- Network Issues: Timeouts or connectivity problems will cause request failures. Verify network access to the Lectful Central API endpoint.
- Continue On Fail: Enable this option to allow the workflow to continue processing other items even if one fails.
Links and References
- Lectful Central API Documentation (hypothetical link as no direct link provided)
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)
- General REST API best practices for handling DELETE operations.
This summary focuses specifically on the "Delete Payment" operation within the "Payment Management" resource of the Lectful Central node, based on static analysis of the provided source code and property definitions.