How to Use the Fork Node
The Fork Node helps you send randomized message variations in your WhatsApp automation.
This keeps your replies more natural and reduces the risk of being flagged for spam by avoiding repetitive patterns.
What Is the Fork Node?
The Fork Node in ChatDaddy’s Flow Builder splits your flow into multiple branches. Each time the flow runs, one branch is chosen at random, allowing different messages to be sent automatically and safely.
Benefits
Benefit | Description |
Natural Automation | Sends different messages each time, avoiding repetitive “bot-like” behavior. |
Lower Risk of Account Ban | Randomized messages lower the chance of WhatsApp account restrictions. |
How to Configure
- Open Message Flow
- Go to Automation → Message Flow.
- Create a new flow or edit an existing one where you want to add randomized messages.
- Add a Trigger Node
- Choose a trigger to start your flow.
- Example: Incoming message
- Add a Fork Node
- Click Choose Next Step → “Fork”.
- Enable Flow Forking
- Turn on “Enable Flow Forking”
- Set your numeric limits:
- The lower limit must be greater than 0.
- The upper Limit must be greater than the Lower Limit.
If the limits are invalid (for example, set to 0 or reversed), the flow will still run, but the message will fail. Check Flow Logs for a “Failed” status to troubleshoot.
- Add Conditions
- To make the randomizer work correctly, you need to set two conditions:
- Do you want to enable flow forking? → is true
- Selected Flow Number → choose the right operator and value
- Example Selected Flow Number is 3
💡 Tip: If you don’t see the option “Do you want to enable flow forking?”, first remove all existing conditions, then add a new one — it will appear correctly.
Available Operators:
- For Do you want to enable flow forking? → is / is not
- For Selected Flow Number → is / is not / is less than / is greater than / ≥ / ≤
If None Match: Used when no condition criteria are met — lets the flow continues with a default message instead of stopping.
- Add Messages
- Assign one message to each condition branch.
- Example:
- Condition 1 → “Hey there! How can I assist you today?”
- Condition 2 → “Hey there! What brings you here today?”
- Condition 3 → “Hello, Need any help?”
- Each time the flow runs, the system randomly selects one message.
- Check Flow Logs (if no message is sent)
- If your message is not delivered:
- Go to Flow Logs in the Automation panel.
- Look for the “Failed” status under the corresponding flow execution to identify configuration issues.
Example Use Case
When a user sends an incoming message, the flow uses a Fork Node to randomly send one of three replies:
- “Hey there! How can I assist you today?”
- “Hi! What brings you here today?”
- “Hello 👋 Need any help?”
📘 FAQ
Q: Why are my fork messages not sending?
A: Check that your lower/upper limits are valid (not 0 or reversed) and conditions are set using “is” logic.
Q: Can I use this to test different message versions?
A: Yes, it’s perfect for A/B-style random testing.
Q: What happens if no condition matches?
A: The system will continue with a default message (if you’ve set one).
Q: Is this feature safe to use for automated replies?
A: Yes. The Fork Node helps you rotate messages so they appear more natural and are less likely to trigger spam checks.