Configuration
| Setting | Description |
|---|---|
| URL | Target URL — supports Mentions for dynamic values (e.g., https://api.example.com/{{Salesforce.Account.Id}}) |
| Method | HTTP method: POST (default), GET, PUT, DELETE, or PATCH |
| Body | Request body as key-value pairs, sent as JSON — values support Mentions |
| Headers | Custom HTTP headers (e.g., Authorization, Content-Type) |
| Title | A human-readable description of the action |
How It Works
Choose the HTTP method
Select the appropriate method for your API (POST for creating, PUT for updating, etc.).
Output
The HTTP request is sent when the Agent runs. The response is logged in the task log.By default, all matching records are batched into a single request. To send one request per record, add a Group By node before this node, grouped by the primary key field.
Example
Trigger a webhook when new leads are created:- Filter for new leads
- Add an HTTP Request node
- URL:
https://hooks.example.com/new-lead - Method: POST
- Body:
name→{{Salesforce.Lead.Name}},email→{{Salesforce.Lead.Email}}
Best Practices
- Use Group By before this node for per-record requests
- Store API keys in headers rather than in the URL
- Test with a single record before enabling automatic execution
- Use POST for creating resources, PUT/PATCH for updating, DELETE for removing
Related Nodes
- Web Search — searches the web rather than calling a specific API
- Create Record — creates records using a native integration (no custom HTTP needed)