Documentation Index
Fetch the complete documentation index at: https://docs.docpipe.ai/llms.txt
Use this file to discover all available pages before exploring further.
This node is in beta. Its behavior may change in future releases.
When to use HTTP action
- You need to enrich an extracted record with data from your own backend, a CRM, or a public API mid-pipeline.
- You want to trigger an external workflow before continuing (create a ticket, post a notification, kick off downstream processing in another system).
- You need to fetch reference data that varies per run (a customer ID, a tax rate, a currency conversion) and feed it into a downstream transform or validation step.
- Use the callback output instead when the goal is just to deliver final results at the end of the run; HTTP action is for mid-pipeline calls whose response you’ll keep using.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| URL | text | Yes | The endpoint to call. Supports template expressions like {{steps.extract.data.id}} |
| Method | select | Yes | HTTP method: GET, POST, PUT, PATCH, or DELETE. Default: GET |
| Headers | key-value list | No | Custom headers to include in the request. Values support template expressions |
| Body format | select | No | JSON (default) sends the body as application/json. OData Batch sends a Business Central JSON $batch request with Isolation: snapshot. See the Business Central guide for the worked example |
| Body template | JSON editor | No | Request body for POST, PUT, and PATCH requests. Supports template expressions |
| Timeout | number | No | Request timeout in seconds. Default: 30 |
| Response path | string | No | Dot-path to extract a subset of the JSON response (e.g., data.results) |
| Response schema | schema editor | No | Define the expected response shape so downstream nodes can reference response fields |
Template expressions
The URL, headers, and body fields support template expressions using the{{expression}} syntax. This lets you dynamically build requests using data from upstream nodes.
Response path
If the API returns a large response and you only need part of it, use the response path to extract a subset. For example, if the response is{ "data": { "results": [...] } }, set the response path to data.results to pass only the array to downstream nodes.
Inputs and outputs
Allowed inputs: All trigger nodes and all action nodes. Output: The HTTP response with the following fields:| Field | Description |
|---|---|
| Status code | The HTTP response status code |
| Success | Whether the request completed successfully |
| Response body | The response body, or the extracted subset if a response path is configured |
| URL | The URL that was called |
| Method | The HTTP method that was used |
Related
Callback output
Send final results to a webhook after processing
Extract action
Extract structured data before or after HTTP calls
Transform action
Transform HTTP response data into a specific format
Webhooks and callbacks
Guide to working with external integrations