Actions26
Overview
This node integrates with the Mercado Pago MCP (Mercado Pago's API) to manage notifications among other resources. Specifically, for the Notification - Get operation, it retrieves detailed information about a notification using its unique notification ID received from a webhook.
Typical use cases include:
- Fetching detailed merchant order information when a notification is received.
- Automating workflows that react to payment or order notifications by retrieving full details for further processing.
- Monitoring and logging notification data for audit or customer service purposes.
For example, after receiving a notification ID from a webhook event, this node can be used to fetch the corresponding merchant order details to update an internal system or trigger additional actions.
Properties
| Name | Meaning |
|---|---|
| Notification ID | The unique identifier of the notification received from the webhook. This ID is required to retrieve the notification details. |
Output
The node outputs a JSON object containing:
type: A string indicating the type of response, here"notification_retrieved".notification: An object with the detailed data of the notification fetched from Mercado Pago's API.success: A boolean indicating if the operation was successful (true).timestamp: ISO 8601 timestamp of when the operation was performed.
Example output structure:
{
"type": "notification_retrieved",
"notification": {
/* Detailed notification data from Mercado Pago */
},
"success": true,
"timestamp": "2024-06-01T12:00:00.000Z"
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Mercado Pago MCP with appropriate permissions.
- The node makes HTTP requests to Mercado Pago's API endpoints.
- Proper configuration of the credential with access token and endpoint URL is necessary.
- Network connectivity to Mercado Pago's API servers is required.
Troubleshooting
- Missing or invalid Notification ID: The node requires a valid notification ID; ensure this is correctly passed from the webhook payload.
- Authentication errors: If the API key or access token is invalid or expired, the node will fail to authenticate. Verify credentials in n8n settings.
- Network issues: Connectivity problems may cause request failures. Check network access and proxy settings if applicable.
- API rate limits: Excessive requests might be throttled by Mercado Pago. Implement retry logic or reduce request frequency.
- Unexpected API responses: If Mercado Pago changes their API, the node might return errors or unexpected data. Keep the integration updated accordingly.
Common error messages usually relate to HTTP status codes like 401 Unauthorized (invalid credentials), 404 Not Found (invalid notification ID), or 429 Too Many Requests (rate limiting).