Module · Replying and messaging✅Knowledge checkCheck: saying something back4 questions · Pass at 60%1. You write {{#if deals}}…{{else}}…{{/if}} in a Text Response. The node documents it and implements it. What does a customer receive in a real run?The correct branch, evaluated by the node as it runsBoth branches at once, the engine having resolved it firstAn error naming the directive as unsupported in this fieldThe raw {{#if}} text, passed through entirely unprocessed2. So how should a reply that differs by value be built?A Condition node, with its own message on each branchA longer prompt telling the model which case appliesTwo Text Response nodes, letting the second overwrite the first{{#each}}, which is unaffected because it loops rather than branches3. A WhatsApp Question is configured with a timeout of 0. What does that mean?The question is asked and the workflow moves straight past itThe node falls back to the organisation's default timeoutWait forever — abandoned conversations never finishThe question is skipped once the 24-hour window has closed4. A Campaign Send node reports a green run. What tells you whether anyone was actually mailed?That node's output in the execution log, which lists recipientsThe campaign's own record — its recipients and its sendsThe node's success flag, which is set only after deliveryThe email integration's log, the only fully reliable sourceCheck answers← Back to Actions — making things happenNext topic →
