custom trigger: Custom trigger starts a flow (inbound POST). The WebHook action node calls out from a running flow. They are opposite directions. See why.
custom trigger is the canvas job clinic + hospital HIS should ship this week. Your developer wired the outbound WebHook node and wonders why the flow never starts? Wrong trigger or no WebHook wastes spend and nights.
Skip it if you only blast lists. clinic + hospital HIS needs a chat path, not a campaign.
Stay on this clinic + hospital HIS job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in clinic + hospital HIS reviews would rather ship a thin v1 than hoard unpublished nodes.
Inbound: Custom webhook trigger + phone map. Outbound: WebHook action with your ERP URL after you already have a contact. That is enough setup talk for clinic + hospital HIS before the first heading.
this node starts a flow (inbound POST). The WebHook action node calls out from a running flow. They are opposite directions. clinic + hospital HIS should treat that sentence as the job, not a slide title.
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—clinic + hospital HIS on a grey gateway is another product.
this step starts a flow (inbound POST). The WebHook action node calls out from a running flow. They are opposite directions. On the canvas you place Trigger (custom-webhook), WebHook, Save Response. clinic + hospital HIS teams finish one job, then use WebHook when the customer sends a photo or a rant.
Need palette click-path? Use WhatsApp Flow Builder, then return to this clinic + hospital HIS recipe.
In this series — Part 8 of 8 (Triggers). Previous: payload variables. Series start: new contact trigger.
Order: trigger, hello, Inbound: Custom webhook trigger + phone map., then WebHook. That is v1 for clinic + hospital HIS.
Inside clinic + hospital HIS ops, they learned the hard way: IT swapped inbound and outbound URLs. They recovered only after trigger URL for site leads; action URL for HIS callback after booking. That is the v1 bar for this journey.
Keep Trigger (custom-webhook), WebHook, Save Response visible in the flow name so the next editor knows the job. First moves: Inbound: Custom webhook trigger + phone map. Outbound: WebHook action with your ERP URL after you already have a contact.
The step teams skip: Save Response to pull ids back into variables. clinic + hospital HIS paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Use the Custom webhook intake template as a starting graph. Then Never paste the inbound token into the outbound URL field. Agents still work in a WhatsApp drip sequences after assign.
Attributed example, from a WAPilot clinic + hospital HIS workspace (2026): IT swapped inbound and outbound URLs. trigger URL for site leads; action URL for HIS callback after booking
clinic + hospital HIS also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: Meta message templates, send-messages (the window), messaging limits. This clinic + hospital HIS path cannot mint session time. WebHook does not reset it.
How we know: WAPilot implementation plus inbox on official Cloud API—human handover, Flow Builder, Flow Builder. clinic + hospital HIS here matches those queues and Meta’s public docs, using Trigger (custom-webhook), WebHook, Save Response.
One sentence? Use human handover. A week of follow-ups? Flow Builder. Branches and WebHook stay on the canvas for clinic + hospital HIS.
Do not park clinic + hospital HIS reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after Trigger (custom-webhook).
Walk the false branch. A clinic + hospital HIS path that only works on perfect taps will strand the first typo after Outbound: WebHook action with your ERP URL after you already have a contact.
Plan days, not minutes, for rating at clinic + hospital HIS. A new customer message can reopen session quickly. Turning the canvas off is not a fresh clock.
Yes. Site POST starts the flow; later a WebHook action tells the CRM the slot was booked. That is the webhook-to-booking pattern.
No. The window can close while Delay is counting for clinic + hospital HIS. Plan a template for that later bubble after Use the Custom webhook intake template as a starting graph.
No. Same customer, same business thread for clinic + hospital HIS. Do not wait for a reset that never arrives after WebHook.
Recap: Custom trigger starts a flow (inbound POST). The WebHook action node calls out from a running flow. They are opposite directions. Test custom trigger on a real phone, then start a free trial once someone at clinic + hospital HIS owns the inbox.
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