Roboteka
Roboteka · Robots · HTTP request GET/POST

HTTP request GET/POST

The HTTP request robot sends a request to an external API from a business process. It accepts a URL, method (GET, POST, PUT, PATCH, DELETE, HEAD), request body, JSON headers, and timeout, and returns the response body, HTTP status code, and a success flag (Y/N). Works in Bitrix24 (Alaio) business processes and robots.

The robot performs an HTTP request to an external API directly from a Bitrix24 (Alaio) business process, with no code or intermediate services. It supports the GET, POST, PUT, PATCH, DELETE, and HEAD methods, an arbitrary request body, headers as JSON (e.g. Authorization), and a timeout from 1 to 60 seconds. Typical cases: send deal data to an external accounting system or request an order status from a delivery service API. Redirects (up to 5) are validated on every hop, requests to internal network addresses are blocked, and the response body is capped at 1 MB. Returns the response body, HTTP status code, and a success flag (Y/N): parse the response with the Extract value from JSON robot and build a condition on the flag in the workflow designer. Does not run while Bitrix24 is in demo mode.

What input parameters does the robot accept?

Parameter Type Required? Default
URL string yes
HTTP method (default GET) select GET, POST, PUT, PATCH, DELETE, HEAD — GET
Request body (for POST/PUT) string —
Headers as JSON: {"Authorization":"Bearer xxx","Content-Type":"application/json"} string —
Timeout in seconds (default 10) int —

What does the robot return?

Parameter Type
Response body string
HTTP status code int
Success (Y/N) — 2xx code string

What errors can the robot return?

The robot writes these messages to the business process log when it cannot complete a step. The text tells you what to fix in the settings or the data.

  • Error: method must be one of {methods}
  • Error: headers must be a JSON object
  • Error: invalid header name: {name}
  • Error: control characters are not allowed in header {name}
  • Error: header {name} is set automatically
  • cURL error: {error}
  • This robot does not run while Bitrix24 is in demo mode or if the plan could not be determined.

Scenario: request an order status from an external service

  1. A deal moves to the Delivery stage and triggers the robot
  2. The robot sends a GET request to the delivery service API with the order number
  3. The Extract value from JSON robot pulls the status from the response
  4. The status is written to a deal field for the manager

Related robots

Related articles

Install Describe a task — we build the robot for free