Mercado Pago MCP icon

Mercado Pago MCP

Integração com MCP Server do Mercado Pago

Actions26

Overview

This node integrates with the Mercado Pago MCP (Mercado Pago's API) to manage webhooks among other resources. Specifically, for the Webhook - Delete operation, it allows users to delete an existing webhook by its ID. This is useful when you want to stop receiving notifications or events from a particular webhook endpoint.

Common scenarios include:

  • Removing obsolete or unused webhook endpoints.
  • Cleaning up webhooks after testing or migration.
  • Managing webhook lifecycle programmatically within automation workflows.

Example: You have a webhook set up to listen for payment events, but you no longer need it. Using this node operation, you can delete that webhook by providing its ID, ensuring no further notifications are sent to that URL.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook to delete. This is required to specify which webhook should be removed.

Output

The output JSON contains information about the deletion result:

  • type: A string indicating the type of operation, here "webhook_deleted".
  • webhook_id: The ID of the webhook that was deleted.
  • status: A string status, typically "deleted" confirming successful deletion.
  • success: Boolean flag indicating if the operation succeeded (true).
  • timestamp: ISO 8601 timestamp of when the operation was performed.

No binary data is output by this operation.

Example output JSON snippet:

{
  "type": "webhook_deleted",
  "webhook_id": "123456789",
  "status": "deleted",
  "success": true,
  "timestamp": "2024-06-01T12:00:00.000Z"
}

Dependencies

  • Requires an API key credential for Mercado Pago MCP with appropriate permissions to manage webhooks.
  • The node makes HTTP requests to the Mercado Pago API endpoint https://api.mercadopago.com/v1/webhooks/{webhookId} using the DELETE method.
  • Proper network connectivity and valid credentials are necessary.
  • No additional environment variables are explicitly required beyond the API authentication token.

Troubleshooting

  • Invalid Webhook ID: If the provided webhook ID does not exist or is malformed, the API will return an error. Ensure the webhook ID is correct.
  • Authentication Errors: If the API key or token is invalid or expired, the request will fail with an authorization error. Verify credentials in n8n.
  • Network Issues: Connectivity problems may cause timeouts or failures. Check your network and proxy settings.
  • Permission Denied: The API user must have permission to delete webhooks. Lack of permissions will cause errors.
  • Error Handling: If the node is configured to continue on failure, errors will be returned in the output JSON with success: false and an error message.

Links and References

This summary covers the static analysis of the node's execute logic for the Webhook resource's Delete operation based on the provided source code and property definitions.

Discussion