Actions26
Overview
This node integrates with the Mercado Pago MCP (Mercado Pago's API platform) to manage webhooks among other resources. Specifically, for the Webhook - Get operation, it retrieves detailed information about a specific webhook by its ID. This is useful when you want to verify the configuration or status of an existing webhook registered in your Mercado Pago account.
Common scenarios include:
- Auditing webhook configurations to ensure they are set up correctly.
- Fetching webhook details before updating or deleting them.
- Debugging webhook issues by inspecting their current settings.
Example: You have a webhook ID and want to retrieve its URL and subscribed events to confirm it matches your expected setup.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to retrieve. |
Output
The node outputs a JSON object containing the webhook details retrieved from Mercado Pago. The structure includes fields such as:
type: A string indicating the type of response, e.g.,"webhook_retrieved".webhook: An object with the webhook's data, typically including:id: The webhook ID.url: The endpoint URL configured for the webhook.events: An array of event objects the webhook listens to, each with atopicproperty.
success: Boolean indicating if the operation was successful.timestamp: ISO timestamp of when the response was generated.
Example output snippet:
{
"type": "webhook_retrieved",
"webhook": {
"id": "123456",
"url": "https://example.com/webhook-endpoint",
"events": [
{ "topic": "payment" },
{ "topic": "plan" }
]
},
"success": true,
"timestamp": "2024-06-01T12:00:00.000Z"
}
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for Mercado Pago MCP with appropriate permissions.
- Uses the Mercado Pago REST API endpoint
https://api.mercadopago.com/v1/webhooks/{webhookId}. - Requires network access to Mercado Pago's API.
- The node expects the credential to provide an access token used in the Authorization header.
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: Missing or invalid API credentials will cause authorization failures. Verify that the API key credential is valid and has necessary scopes.
- Network Issues: Connectivity problems can prevent reaching Mercado Pago's API. Check internet connection and firewall settings.
- API Rate Limits: Excessive requests may be throttled by Mercado Pago. Implement retries or backoff strategies if needed.
- Error Messages: The node throws errors with messages from the API or internal exceptions. Use the error message to diagnose issues; common messages include "Not Found" for invalid IDs or "Unauthorized" for credential problems.
Links and References
- Mercado Pago Webhooks API Documentation
- Mercado Pago Developer Portal
- n8n Documentation on Credentials
This summary covers the static analysis of the node’s execute method focusing on the Webhook resource and Get operation as requested.