Home
/
Glossary
/
HTTP request action

HTTP request action

Definition

An HTTP request action is a scenario step that calls an outside URL mid-flow, filling contact details into the URL and body, then branching on whether the call succeeded. In Inrō it is called Send HTTP request.

An HTTP request action is a scenario step that calls an outside URL in the middle of your Instagram DM flow. In Inrō it is called Send HTTP request: it fills contact details into the URL and body, sends the call, then branches on the answer. The Free plan skips it; Pro and the Pro trial run it.

What can an HTTP request send?

You pick the method: GET, POST, PUT, PATCH or DELETE. Then you set:

  • the URL, which can hold variables such as {{contact.username}}, filled in for each contact
  • headers, as key and value pairs, for example the API key your service asks for
  • a body, for any method but GET, as Key / Value pairs or raw JSON, both with variables

In JSON mode, Inrō adds Content-Type: application/json unless you set your own.

Typical uses: push a new lead to your CRM, or check a contact against your own backend before you send a link. The tools Inrō connects to are on Inrō integrations, and the Make integration use case shows one end to end.

What happens when the request succeeds or fails?

The step has two branches:

  • If request is successful: the service answered with a 2xx status.
  • If request fails: the service answered with an error status, or the request timed out.

Connect both. A failure branch that moves the contact into a folder gives you a list to check by hand.

Inrō saves the request and the response (status, headers and body) on the run. Open the run and click View details to see them. Run again resends a request that completed.

How do later steps use the response?

Later steps in the same run read {{http_request.response.body}}, the whole body. When the service answers in JSON, Inrō parses it, so one field reads as {{http_request.response.body.id}}. If the run made several requests, the variable holds the most recent one.

To keep a value on the contact as a contact property, add an Update contact property step after it and put the response variable in its value.

How is it different from a webhook?

They point in opposite directions:

  • Send HTTP request: Inrō calls your URL, in the middle of a flow.
  • Webhook is called: a trigger. Your site or tool sends a POST to a URL Inrō gives you, and that starts a scenario.
  • Instagram webhook: what Meta sends Inrō when a DM or comment arrives on your account (see how an Instagram webhook works).

To read or change Inrō data from your own code instead, use the Inrō API for developers, or connect an AI assistant through the Inrō MCP server. For more terms, see the Inrō automation glossary.

Try Inrō and leverage the power of Instagram marketing automation

Attract more leads, target them with DM marketing, and automate all your interactions on Instagram!

Free plan available
Meta Tech Provider
Setup in 5 minutes