Mercado Pago MCP

Overview

This node integrates with the Mercado Pago MCP Server to manage orders and their transactions. Specifically, for the Order - Delete Transaction operation, it allows users to delete a specific transaction associated with an order by providing the order ID and the transaction ID.

Common scenarios where this node is beneficial include:

• Removing erroneous or duplicate transactions from an order.
• Managing order payment lifecycle by cleaning up unwanted transactions.
• Automating order transaction management in e-commerce workflows.

Practical example:

• An e-commerce platform detects a failed or duplicated payment transaction linked to an order and uses this node to delete that transaction programmatically, ensuring accurate order payment records.

Properties

Output

The output JSON object contains the following fields:

• type: A string indicating the type of operation result, here "transaction_deleted".
• order_id: The ID of the order from which the transaction was deleted.
• transaction_id: The ID of the deleted transaction.
• status: A string status confirming deletion, typically "deleted".
• success: A boolean indicating if the operation was successful (true).
• timestamp: ISO 8601 timestamp of when the operation was performed.

Example output JSON snippet:

{
  "type": "transaction_deleted",
  "order_id": "12345678",
  "transaction_id": "87654321",
  "status": "deleted",
  "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 authenticating with the Mercado Pago MCP API.
• Uses the Mercado Pago REST API endpoint for orders and transactions.
• Requires network access to https://api.mercadopago.com.
• The node expects proper configuration of the Mercado Pago API credentials within n8n.

Troubleshooting

• Common issues:

  • Invalid or missing order ID or transaction ID parameters will cause errors.
  • Insufficient permissions or invalid API credentials may lead to authentication failures.
  • Attempting to delete a non-existent transaction will likely return an error from the API.
  • Network connectivity issues can prevent communication with the Mercado Pago API.

• Error messages and resolutions:

  • "Card token is required for card payments" (not applicable here but common in related operations): Ensure all required payment tokens are provided.
  • "Issuer ID is required for card payments": Provide issuer ID if relevant.
  • API errors indicating "Not Found" or "Unauthorized": Verify that the order and transaction IDs exist and that the API credentials have appropriate permissions.
  • Timeout or network errors: Check internet connection and firewall settings.

• To handle errors gracefully, enable the node's "Continue On Fail" option to allow workflow continuation despite individual item failures.

Links and References

• Mercado Pago API Documentation
• Mercado Pago Orders API Reference
• n8n Documentation on Credentials
• Axios HTTP Client (used internally)