Lectful Central

Overview

The "Lectful Central" node integrates with the Lectful Central API, enabling administrative operations across various resources such as payments, invoices, subscriptions, blogs, and more. Specifically, the Payment Management - Get Payment Statistics operation retrieves comprehensive payment statistics and analytics from the Lectful system.

This node is beneficial for finance teams or administrators who want to automate the retrieval of payment insights, monitor payment trends, or generate reports within their workflow automation. For example, it can be used to fetch payment overview data periodically and trigger alerts if anomalies are detected or to feed dashboards with up-to-date payment metrics.

Properties

These properties control how the node authenticates requests to the Lectful Central API.

Output

The output is a JSON object containing the payment statistics data retrieved from the API endpoint /admin/payments/statistics/overview. The structure depends on the API response but generally includes aggregated payment metrics and analytics.

Example output JSON structure (simplified):

{
  "totalPayments": 1234,
  "totalAmount": 567890,
  "currency": "USD",
  "paymentStatusBreakdown": {
    "completed": 1000,
    "pending": 100,
    "failed": 50,
    "refunded": 84
  },
  "dateRange": {
    "from": "2023-01-01",
    "to": "2023-12-31"
  }
}

No binary data output is produced by this operation.

Dependencies

• Requires access to the Lectful Central API.
• Requires either:
  • Stored credentials configured in n8n with a valid base URL and API key, or
  • Manual configuration of the base URL and API key in the node parameters.
• The node uses HTTP Bearer token authentication with the provided API key.
• No additional external dependencies.

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 that the API key and base URL are correctly configured.
• Base URL Override required in Manual mode: When using Manual Configuration mode, both Base URL Override and API Key Override must be provided; otherwise, the node throws an error.
• API errors: If the API returns an error (e.g., unauthorized, rate limited), the node will throw an error with the message returned by the API. Check your API key permissions and usage limits.
• Network issues: Timeouts or connectivity problems will cause request failures. Verify network access to the Lectful API endpoint.
• Invalid JSON responses: The node attempts to parse string responses as JSON. If parsing fails, the raw string is returned. This usually indicates an unexpected API response format.

Links and References

• Lectful Central API Documentation (Assumed URL, replace with actual if available)
• n8n Documentation on HTTP Request Node for understanding API calls
• General info on Bearer Token Authentication

If you need details on other operations or resources, feel free to ask!