Actions37
- Offer Item Actions
- Customer Actions
- Dispute Actions
- Installment Actions
- Line Item Actions
- Offer Actions
- Payment Actions
- Payment Method Actions
- Payment Plan Actions
- Payment Schedule Actions
- Refund Actions
Overview
This node interacts with the "Partially Payment Plans API" to manage various payment-related resources. Specifically, for the Payment Method - List operation, it retrieves a list of payment methods associated with a specified customer. This is useful in scenarios where you want to fetch all saved payment methods for a customer to display them, validate them, or use them in subsequent payment processing workflows.
Practical example:
You have an e-commerce workflow where after identifying a customer, you want to retrieve all their stored payment methods to allow them to select one for a new purchase or subscription plan.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer whose payment methods you want to list. Required. |
Output
The output is a JSON array where each element represents a payment method object retrieved from the API for the given customer. Each payment method object typically contains details such as payment method type, identifiers, and metadata related to that payment method.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Partially Payment Plans API.
- Requires an API authentication token or API key credential configured in n8n to authorize requests.
- The node uses an internal helper function to make HTTP requests to the API endpoints.
Troubleshooting
Common issues:
- Missing or invalid Customer ID will cause the API request to fail.
- Invalid or expired API credentials will result in authentication errors.
- Network connectivity issues can prevent successful API calls.
Common error messages:
- "401 Unauthorized" — Check that your API key or token is correctly configured and has not expired.
- "404 Not Found" — Verify that the provided Customer ID exists in the system.
- "400 Bad Request" — Ensure the Customer ID parameter is provided and correctly formatted.
Resolution tips:
- Double-check the Customer ID input for correctness.
- Confirm API credentials are valid and properly set up in n8n.
- Review network settings and firewall rules if connectivity issues persist.
Links and References
- Partially Payment Plans API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes