Actions26
- Product Actions
- Order Actions
- Customer Actions
- Category Actions
- Stock Actions
Overview
This node integrates with the PrestaShop API to manage customer data. Specifically, the Delete Customer operation removes a customer from the PrestaShop store by their unique ID. This is useful in scenarios where you need to automate customer management tasks such as cleaning up inactive or fraudulent accounts, or synchronizing customer records between systems.
Practical examples:
- Automatically deleting customers who have requested account removal.
- Removing test or dummy customer accounts after QA processes.
- Syncing deletions from an external CRM system into PrestaShop.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique numeric identifier of the customer to delete. Must be a positive integer (minimum 1). |
| Advanced Options | A collection of optional settings to customize the request: |
| - Output Format | Choose response format: JSON (recommended) or XML. |
| - Language ID | Numeric ID to filter localized fields by language (default is 1). |
| - Display Fields | Control which fields are returned in the response: Full (All Fields) or Custom Fields. |
| - Custom Fields | If "Custom Fields" is selected, specify a comma-separated list of fields to return (e.g., "id,name,price,reference"). |
| - Shop Context | Define the shop context for multishop environments: All Shops, Specific Shop, or Shop Group. |
| - Shop ID | If "Specific Shop" is chosen, provide the numeric ID of that shop (minimum 1). |
| - Shop Group ID | If "Shop Group" is chosen, provide the numeric ID of that shop group (minimum 1). |
| - Enable Debug Mode | Enable debug information in the response, including URL, method, and parameters used, to assist troubleshooting. |
Output
The node outputs the result of the delete operation in the specified format (JSON by default). The main output is a JSON object containing details about the deletion status, such as success confirmation or error messages.
If debug mode is enabled, additional metadata about the HTTP request (URL, method, parameters) will be included in the output to help diagnose issues.
No binary data is produced by this operation.
Dependencies
- Requires connection to a PrestaShop instance via its REST API.
- An API key credential must be configured in n8n to authenticate requests.
- The node depends on the PrestaShop API being accessible and properly configured to allow customer deletions.
- Multishop contexts require correct shop or shop group IDs if used.
Troubleshooting
Common issues:
- Invalid or missing Customer ID: Ensure the Customer ID is provided and is a positive integer.
- Insufficient permissions: The API key must have rights to delete customers.
- Incorrect shop context: When using specific shops or groups, verify the IDs are valid.
- Network or connectivity problems with the PrestaShop API endpoint.
Error messages:
"Customer not found": The specified Customer ID does not exist."Unauthorized"or"Forbidden": Check API credentials and permissions."Invalid shop context": Verify shop or shop group IDs."API request failed": General failure; enable debug mode to get detailed request info.
Enabling debug mode can provide detailed request and response data to help identify the root cause of errors.