Why it matters
The Send HTTP Request action allows your AI agent to send data to an external system using an API call. This is useful for triggering webhooks, updating third-party systems, creating records in external platforms, or retrieving data.
Because this action interacts with external services, correct configuration and clear agent instructions are critical. Creating the tool alone is not enough. You must assign the tool to the agent and define exactly when and how the request should be sent.
Key Concepts
Action Tool: A tool created using the Execute Actions tool type that allows an agent to perform structured system actions such as sending HTTP requests, updating records, or triggering workflows.
Execute Actions Tool Type: A tool type that enables you to configure one or more actions inside a single tool. Multiple actions can run when the tool is triggered.
Send HTTP Request Action: An action that sends a GET or POST request to a specified URL endpoint when executed.
HTTP Method: The request type used when sending data. Available options are GET, typically used for retrieving data, and POST, typically used for sending data.
URL Endpoint: The destination URL where the request will be sent. This must be a valid HTTP or HTTPS address.
API Formatting: The structure and required parameters expected by the external system. Incorrect formatting may cause the request to fail.
Agent Instructions: The configuration where you define when the tool should be triggered, what data must be collected, and how the request should be structured.
Step-by-Step: Create a Send HTTP Request Action Tool
Navigate to Agents in the left-hand menu.
Click Tools (jigsaw icon).
Click Create Tool in the top right corner.
Select Execute Actions from the Tool Type dropdown.
Enter a Tool Name and click Save Tool.
Configure Basic Info
Enter the Label. Use only letters, numbers, underscores, or hyphens. Maximum 64 characters.
Add a clear Description explaining what the HTTP request does and when it should run.
Click Save.
Configure Tool Settings
Set the Timeout (milliseconds). Default is 5000 ms. Increase if the external system may take longer to respond.
Toggle Speak After Execution if the agent should confirm completion.
Toggle Speak During Execution if required.
Add execution speech if enabled.
Click Save.
Add the Send HTTP Request Action
In the Actions section, click Add Action.
Select Send HTTP Request from the Action Type dropdown.
Select the HTTP Method:
GET for retrieving data.
POST for sending data.
Enter the URL endpoint. This must be a valid HTTP or HTTPS URL, for example
https://api.example.com/webhook.Click Create Action.
When the tool is triggered, the request will be sent to the specified endpoint using the selected method.
You can add additional actions to the same tool if needed.
Implement the Tool in an Agent
Creating the tool does not automatically make the agent use it.
To implement it:
Open the relevant Agent.
Select the newly created Send HTTP Request tool to give the agent access.
Update the Agent Instructions to clearly define:
When the request should be sent.
What information must be collected from the contact.
How any required parameters should be formatted.
What should happen after the request completes.
You must both assign the tool to the agent and define its trigger logic in the instructions. If formatting or required parameters are not clearly defined, the request may fail.
Tips and Best Practices
Confirm the correct HTTP method with the external API documentation.
Verify the URL endpoint before saving.
Clearly define required data in the agent instructions.
Validate parameter formatting carefully.
Increase timeout if the external system responds slowly.
Test the integration in a controlled environment before deploying.
Troubleshooting
Issue | Possible Cause | Fix |
Request not sent | Tool not assigned to agent | Enable the tool in the agent settings |
Request failing | Incorrect URL or method | Verify endpoint and HTTP method |
External system not updating | Missing required parameters | Review API documentation and formatting |
Timeout error | External service too slow | Increase timeout setting |
Agent not triggering request | No clear instruction to use the tool | Update Agent Instructions with explicit conditions |