Whatsable
Yes. If you type a reply in the WhatsApp Business app on your phone, n8n can still start a scenario from that message. You keep the app installed. The same WhatsApp Business number stays on the phone and in the automation.
The catch is outgoing. If outgoing is off on the webhook, that phone-app reply never arrives, so there is nothing for n8n to run. In the WhatsAble dashboard, open Developer, add an endpoint, and enable outgoing. A custom webhook needs outgoing: true.
https://whatsable.app/integrations/webhook
n8n makes this easy to miss. The trigger is labelled On new Incoming message event, which sounds inbound-only. That string is the node's label, not a filter. With the credential Notifyer System incoming and outgoing messages, the same trigger also fires when you reply from the phone. Set a filter so incoming_message is false, or you will treat an owner reply as if a customer had just written in.
https://whatsable.app/integrations/n8n
The same POST can land in Zapier or Make. This walkthrough is n8n, and the filter is still incoming_message is false.
https://whatsable.app/integrations/zapier
https://whatsable.app/integrations/make
An Agent Skill is not a separate event. It sees that same webhook payload only if the skill is on a webhook you created with outgoing enabled. Installing skills alone does not deliver the phone-app reply.
https://whatsable.app/vibe-code
When that phone-app reply hits the webhook, the sanitized shape is incoming_message false, send_by "WhatsApp App", and was_message_by_human true. This post does not publish customer JSON, phones, or names.
What can I build with that owner reply?
A CRM that knows you already handled it. The phone-app reply hits n8n, Zapier, Make, or the webhook. That scenario can mark the contact as owner-replied in the CRM you already use. This page does not invent CRM clicks or field labels.
A Sheet of owner replies. The same POST can append a row so you can see how often someone answered from the phone instead of from automation. No invented Sheet buttons.
Another automation in the same picture. n8n is the story here. Zapier and Make get the same POST. An Agent Skill only sees it on the webhook you created.
https://www.tella.tv/video/trigger-n8n-workflows-with-whatsapp-messages-e1f3
This is not a second field spec, and it is not a customer payload. It is also not a claim that the n8n label means inbound-only once outgoing is on.