Actions26
Overview
This node integrates with the Mercado Pago MCP (Mercado Pago's API) to manage customers, payments, orders, preferences, webhooks, notifications, and documentation searches. Specifically for the Customer - Get operation, it retrieves detailed information about a customer by their unique ID.
Typical use cases include:
- Fetching customer details to display or process in workflows.
- Integrating customer data retrieval into payment or order processing flows.
- Synchronizing customer information between Mercado Pago and other systems.
Example: You have a customer ID from a previous step or external source, and you want to retrieve that customer's profile information such as email, first name, and last name to personalize communications or verify identity.
Properties
| Name | Meaning |
|---|---|
| ID do Cliente | The unique identifier of the customer to retrieve. This is required for the "Get" and "Update" operations on the Customer resource. Example: "123456789". |
Output
The node outputs a JSON object containing the retrieved customer data under the customer key. The output structure includes all customer details returned by the Mercado Pago API for the specified customer ID.
Example output JSON structure:
{
"type": "customer_retrieved",
"customer": {
"id": "123456789",
"email": "cliente@exemplo.com",
"first_name": "João",
"last_name": "Silva",
// ... other customer fields as provided by Mercado Pago
},
"success": true,
"timestamp": "2024-06-01T12:00:00.000Z"
}
No binary data is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access Mercado Pago MCP endpoints.
- Uses the Mercado Pago REST API endpoint
https://api.mercadopago.com/v1/customers/{customerId}to fetch customer data. - Requires network connectivity to Mercado Pago's API servers.
Troubleshooting
Common issues:
- Invalid or missing customer ID will cause the API call to fail.
- Expired or invalid API token will result in authentication errors.
- Network issues may cause request timeouts or failures.
Error messages:
"Card token is required for card payments"or"Issuer ID is required for card payments"are specific to payment operations and not relevant here.- For customer get operation, typical errors relate to HTTP 401 Unauthorized (invalid credentials) or 404 Not Found (customer ID does not exist).
Resolution tips:
- Verify the customer ID is correct and exists in Mercado Pago.
- Ensure the API credential is valid and has necessary permissions.
- Check network connectivity and retry if transient errors occur.
- Use the "Continue On Fail" option in n8n to handle errors gracefully in workflows.