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 management, among other resources. Specifically, the Get Payment operation retrieves detailed information about a specific payment by its ID.
Common scenarios where this node is beneficial include:
- Fetching payment details for auditing or reconciliation purposes.
- Integrating payment data into workflows for reporting or notification.
- Automating retrieval of payment status and metadata in business processes.
For example, you might use this node to get the status and details of a payment after a customer completes a transaction, then trigger follow-up actions such as sending a receipt or updating an internal 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. |
| Payment ID | The unique numeric identifier of the payment to retrieve (required). |
Output
The output contains a JSON object representing the payment details retrieved from the Lectful Central API. This includes all available fields returned by the API for the specified payment ID, such as amount, currency, status, payment method, date, reference numbers, notes, and any other metadata associated with the payment.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": 12345,
"invoice_id": 67890,
"payment_method_id": 111,
"amount": 2999,
"currency": "USD",
"status": "completed",
"payment_date": "2024-01-15",
"payment_reference": "REF-001",
"gateway_transaction_id": "TXN-12345",
"notes": "Payment received via credit card"
}
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 read payment data.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
Missing or invalid credentials:
Error if neither valid stored credentials nor manual configuration with base URL and API key are provided.
Resolution: Configure credentials properly or provide manual overrides.Invalid Payment ID:
If the payment ID does not exist or is invalid, the API will likely return an error or empty response.
Resolution: Verify the payment ID is correct and exists in the system.Network or API errors:
Timeouts, connectivity issues, or API downtime can cause failures.
Resolution: Check network connectivity, API status, and retry as needed.JSON parsing errors:
Unlikely in this operation since the response is expected to be JSON, but malformed responses could cause issues.
Resolution: Ensure the API endpoint is stable and returning valid JSON.
Links and References
- Lectful Central API Documentation (Assumed URL, replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for authentication and error handling.
This summary focuses exclusively on the Payment Management > Get Payment operation as requested.