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 to manage customer data and related payment plan entities. Specifically, for the Customer - Get operation, it retrieves detailed information about a specific customer by their unique Customer ID.
Common scenarios where this node is beneficial include:
- Fetching customer details to display or process in workflows.
- Verifying customer existence before creating or updating payment plans.
- Integrating customer data retrieval into automated billing or support processes.
Example:
You have a workflow that triggers when an order is placed, and you want to fetch the customer's profile from Partially to personalize communications or check their payment plan status.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the retrieved customer data as returned by the Partially API. This typically includes fields such as the customer's email, first name, last name, and any additional metadata associated with the customer.
The output is structured as an array of JSON objects (one per input item), each containing the full customer record under the json property.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Partially Payment Plans API.
- Needs an API authentication token configured in the node's credentials to authorize requests.
- The node uses internal helper functions to make HTTP requests to the Partially API endpoints.
Troubleshooting
- Missing or invalid Customer ID: The operation requires a valid Customer ID. Ensure the ID is correctly provided and exists in the Partially system.
- Authentication errors: If the API key or token is missing or invalid, the request will fail. Verify that the API credentials are correctly set up in n8n.
- Network or API downtime: Connectivity issues or Partially API outages can cause request failures. Check network connectivity and Partially service status.
- Unexpected response format: If the API changes its response structure, the node might not parse the data correctly. Keep the node updated with the latest version.
Links and References
- Partially Payment Plans API Documentation (Assumed URL; replace with actual if known)
- n8n Documentation on Creating Custom Nodes