Overview
This node integrates with Comercia.io to perform actions related to client management. Specifically, the "Crear cliente" (Create Client) operation allows users to create a new client account in Comercia.io by providing detailed client information.
Common scenarios where this node is beneficial include automating client onboarding processes, synchronizing client data from other systems into Comercia.io, or integrating Comercia.io client creation into broader workflows such as CRM updates or e-commerce order processing.
For example, when a new customer signs up on an e-commerce platform, this node can automatically create a corresponding client record in Comercia.io with all relevant details like contact info, fiscal data, payment methods, and shipping preferences.
Properties
| Name | Meaning |
|---|---|
| Nombre de la Cuenta | The name of the client account in Comercia. (Required) |
| Telefono | Client's phone number. |
| Primary email address of the client. | |
| Usuario Asignado | User assigned to manage the client account. Options are dynamically loaded from Comercia users. |
| Información del Cliente | Informational notice for client-related data (display only). |
| Nombre (Persona) | First name of the contact person. |
| Apellidos | Last name(s) of the contact person. |
| ID Lista de Precios | ID of the price list to assign to the client. |
| Descripción | Description or notes about the client. Supports multiline text. |
| Datos Fiscales Para Facturación | Informational notice regarding fiscal data for invoicing (display only). |
| Razón Social | Legal business name of the client. |
| RFC | Tax identification code (RFC) of the client. |
| CP del RFC | Postal code associated with the RFC. |
| Régimen Fiscal | Fiscal regime ID or key. |
| Método de Pago | Payment method. Options: "PUE |
| Forma de Pago | Form of payment. Multiple options including cash, check, electronic transfer, credit card, etc. |
| Uso de CFDI | Usage of the digital tax receipt (CFDI). Various predefined options indicating fiscal usage categories. |
| Configuración en Tienda | Informational notice about store configuration (display only). |
| Contraseña Tienda | Store password (masked input). |
| Tipo Pub.General | Boolean flag indicating general public type. |
| Envíos Disponibles | Multiple selectable shipping options such as Skydropx, Envia Ya, Lalamove, Shipstation, free shipping, etc. |
| Información Adicional | Additional informational notice (display only). |
| ID Carrito Predeterminado (TPV) | Default cart ID for point-of-sale system. |
| Límite de Crédito | Credit limit amount. |
| Días de Crédito | Number of credit days allowed. |
| Tarjeta de Puntos | Points card number associated with the client. |
| ID Tipo de Afiliado | Affiliate type ID. |
| ID Referido Por | ID of the account that referred this client. |
| Datos de Campaña | Campaign data string. |
| Suscrito a Mercadotecnia | Boolean indicating if the client is subscribed to marketing communications. |
| No Enviar Correos | Boolean flag to opt out from receiving emails. |
| Notificar al Propietario | Boolean flag to notify the owner about this client. |
| Timbre NdC Pendiente | Pending stamp note (multiline text). |
| ID Plantilla Adenda | Addendum template ID. |
Output
The node outputs JSON data containing the response from the Comercia.io API after attempting to create a client. The output includes:
- The full API response fields returned by Comercia.io.
- A metadata object
_metadatawith:operation: the operation performed ("createClient").timestamp: ISO timestamp of when the operation was executed.
If the operation is not implemented (e.g., creating addresses or shipments), it returns a JSON message indicating that the functionality is coming soon.
In case of errors, if the node is configured to continue on failure, the output will contain an error message and timestamp.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Comercia.io authentication.
- Needs network access to the Comercia.io API endpoint.
- The node dynamically loads user options from the Comercia.io users endpoint.
- Proper configuration of the API base URL and key is necessary in the credentials.
Troubleshooting
Common Issues:
- Invalid or missing API key credential will cause authentication failures.
- Network connectivity issues to Comercia.io API endpoints.
- Missing required parameters such as "Nombre de la Cuenta" will cause request errors.
- Incorrect IDs for price lists, users, or fiscal regimes may result in API errors.
Error Messages:
- Errors thrown during user loading indicate problems fetching users from the API; verify credentials and network.
- API request errors during client creation will return the error message from the API; ensure all required fields are correctly filled.
- If the node throws an error and is not set to continue on fail, the workflow execution will stop.
Resolutions:
- Verify and update the API key credential.
- Check required fields before executing the node.
- Ensure all referenced IDs exist in Comercia.io.
- Enable "Continue On Fail" in the node settings to handle errors gracefully.
Links and References
- Comercia.io official website: https://comercia.io
- Comercia.io API documentation (if publicly available)
- n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/