

Webhook - HTTP Request
Core Utility
Available ActionsEach successful request consumes credits as outlined below.
request5cr
Details
A flexible and secure HTTP client designed for agent-driven API integrations and web service interactions. This function supports all standard HTTP methods including GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS, enabling comprehensive RESTful API communication. Users can configure requests with custom headers, query parameters, and request bodies in JSON, plain text, or base64-encoded binary formats. The tool provides four authentication modes: none for public endpoints, basic for username/password credentials automatically encoded to Base64, bearer for OAuth-style token authentication, and header for custom API key or signature-based authentication schemes. Built-in security features include URL validation that blocks private and loopback IP addresses by default (configurable via allow_private), configurable timeouts from 1 to 120 seconds, and response size limits up to 20MB to prevent memory issues. Response handling offers four modes—auto, json, text, and base64—with auto-detection intelligently parsing responses based on content-type headers. The function returns comprehensive response metadata including status code, headers, final URL after redirects, and the parsed body, making it an essential building block for workflows that need to interact with external APIs, webhooks, or web services.
Use Cases
Fetching data from third-party REST APIs for aggregation or transformation pipelines, submitting form data or JSON payloads to webhook endpoints for event-driven workflows, authenticating with OAuth-protected services using bearer tokens for secure integrations, polling external services for status updates or job completion in asynchronous workflows, posting structured data to CRM or marketing automation platforms, retrieving remote configuration files or feature flags from external services, sending notifications to Slack or Discord webhooks with custom message payloads, interacting with payment gateways or e-commerce APIs for order processing, fetching remote JSON schemas or API specifications for validation workflows, integrating with legacy systems via custom header-based authentication for enterprise data exchange
Actions(1)
request5cr17 params(1 required)Make an HTTP request to a specified URL. Supports all standard HTTP methods, multiple authentication schemes, and flexible body/response formats.
request5cr17 params(1 required)Make an HTTP request to a specified URL. Supports all standard HTTP methods, multiple authentication schemes, and flexible body/response formats.
urlrequiredstringThe full URL to send the request to (must be http or https).
request_methodstringHTTP method to use.
Values:
GETPOSTPUTPATCHDELETEHEADOPTIONS
Default:
GETheadersobjectCustom HTTP headers as key-value pairs.
query_paramsobjectURL query parameters as key-value pairs.
body_jsonobjectJSON object body. Sets Content-Type to application/json automatically. Only one body type allowed per request.
body_textstringPlain text body payload. Only one body type allowed per request.
body_base64stringBase64-encoded binary body payload. Only one body type allowed per request.
auth_typestringAuthentication scheme to use.
Values:
nonebasicbearerheader
Default:
noneauth_usernamestringUsername for basic authentication. Required when auth_type is basic.
auth_passwordstringPassword for basic authentication. Required when auth_type is basic.
auth_tokenstringBearer token for authentication. Required when auth_type is bearer.
auth_header_namestringCustom header name for header-based authentication. Required when auth_type is header.
auth_header_valuestringCustom header value for header-based authentication. Required when auth_type is header.
timeout_secondsintegerRequest timeout in seconds.
Default:
30Range: 1 - 120
response_modestringHow to return the response body. Auto detects based on Content-Type.
Values:
autojsontextbase64
Default:
automax_response_bytesintegerMaximum response size to return in bytes.
Default:
1048576Range: 1024 - 20971520
allow_privatebooleanSet to true to allow requests to private or loopback IP addresses.
Default:
falseFrequently Asked Questions
How do I connect this tool to an external agent?
You can install the local MCP server by opening a terminal and running:
Install commands
npm install -g @agentpmt/mcp-router
agentpmt-setupThis will connect you to local agents like Claude Code, Windsurf, Grok Build, Cursor, etc.
Alternatively you can connect to the hosted version with this config block, no installation required:
Hosted MCP config
{
"mcpServers": {
"agentpmt": {
"type": "streamable-http",
"url": "https://api.agentpmt.com/mcp",
"headers": {
"Authorization": "Bearer <AGENTPMT_BEARER_TOKEN>",
"x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}"
}
}
}
}View MCP Connection Instructions for more details.
How does an external agent use this tool?
After the external agent is connected to an Agent Group that can use this tool, paste this prompt into the agent:
Agent prompt
Call the AgentPMT-Tool-Search-and-Execution tool with action 'get_schema' and tool_id 695c37c5767df5adfd9bc873 ("Webhook - HTTP Request"). Then call the same tool with action 'call_tool', tool_id 695c37c5767df5adfd9bc873, and the parameters needed for my request.
The agent should fetch the tool schema first, collect the required parameters for your request, and then call the tool through AgentPMT.







