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.
You pick the method: GET, POST, PUT, PATCH or DELETE. Then you set:
{{contact.username}}, filled in for each contactIn 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.
The step has two branches:
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.
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.
They point in opposite directions:
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.
Attract more leads, target them with DM marketing, and automate all your interactions on Instagram!

