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 integrates with the Partially Payment Plans API, allowing users to manage payment plans and related entities such as customers, offers, payments, and more. Specifically, for the Payment Plan - Update operation, it enables updating details of an existing payment plan, such as adding or modifying merchant notes.
Common scenarios where this node is beneficial include:
- Updating merchant notes or metadata on a payment plan after creation.
- Adjusting payment plan details without recreating the entire plan.
- Automating updates to payment plans based on external triggers or workflows.
For example, a merchant might use this node to add internal notes to a payment plan after customer service interactions or to update status-related information programmatically.
Properties
| Name | Meaning |
|---|---|
| Payment Plan ID | The unique identifier of the payment plan to update. |
| Notes | Merchant-specific notes or comments to attach to the payment plan (optional). |
Output
The node outputs an array of JSON objects representing the updated payment plan(s) returned from the Partially API. Each object contains the full details of the payment plan after the update, including any fields modified by the operation.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Partially API via an API key credential configured in n8n.
- The node uses the Partially API endpoints to perform CRUD operations on payment plans.
- Proper API credentials must be set up in n8n to authenticate requests.
Troubleshooting
- Missing or invalid Payment Plan ID: The node requires a valid payment plan ID; ensure this is correctly provided and corresponds to an existing payment plan.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or connectivity issues: Ensure that n8n can reach the Partially API endpoint without firewall or proxy restrictions.
- Invalid input data: If merchant notes or other fields contain unsupported characters or exceed length limits, the API may reject the request.
- Error messages from API: Typically include HTTP status codes and error messages indicating the cause (e.g., 404 if payment plan not found, 400 for bad request). Review the message and adjust inputs accordingly.
Links and References
- Partially API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance