End Node

Loading node sections...

Overview

The End Node is used to stop the execution of a flow immediately. When the flow reaches this node, Lamatic skips any nodes that would execute after it and routes execution directly to the Final Trigger Response node.

Node Type Information

Type	Description	Status
Batch Trigger	Starts the flow on a schedule or batch event. Ideal for periodic data processing.	❌ False
Event Trigger	Starts the flow based on external events (e.g., webhook, user interaction).	❌ False
Action	Executes a task or logic as part of the flow (e.g., API call, transformation).	✅ True

This node is an **Action** node that immediately ends flow execution and jumps to the Final Trigger Response node.

Place an End Node on any branch where you want to stop early (for example, after a validation failure or a “no-op” condition). Any nodes connected after the End Node won’t run.

Features

Key Functionalities

Immediate termination: Stops the current execution path as soon as it’s reached.
Skip downstream execution: Prevents any nodes after the End Node from running.
Predictable exit point: Routes execution to the Final Trigger Response node to finish the run cleanly.

Benefits

Cost control: Avoid unnecessary model calls, API requests, or processing once a result is already decided.
Cleaner flow logic: Replace complex branching workarounds with a clear “stop here” node.
Safer automation: Prevent side effects (writes, sends, deletes) when a condition indicates execution should halt.

What Can You Build?

Guard rails / validation gates: End the flow when required inputs are missing or invalid.
Early return logic: Return a response when a cached result exists, without running the rest of the pipeline.
Conditional short-circuiting: Stop non-relevant branches (for example, when a user is not eligible for a path).

Setup

Add the End Node to the point in your flow where execution should stop.
Connect your branch/path into the End Node.
Ensure your flow has a Final Trigger Response node to produce the final output.
Deploy the project.

Configuration Reference

The End Node does not require configuration. Its behavior is defined by its position in the flow.

Low-Code Example

Stop execution on a condition

nodes:
  - nodeId: endNode_192
    nodeType: endNode
    nodeName: End
    values: {}
    modes: {}
    needs:
      - triggerNode_1
    allConfigs:
      Config A:
        nodeName: End
    schema: {}

Output

The End Node does not transform data. Its purpose is to terminate execution and pass control to the Final Trigger Response node.

Troubleshooting

Common Issues

Problem	Solution
Nodes after End Node still run	Ensure the path actually reaches the End Node (check connections and branch conditions).
No final response is returned	Confirm your flow includes a Final Trigger Response node and it is reachable after termination.
End Node placed but flow doesn’t stop	Verify you’re not executing a different branch/path that bypasses the End Node.

Debugging Tips

Use flow logs to confirm the End Node is reached on the expected path.
If you have multiple branches, add End Nodes only where you want early termination—other branches will continue unless they also end.