Lectful Central icon

Lectful Central

Interact with the Lectful Central API for admin operations

Actions63

Overview

The "Get Invoice" operation in the Lectful Central node allows you to retrieve detailed information about a specific invoice by its ID from the Lectful Central API. This is useful for scenarios where you need to fetch invoice data for reporting, auditing, or further processing within an automation workflow.

For example, you might use this operation to:

  • Automatically pull invoice details after a payment is processed.
  • Retrieve invoice status and amounts to update your accounting system.
  • Fetch invoice metadata to send customized notifications 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)
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.
Invoice ID The unique numeric identifier of the invoice to retrieve. Required for the Get Invoice operation.

Output

The output is a JSON object representing the invoice details as returned by the Lectful Central API. It typically includes fields such as invoice number, subscription ID, amount, currency, due date, status, description, and other relevant invoice metadata.

Example structure (simplified):

{
  "id": 123,
  "subscription_id": 456,
  "invoice_number": "INV-001",
  "amount": 10000,
  "currency": "USD",
  "due_date": "2024-12-31",
  "status": "sent",
  "description": "Monthly subscription invoice"
}

No binary data output is produced by this operation.

Dependencies

  • Requires access to the Lectful Central API.
  • Authentication can be provided either via stored credentials configured in n8n or manual entry of the base URL and API key.
  • The node expects the API to be reachable at the specified base URL with valid authentication tokens.

Troubleshooting

  • Missing or invalid credentials: If using stored credentials, ensure they are correctly configured with a valid base URL and API key. If using manual mode, both Base URL Override and API Key Override must be provided.
  • Invoice ID not provided or invalid: The operation requires a valid numeric invoice ID. Ensure this property is set and corresponds to an existing invoice.
  • API connectivity issues: Network problems or incorrect base URL can cause request failures. Verify the base URL and network accessibility.
  • Error messages from API: The node will throw errors if the API returns error responses (e.g., invoice not found). Check the error message for details and verify the invoice ID.
  • JSON parsing errors: Rarely, if the API response is malformed, the node may fail to parse it. This usually indicates an issue on the API side.

Links and References

Discussion