Actions2
- Custom API Call Actions
Custom API Call → Custom Request
AI-generatedSummary
Send a custom HTTP request with specified method, endpoint, and optional body, with GET/HEAD query conversion and pagination support.
Inputs
- method (required) — HTTP method for the request. One of: GET, POST, PUT, PATCH, DELETE. Defaults to GET.
- endpoint (required) — API endpoint URL. Defaults to /v3/api/tickets. Can include {{variable}} placeholders resolved from workflow data.
- bodyJson — Payload or query data as JSON. For GET/HEAD requests, sent as query parameters; for other methods, sent as JSON body. Defaults to {}.
- fetchAllPages — Automatically paginate GET/HEAD responses until the last page is reached. Defaults to false. Maximum 1000 pages.
Output shape
array
Each output item's json field contains the API response. If fetchAllPages is true and method is GET/HEAD, the array aggregates all items across all pages (up to 1000). Otherwise, a single response object is returned per execution.
Examples
Example 1: Single GET request
method=GET, endpoint=/v3/api/tickets, bodyJson={}, fetchAllPages=false
Example 2: Paginated GET request
method=GET, endpoint=/v3/api/tickets, bodyJson={}, fetchAllPages=true