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 node outputs a JSON object with the following structure when deleting a transaction:

{
  "type": "transaction_deleted",
  "order_id": "<ID do Pedido>",
  "transaction_id": "<ID da Transação>",
  "status": "deleted",
  "success": true,
  "timestamp": "<ISO 8601 timestamp>"
}

Explanation:

• type: Indicates the type of operation performed ("transaction_deleted").
• order_id: The ID of the order from which the transaction was deleted.
• transaction_id: The ID of the deleted transaction.
• status: Confirmation status of the deletion ("deleted").
• success: Boolean indicating if the operation succeeded.
• timestamp: The time when the operation was completed.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating with the Mercado Pago MCP API.
• The node makes HTTP DELETE requests to the Mercado Pago API endpoint:
  https://api.mercadopago.com/v1/orders/{orderId}/transactions/{transactionId}
• Proper configuration of the API authentication token (access token) is necessary.
• The node uses the Axios HTTP client internally to perform API calls.

Troubleshooting

Common Issues

• Invalid or missing order ID or transaction ID:
  The operation requires both IDs to be valid and existing in Mercado Pago. Providing incorrect IDs will result in errors.

• Authentication errors:
  If the API key or access token is invalid or expired, the request will fail with authorization errors.

• Network or connectivity problems:
  Failure to reach the Mercado Pago API endpoint due to network issues will cause the node to error out.

Common Error Messages and Resolutions

• "Unauthorized" or "Invalid access token":
  Verify that the API credentials are correctly configured and have not expired.

• "Not Found" or "Resource does not exist":
  Check that the provided order ID and transaction ID are correct and exist in your Mercado Pago account.

• "Bad Request":
  Ensure all required parameters are provided and formatted correctly.

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

Links and References

• Mercado Pago API Documentation - Orders
• Mercado Pago Developer Site
• Axios HTTP Client