Actions13
Overview
This node integrates with the Polar.sh API to manage customers, products, and checkout sessions. Specifically for the Customer - Update operation, it updates an existing customer's details in the Polar system by sending a PATCH request with the specified fields.
Typical use cases include:
- Updating customer contact information such as email or name.
- Modifying billing address details.
- Changing tax ID or external/internal identifiers.
- Keeping customer records synchronized between Polar and other systems.
For example, you might update a customer's billing address after they move to a new location or correct their email address to ensure communications are sent correctly.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to update. |
| Update Fields | Collection of fields to update on the customer record. Includes: |
| Billing Address | Nested address fields including country (2-letter code), state, city, line 1, line 2, postal code. |
| Customer's email address. | |
| External ID | Internal customer ID used by your system. |
| Name | Customer's full name. |
| Tax ID | Customer's tax identification number. |
Output
The output is JSON data representing the updated customer object returned from the Polar API. It contains all the current customer details after the update.
If multiple input items are processed, the output will be an array of JSON objects, each corresponding to one updated customer.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Polar.sh API.
- The base URL switches between sandbox and production environments based on the configured environment credential parameter.
- Uses internal helper functions to make HTTP requests to the Polar API endpoints.
Troubleshooting
Common issues:
- Invalid or missing Customer ID will cause the API to return an error.
- Providing invalid field values (e.g., incorrect country code format) may result in validation errors.
- Network or authentication failures if the API key is incorrect or missing.
Error messages:
- Errors from the Polar API typically include a message and optional description. These are surfaced in the node output if "Continue On Fail" is enabled.
- To resolve errors, verify that the Customer ID exists, the API key is valid, and all required fields meet the expected formats.
Links and References
- Polar.sh API Documentation (general reference for API endpoints and data models)
- n8n Documentation (for general usage of custom nodes and credentials)