AutomationBlocks
Flow Control Blocks
End the current run or stop other funnels for the chat.
Flow control blocks stop automation processing. Their position inside the step is important.
Stop Automation
Stop automation completes the current funnel run.
- Blocks above it in the same step can run.
- Blocks below it do not run.
- Outgoing triggers from that step do not continue the stopped run.
- Other funnels are not affected.
Place this block after the final message or update that the current funnel must complete.
Example order:
- Send text: confirmation.
- Add client tag:
completed. - Stop automation.
Stop Funnels
Stop funnels cancels active runs of selected other funnels in the same automation space for the current chat.
- Add the block.
- Select one or more funnels.
- Put the block before actions that assume those runs have been canceled.
The current funnel continues after this block unless it also reaches Stop automation. At least one other funnel must be selected. If no options are shown, the space has no other funnels available to stop.
Which Stop Block to Use
| Goal | Block |
|---|---|
| End only the funnel that is currently running | Stop automation |
| Cancel selected parallel runs but continue this funnel | Stop funnels |
| Cancel selected runs and then end this funnel | Stop funnels, followed by Stop automation |
Common Uses
- End a support intake flow after transferring the chat.
- Stop reminder funnels when the client completes the requested action.
- Cancel an older campaign funnel before starting a replacement path.
- Prevent blocks below a final decision from running.
Use clear funnel names so the selection in Stop funnels is unambiguous.