Skip to content

Sending results onward (Send to a URL)

Finish a flow by POSTing each item's result to Slack, Zapier, n8n or your own backend — as JSON, with links to the generated files, no sign-in needed.

In this article (5)

A batch that finishes inside FlowArray still needs someone to go and look at it. A Send to a URL card closes the loop: the results arrive where your team already is.

Setting it up

Add the card (it is under Output, and a quick-add in Simple view) and paste a URL. Point it at:

  • a Slack, Discord or Teams incoming webhook,
  • a Zapier / Make / n8n hook,
  • or your own backend endpoint.

No OAuth, no connector to install. Leave the message blank to send the previous step's text, or write one using {previous.text}, {item.<column>} and {step.<label>.text}. Add custom fields if your receiver expects a particular shape.

What arrives

One POST per item, as JSON: the text, absolute links to any generated images or videos, and your custom fields. Absolute links matter — the receiving system can fetch the file without being signed in to FlowArray.

The guardrails

  • The URL is treated as a secret: masked as you type, and stripped out of exported workflow files.
  • Public addresses only. Internal, loopback and private-network addresses are refused, and redirects are not followed — a webhook URL should not be a way to probe the inside of the network.
  • Retries are off by default. A POST that was delivered may already have had an effect; sending it twice is worse than sending it once.
  • Keyless and $0 — no provider call is involved.

When this is not enough

For the full Slack, Drive or Gmail APIs — posting a file into a channel, uploading to a folder — connect an MCP server and use a Call a tool step instead. A webhook is for "here is the result"; a tool call is for "do this specific thing in that product".

The other two ways results leave

  • After the fact: the Library can send an individual output, or a multi-selection, to a URL.
  • Run outcomes rather than results: notifications can POST a run summary (which run, which flow, succeeded/failed, cost, link) to a URL of yours, optionally signed.