Actions26
Overview
This node integrates with the Mercado Pago MCP (Mercado Pago's API) to manage various resources such as payments, orders, customers, preferences, webhooks, notifications, and documentation searches. Specifically for the Customer - Update operation, it updates an existing customer's information in Mercado Pago by sending the updated data to the Mercado Pago API.
Typical use cases include:
- Keeping customer records up-to-date with their latest email, first name, or last name.
- Synchronizing customer data between your CRM or database and Mercado Pago.
- Automating customer profile updates after changes in your system.
Example: You have a customer who changed their email address or name, and you want to reflect this change in Mercado Pago automatically via n8n.
Properties
| Name | Meaning |
|---|---|
| ID do Cliente | The unique identifier of the customer to update. |
| The customer's email address. This is required for updating the customer. | |
| Primeiro Nome | The customer's first name. Optional field to update the first name. |
| Sobrenome | The customer's last name. Optional field to update the last name. |
Output
The node outputs a JSON object containing:
type: A string indicating the type of response, here"customer_updated".customer: An object representing the updated customer data returned from Mercado Pago.success: A boolean indicating if the operation was successful (true).timestamp: ISO string timestamp of when the operation was performed.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error message with success: false.
No binary data is output by this node.
Dependencies
- Requires an API key credential for Mercado Pago MCP with appropriate permissions.
- Uses the Mercado Pago REST API endpoint
https://api.mercadopago.com. - Requires network access to Mercado Pago's API.
- The node uses the Axios HTTP client internally to make API requests.
Troubleshooting
- Missing or invalid credentials: Ensure that the API key credential is correctly configured and has permission to update customers.
- Invalid customer ID: If the provided customer ID does not exist, the API will return an error. Verify the ID before updating.
- Required fields missing: The email field is mandatory; omitting it will cause an error.
- API rate limits or connectivity issues: Network problems or hitting API limits may cause failures.
- Error messages: Errors thrown by the node will include the API error message. Common errors include unauthorized access, resource not found, or validation errors on input fields.
To resolve errors:
- Double-check all required parameters.
- Confirm the API key is valid and active.
- Check the customer ID exists in Mercado Pago.
- Review the error message details for specific guidance.
Links and References
This summary focuses exclusively on the Customer - Update operation as requested.