n8n WhatsApp Trigger test step waits and never runs

Test record: run by Fractional HQ on 11 November 2026 on self-hosted n8n 2.23.4. Phone steps are executions 94091 to 94109 in webhook mode. Replays are executions 94117 to 94165 in manual mode. The attempt with the workflow off was made at 12:38. Not tested: n8n Cloud, a test run completing once a message arrives. One phone step produced no execution and the cause was not found.

Symptom

On 11 November 2026, on self-hosted n8n 2.23.4, we had our WhatsApp booking workflow switched off and asked n8n to run from the WhatsApp Trigger up to the next node, which is what the play button does. n8n answered that it was waiting for a WhatsApp message. The first step of our own setup guide told buyers to press play and read the output, so that step could not finish as we had written it.

Why it happens

A trigger of this kind has nothing to run with until an event reaches it, so a test run can only listen for one. Two more things made the hand test harder than the guide suggested.

We could not hand the workflow a message we had typed up ourselves, because n8n checks Meta's signature on whatever arrives at that trigger. The Slack commands in the same workflow had a similar limit: they only reach n8n through the Request URL set in the Slack app, so they do not arrive while the workflow is off either, unless the Slack app is pointed at n8n's test URL.

What worked

The simplest hand test was to switch the workflow on and send each message from a real phone. We sent eleven steps that way. They covered a booking, a move, a cancellation, a request for a person and the Slack takeover and resume commands. Ten of them produced an execution we could read afterwards.

For the cases we could not easily repeat from a phone, we used replays. We started a new run from the trigger output of a real earlier execution and changed only the text of the message. Everything after the trigger was then real: the sheet, the calendar, the data tables, the model, the Slack posts and the WhatsApp replies to the same phone. The log marks which results came from the phone and which came from a replay, because the two are different grades of evidence.

We corrected the guide in the pack sold here the same day, and it now tells the buyer to do the hand run with the workflow switched on.

How we found it

The phone steps are executions 94091 to 94109, in webhook mode. The replays are 94117 to 94165, in manual mode. The WhatsApp ones started from the inbound message of run 94106, and the Slack ones from the real commands of runs 94102, 94104 and 94109. The attempt with the workflow off was made at 12:38 that day, and we stopped the listening afterwards.

What we did not establish

We stopped the listening without sending a message into it, so we did not check whether a test run started that way completes normally once a message arrives. We did not try this on n8n Cloud. One phone step produced no execution at all, a booking request sent while the chat was paused, and we never found out why. We covered that case with a replay.

Written by Fractional HQ from its own runs. If your n8n behaves differently, email hello@fractionalhq.uk and we will correct the note.