Send pop-up
Step · Stable
Show an ephemeral in-app modal readout to the person running the flow.
Surfaces a modal readout on the canvas when the run reaches this step. title and body accept Jinja2 templates and are resolved against the run context. The pop-up is shown only to the actor currently watching the run — it is ephemeral and does not persist in the bell panel or database. An optional attachment field names an earlier step (e.g. Storage read) whose fetched file renders inline in the pop-up.
When to use
Section titled “When to use”Use to surface a quick result or diagnostic value you want to eyeball while watching a flow run — e.g. “Počasí: {{ weather.temp_now }} °C” or ”{{ extraction.summary }}”. Ideal for debugging intermediate values or presenting a computed result inline without leaving the canvas.
When not to use
Section titled “When not to use”If the message must persist or reach someone not currently watching the run, use Send notification (bell panel) or Send email. For a lasting alert visible in the bell after the run finishes, use Send notification.
Inputs
Section titled “Inputs”string · required
Short headline shown at the top of the pop-up. Jinja2 templates resolved against run context.
Example: Výsledek dotazu
- ✓
Výsledek hotov— literal headline - ✓
Počasí: {{ weather.temp_now }} °C— templated headline
string · optional
Optional detail shown below the title. Templates resolve against the run context. Structured values (dict/list) are pretty-printed as JSON.
Example: {{ extraction.summary }}
- ✓
{{ weather.report }}— reuse a prepared body - ✓
{{ results | tojson }}— pretty-print a structured value
attachment
Section titled “attachment”string · optional
Optional. NOT a general template — type the label of an earlier step whose output includes a file (e.g. Storage read). The pop-up renders that file’s content inline (text/image/PDF) instead of just its templated fields. For a switch/case fan-in where only one of several branches actually ran, use first_defined(a, b, c) / last_defined(a, b, c) over the candidate step labels.
Example: read_step
- ✓
read_step— shows the file fetched by the step labeled ‘read_step’ - ✓
{{ first_defined(storage_read2, storage_read3, storage_read4) }}— picks whichever of these switch-branch steps actually ran - ✗
{{ read_step.file_path }}— a file_path string, not a step label, cannot be served — reference the step label itself
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.