Actions26
Overview
This node integrates with the Mercado Pago MCP (Mercado Pago Checkout Pro) API to manage various payment-related resources such as payments, orders, customers, preferences, webhooks, notifications, and documentation search. Specifically for the Preference - Get operation, it retrieves detailed information about a checkout preference by its ID.
Use cases include:
- Fetching checkout preference details to review or validate before processing payments.
- Integrating with Mercado Pago's checkout system to dynamically retrieve preference configurations.
- Automating workflows that depend on preference data, such as order fulfillment or customer notifications.
Example: You have created a checkout preference for a shopping cart and want to retrieve its current configuration and status to display or log it in your system.
Properties
| Name | Meaning |
|---|---|
| ID da Preferência | The unique identifier of the checkout preference to retrieve or update (e.g., "PREF123456789"). |
Output
The node outputs a JSON object containing:
type: A string indicating the type of response, here"preference_retrieved".preference: An object with the full details of the retrieved checkout preference as returned by the Mercado Pago API.success: Boolean flag indicating if the operation was successful (true).timestamp: ISO 8601 timestamp of when the operation was performed.pairedItem: Metadata linking the output to the input item index.
The structure of the preference object follows Mercado Pago's API schema for checkout preferences, typically including items, payer info, payment methods, back URLs, and other checkout settings.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for Mercado Pago MCP with access token and endpoint URL.
- Uses the Axios HTTP client to make REST API calls to Mercado Pago endpoints.
- The node expects proper configuration of credentials within n8n to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing preference ID will cause the API call to fail.
- Expired or incorrect API authentication token will result in authorization errors.
- Network connectivity problems can prevent reaching Mercado Pago servers.
Error messages:
"Card token is required for card payments"— not applicable for this operation but appears in payment creation.- API errors from Mercado Pago are propagated; check the error message for details like invalid ID or permission denied.
Resolutions:
- Verify the preference ID is correct and exists in your Mercado Pago account.
- Ensure the API credentials are valid and have necessary permissions.
- Check network access and proxy/firewall settings if requests fail.
Links and References
This summary focuses exclusively on the Preference - Get operation as requested.