Actions16
Overview
This node allows creating a new customer record in the connected system. It is designed to facilitate adding customer information such as name, type (person or company), contact details, and address data. This node is useful in scenarios where you want to automate customer onboarding, synchronize customer data from other systems, or programmatically manage customer records.
For example, you could use this node to:
- Automatically create a customer profile when a new user signs up on your platform.
- Import customer data from a CRM or spreadsheet into your commerce system.
- Enrich customer records with additional metadata like tax IDs or external references.
Properties
| Name | Meaning |
|---|---|
| Name | The full name of the customer to be created. |
| Type | The category of the customer: either "Person" or "Company". |
| Contact | Contact information for the customer, including: |
| - Email (required): Email address of the contact person. | |
| - First Name: First name of the contact person. | |
| - Last Name: Last name of the contact person. | |
| - Phone: Phone number of the contact person. | |
| Address | Address details for the customer, including: |
| - Address Line 1 (required): Primary street address. | |
| - Address Line 2: Secondary address line (e.g., suite or apartment). | |
| - City (required): City name. | |
| - State: State or province name. | |
| - Postal Code (required): ZIP or postal code. | |
| - Country (required): Country name. | |
| Additional Fields | Optional extra fields to provide more context about the customer: |
| - Description: Text description of the customer. | |
| - External ID: An external reference identifier for the customer. | |
| - Tax ID: Tax identification number associated with the customer. |
Output
The node outputs an array of JSON objects representing the newly created customer(s). Each output item contains the full customer data as returned by the underlying API after creation, including all submitted fields and any additional metadata assigned by the system.
If the node supports binary data output (not indicated here), it would typically represent attachments or documents related to the customer, but this node focuses on JSON data only.
Dependencies
- Requires connection to the target commerce or customer management API via an initialized API service.
- Needs proper authentication credentials configured in n8n to authorize API requests.
- Relies on a resource registry mechanism internally to resolve and execute resource-specific operations.
Troubleshooting
- Resource Not Found Error: If the specified resource ("customer") is not recognized, ensure that the node's configuration includes the correct resource name and that the integration supports it.
- API Authentication Failures: Verify that the API key or authentication token is correctly set up in n8n credentials and has sufficient permissions to create customers.
- Validation Errors: Required fields such as "Name", "Email" in contact, and address components must be provided; missing these will cause errors.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON for failed items.