Actions26
Overview
This node integrates with the Mercado Pago MCP (Mercado Pago Cloud Platform) API, providing various operations across multiple resources such as payments, orders, customers, preferences, webhooks, notifications, and documentation. Specifically for the Documentation - Search operation, it allows users to search Mercado Pago's official documentation by submitting a query string and selecting a language.
Common scenarios where this node is beneficial include:
- Automating retrieval of relevant Mercado Pago documentation snippets or articles based on user queries.
- Integrating documentation search into workflows to assist support teams or developers in quickly accessing help content.
- Building custom help or FAQ systems that dynamically fetch Mercado Pago documentation content.
Practical example:
- A workflow triggers when a user submits a question about "Como integrar Checkout Pro" (How to integrate Checkout Pro). This node searches the Mercado Pago documentation in Portuguese and returns relevant results to guide the user.
Properties
| Name | Meaning |
|---|---|
| Query | The search term or phrase to look up in Mercado Pago documentation. |
| Language | The language in which to perform the documentation search. Options: Português, English, Español. |
Output
The node outputs JSON data containing the search results from Mercado Pago documentation. The output structure includes:
query: The original search term used.language: The language selected for the search.result: The raw result data returned by the Mercado Pago MCP API for the documentation search.type: A string identifier"documentation_search"indicating the type of response.
Example output snippet:
{
"query": "Como integrar Checkout Pro",
"language": "pt",
"result": { /* Mercado Pago documentation search results */ },
"type": "documentation_search",
"success": true,
"timestamp": "2024-06-xxTxx:xx:xx.xxxZ"
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Mercado Pago MCP with access to the MCP Server endpoint.
- Uses the Axios HTTP client library to make POST requests to the Mercado Pago MCP API.
- The node expects the credential to provide:
- An MCP endpoint URL.
- An access token for authorization.
- The request is made with JSON-RPC 2.0 format to the MCP server.
Troubleshooting
Common issues:
- Invalid or expired access token: The API call will fail with authorization errors. Ensure the API key credential is valid and has proper permissions.
- Network connectivity problems: The node requires internet access to reach Mercado Pago MCP endpoints.
- Empty or invalid query parameter: The node requires a non-empty search query; otherwise, the API may return no results or errors.
Error messages:
- Authorization errors typically indicate issues with the provided API token.
- Validation errors if required parameters like
queryare missing. - JSON parsing errors if the API response is malformed (rare).
Resolutions:
- Verify and refresh the API credentials.
- Confirm the query string is correctly set and not empty.
- Check network connectivity and proxy settings if applicable.
Links and References
If you need summaries for other resources or operations, please provide their names.