Control the run
Respond
Answers the caller of the webhook or API operation that started the run, while the run goes on.
Nodes › LogicOpen in Neblex
- Good for
- Answering early
- Role
- Works on the records in a flow
- Find it in
- Nodes › Logic
When to use it
- The caller should get an answer before slow work finishes.
- The answer needs its own status and headers, such as 202 Accepted.
- The rest of the flow should keep running after answering.
Reach for something else when
Example
Accept an order, answer 202 with the order number, then create it in the ERP.
How it works
- Settings
- Status; Headers, one
Name: valueper line. - Output
- Its records, unchanged; they are also the body of the answer.
- Behaviour
- The first Respond step that records reach answers, wherever it is in the flow; the caller does not wait for the steps after it. Example: accept an order, answer
202with the order number, then create it in the ERP.
Add it to a flow
- Open the flow from Build › Workflows.
- Open Nodes and find Respond under Logic, or search for it. Click it or drag it onto the canvas.
- Drag from the previous step's output handle to its input, then open its settings with ✎ Edit.
- Run the flow and click the step to see the records it received and produced.
More in Control the run
LoopRepeats a group of steps for each record, a set number of times, or while or until a condition holds.Nodes › LogicRun another flowRuns another flow as a reusable sub-flow and continues with its result.Nodes › LogicWaitPauses for a set time before passing records on.Nodes › LogicWait for eventPauses the run until a matching event arrives, then continues with its data.Nodes › LogicSet valueSaves a named value that later steps in the same run can read.Nodes › LogicAssert Data QualityChecks the batch against your rules and stops with precise details when one fails.Nodes › Logic