WorkflowsNode ReferenceWeb & HTTP

HTTP Request

View as Markdown

The HTTP Request node makes a call to an outside service and hands the response back to your workflow: the status code, the body, and the headers. It is the general-purpose way to talk to any system that has a web API, whether you are looking up a record, pushing an update, or triggering something elsewhere.

When to use it

  • You need to pull data from another system mid-run, such as a policyholder’s account details from your agency management system.
  • You want to send information out to a service, like posting a new record or kicking off a process in another tool.
  • You need to react to whatever the service returns, for example retrying, branching, or notifying someone when a call comes back with an error.

Inputs

FieldWhat it’s forExample
URLThe web address of the service you are calling.https://api.example-crm.com/v1/accounts/sarah-chen
HTTP MethodThe kind of call to make: get data, create, update, or delete.GET
HeadersExtra information sent with the request, such as an authorization token or the content type.Authorization: Bearer ...
Query ParametersValues added to the end of the URL to filter or shape what comes back.status = active
BodyThe data you send along, most often when creating or updating a record.A JSON record of the new contact

Any of these can be written as an expression so the call adapts to earlier steps, and secrets like API keys can be pulled in without hard-coding them (see Secrets).

Outputs

FieldWhat you get back
Status codeThe result code of the call. Codes in the 200s mean success; 400 and above mean the service reported a problem. A code of 0 means the request never reached the service at all.
Response bodyThe content the service sent back, usually a record or a message.
Response headersThe headers the service returned, such as content type or rate-limit hints.

Example

Marcus Johnson submits a new quote request. A workflow calls the agency’s management system to pull his existing account before deciding how to route the request. The HTTP Request node is set to GET the account URL, with an authorization token supplied from a secret. A later Conditional step reads the status code: if it comes back in the 200s the run continues with his account data, and if it comes back 404 the run branches to create a fresh contact instead.

The HTTP Request node configuration panel, showing the URL, HTTP method, and headers.

This node never stops the run on its own, even when a call fails. It always hands back a result so you stay in control. Follow it with a Check or Conditional that reads the status code, and treat 0 as “the service could not be reached.”

Web Search

Find pages on the public web instead of calling a known API.

Agent

Hand the response to an agent to summarize or pull out key fields.

Conditional

Branch the run based on the status code that came back.

Check

Turn the response into a single labeled outcome.