Output
REST API Output
Sends the rows to an API or webhook as JSON — in batches as arrays, or one request per row — with bearer, basic or custom-header authentication.
When to use it
Use it to push results into another system that has an HTTP API: a CRM, a ticketing tool, a webhook receiver.
In a pipeline
File InputFilter RowsREST API Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Address | text | Yes | https://api.example.com/orders |
| Method | select | — | post |
| Send | select | — | array |
| Rows per request | number | — | 100 |
| Authentication | select | — | none |
| Token / credentials | password | — | $ApiToken |
| Extra headers (JSON) | textarea | — | {"X-Source": "FlowDoo"} |
| Add an HTTP Status column | checkbox | — | false |
Example
POST each batch to a webhook
- Address=https://api.example.com/orders
- Send=Rows in batches (JSON array)
- Rows per request=100
| Order | Amount |
|---|---|
| A-1041 | 1240 |
| A-1042 | 860 |
| Order | Amount |
|---|---|
| A-1041 | 1240 |
| A-1042 | 860 |
Worth knowing
- Previews never send: they show the requests that would go out, without the auth header.
- Any reply outside 2xx stops the node with the status and the start of the reply, and says whether earlier requests had already gone.
- Put the token in a $Variable rather than typing it, and keep the flow private.
- Internal __ columns are never sent.