Payfunnels icon

Payfunnels

Payfunnels

Actions4

Overview

This node integrates with the Payfunnels API to manage payments and subscriptions. Specifically, for the Payment - List operation, it retrieves a paginated list of payment records, optionally filtered by customer email. This is useful for scenarios where you want to fetch recent or specific payments made through Payfunnels, such as generating reports, auditing transactions, or syncing payment data with other systems.

Practical examples:

  • Fetching the latest 50 payments to display in a dashboard.
  • Searching payments by a customer's email to verify their transaction history.
  • Paginating through payments to process them in batches.

Properties

Name Meaning
Limit Max number of results to return. Controls how many payment records are fetched per call.
Page Page number. Used for pagination to specify which page of results to retrieve.
Email Search by customer email. Filters payments to those matching the provided email address.

Output

The output is an array of JSON objects representing individual payment records retrieved from the Payfunnels API. Each item corresponds to one payment and contains all relevant payment details as returned by the API.

Example structure (simplified):

[
  {
    "id": "payment_id_123",
    "amount": 1000,
    "currency": "USD",
    "customerEmail": "customer@example.com",
    "status": "completed",
    "createdAt": "2024-01-01T12:00:00Z",
    ...
  },
  ...
]

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Payfunnels API.
  • The node makes HTTP requests to https://api.payfunnels.com/n8n-integration.
  • Proper network access to the Payfunnels API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Providing an invalid page number or limit (e.g., less than 1) may result in API errors.
    • Network connectivity problems can cause request failures.
  • Error messages:

    • Authentication errors typically indicate issues with the API key; ensure the credential is correctly configured.
    • Validation errors from the API may occur if parameters like limit or page are out of range.
    • If the node throws an error about failing to fetch data, check internet connectivity and API availability.
  • Resolution tips:

    • Verify that the API key credential is set up and valid.
    • Use sensible values for pagination parameters (limit ≥ 1, page ≥ 1).
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion