save response: WebHook plus Save Response pulls ERP status back into WhatsApp variables so the next text can quote a real id or state. See why. Read how.
save response is the canvas job B2B spare parts should ship this week. Flow asks “order status?” then agents Alt-Tab into the ERP anyway? Wrong trigger or no Flow Builder wastes spend and nights.
If you own the shared inbox at B2B spare parts, this canvas is your problem. Developers can sit this one out.
We review the B2B spare parts path the same way: trigger, short copy, Flow Builder, live test—then maybe more nodes.
This is Cloud API, not a grey sender. B2B spare parts still obeys windows and templates.
Ask or already know order id. WebHook GET/POST to your ERP with that id. That is enough setup talk for B2B spare parts before the first heading.
WebHook plus this node pulls ERP status back into WhatsApp variables so the next text can quote a real id or state. B2B spare parts should treat that sentence as the job, not a slide title.
Sources: Meta Cloud API send-messages and messaging limits. B2B spare parts fails on policy more often than on missing icons in WebHook, this step, Simple Text, Assign Agent.
WebHook plus that component pulls ERP status back into WhatsApp variables so the next text can quote a real id or state. On the canvas you place WebHook, the canvas action, Simple Text, Assign Agent. B2B spare parts teams finish one job, then use Flow Builder when the customer sends a photo or a rant.
Need palette click-path? Use WhatsApp Flow Builder, then return to this B2B spare parts recipe.
In this series — Part 2 of 6 (Integrations). Previous: Google Sheets node. Next: Meta CAPI. Series start: Google Sheets node.
Name it like webhook-save-response-_v1. Steal a preset if B2B spare parts matches. Every tap needs an edge.
Inside B2B spare parts ops, they learned the hard way: webhook 500s with no fallback; chat went silent. They recovered only after this node on 200; else “checking with ops” + agent. That is the v1 bar for this journey.
Keep WebHook, this step, Simple Text, Assign Agent visible in the flow name so the next editor knows the job. First moves: Ask or already know order id. WebHook GET/POST to your ERP with that id.
The step teams skip: that component paths (status, eta) into variables. B2B spare parts paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Speak the status; if unknown, Assign Agent. Then Timeout the HTTP call in your mind—have a fallback text. Agents still work in a shared WhatsApp inbox after assign.
Attributed example, from a WAPilot B2B spare parts workspace (2026): webhook 500s with no fallback; chat went silent. the canvas action on 200; else “checking with ops” + agent
Recovery was boring: shorter copy, honest Flow Builder, and this path on 200; else “checking with ops” + agent. Quality stopped sliding.
Rule sources: Cloud API templates and session rules. B2B spare parts dropped a promo template into this journey and watched quality dip.
How we know: when this canvas double-texts human handover at B2B spare parts, we see it in the same thread the agent sees.
Turn AI Reply off on the same trigger B2B spare parts uses, or you greet twice. Priority is a setting, not a wish.
STOP and quiet hours bind this B2B spare parts path. If campaigns already suppressed the contact, do not continue the pitch here.
QA with a photo, “ok”, and “agent”. Empty Responses at B2B spare parts usually means the Ask or webhook never saved after WebHook.
In a B2B spare parts thread (2026), the failure was concrete: webhook 500s with no fallback; chat went silent. The rewrite that stuck was this node on 200; else “checking with ops” + agent. Repeat that, rather than adding decorative palette icons.
B2B spare parts only needed WebHook, this step, Simple Text, Assign Agent on the happy path. Day-one order: Ask or already know order id. After the hello: WebHook GET/POST to your ERP with that id.
Days for rating if reports stacked on B2B spare parts; minutes for inbound to reopen session. Killing the flow does not gift free-form sends.
Opposite direction. Trigger starts the flow. This WebHook runs in the middle and Save Response maps the body.
No. Bots share the care window with humans at B2B spare parts. After it closes, you need a template or a new customer message—not another WebHook bubble.
No. Handoff is ownership. Shared numbers still share reports. B2B spare parts cannot isolate that with a tag on WebHook, Save Response, Simple Text, Assign Agent.
Keep the B2B spare parts path thin, keep Flow Builder, keep the window in mind. Start a free trial if this layer is still missing.
ads to booking flow: Ads → catalog or booking: paid chat that sells the thing in the ad—slot or product—then human if needed. See why. Read how. Start here.
Read MoreStart automating your WhatsApp marketing today with WA-Pilot. Join thousands of businesses already growing with our platform.
Start Free Trialassign ads leads: Assign and tag ads leads: source label in the flow, Meta ad routing in Team Assignment, then sub-flow for the product. See why. Read how.
Read MoreCAPI in ads flow: Meta CAPI in an ads flow: fire Lead/Purchase after chat qualify so Ads Manager sees the WhatsApp truth. See why. Read how. Start here.
Read More