Send to a URL

Post the result to a webhook, an automation, or your own API. Only public addresses.

What it does

Posts the result to an address you choose — a webhook, an automation, or the client's own system. It is the escape hatch: when a business already has software that should hear about something, this hands it over rather than asking them to check a screen.

What you need

Nothing. This one runs on RAiN — no key, no account, no per-use cost from the provider.

Connecting it

Nothing to connect. It is available to every project already — tick it on an agent, or choose it in an Action step.

Using it in a step

An Action step runs one tool with the arguments you type, exactly as written, with no model involved — so it costs nothing per run and behaves the same every time. Add one from the canvas toolbar, choose Send to a URL, and fill in:

Field	Required	What goes in it
`url`	yes	A public https address — a webhook, an automation, the client's own API.
`body`	yes	What to post, as text or JSON.

Values can carry results forward: {{previous}} is the step before, and {{row:column}} is a column from the row this run is about when the trigger fans out.

Press Try it to run the step on its own before committing to a whole sequence.

This one really sends. Trying it delivers a real message — use your own address or number, never a customer's.

Using it with an agent

Tick Send to a URL on any agent that should be able to call it, and the agent decides when to. Use an agent when the judgement matters and an Action step when the certainty does.

A worked example

A logistics company already runs a dispatch board. When an agent decides a delivery is late, this posts the order id and the reason to their board's webhook, and the board shows it beside the driver's name within seconds.

When it goes wrong

It refuses a private address. Only public URLs are allowed. localhost, 10.x and 192.168.x are the runtime's own network, not the client's, and posting there would either fail or reach something it should not.