custom webhook trigger: Custom webhook + payload is the Flow Builder trigger that starts from your POST: copy URL, listen, map the phone field. See why.
custom webhook trigger is the canvas job agency lead-gen site should ship this week. Website form submits into a CRM while WhatsApp never starts the journey? Wrong trigger or no Simple Text wastes spend and nights.
Written for people who will publish this agency lead-gen site journey this week—not for a strategy offsite.
You get a five-step build, the real nodes (Trigger (custom-webhook), Simple Text, Update Contact), and why agency lead-gen site had to cut half the graph.
We would rather agency lead-gen site publish with Trigger (custom-webhook) and an agent exit than collect features “for later.”
Set starting step to Custom webhook + payload and open Configure webhook. Copy the flow-trigger URL and keep the token private. That is enough setup talk for agency lead-gen site before the first heading.
Custom webhook + payload is the Flow Builder trigger that starts from your POST: copy URL, listen, map the phone field. agency lead-gen site should treat that sentence as the job, not a slide title.
Sources: WhatsApp messaging limits and Cloud API send-messages. That pairing explains why agency lead-gen site goes quiet after a day of silence on Trigger (custom-webhook).
Custom webhook + payload is the Flow Builder trigger that starts from your POST: copy URL, listen, map the phone field. On the canvas you place Trigger (custom-webhook), Simple Text, Update Contact. agency lead-gen site teams finish one job, then use Simple Text when the customer sends a photo or a rant.
Need palette click-path? Use WhatsApp Flow Builder, then return to this agency lead-gen site recipe.
In this series — Part 5 of 8 (Triggers). Previous: shopify store events. Next: fire a Wapilot flow. Series start: new contact trigger.
If a template already includes Trigger (custom-webhook), start there and delete what agency lead-gen site does not need.
Inside agency lead-gen site ops, they learned the hard way: they POSTed without a WhatsApp-able phone path. They recovered only after mapped mobile and tested with a real +91 number. That is the v1 bar for this journey.
Keep Trigger (custom-webhook), Simple Text, Update Contact visible in the flow name so the next editor knows the job. First moves: Set starting step to Custom webhook + payload and open Configure webhook. Copy the flow-trigger URL and keep the token private.
The step teams skip: POST sample JSON while the canvas is listening. agency lead-gen site paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Pick the phone path (phone, mobile, or nested customer.phone). Then Save selected fields as payload variables, then publish. Agents still work in a bot to human handover after assign.
Attributed example, from a WAPilot agency lead-gen site workspace (2026): they POSTed without a WhatsApp-able phone path. mapped mobile and tested with a real +91 number
agency lead-gen site then judged the path on finished jobs and escapes to humans—not on bot bubble count.
Rule sources: templates when silent; send-messages when the window is live; limits if agency lead-gen site nags. Read those before stacking Delay after Trigger (custom-webhook).
How we know: canvas coaching for agency lead-gen site. The path either qualifies, books, or routes, or it is theatre. Source of truth is Cloud API docs.
Campaigns open the door. This path walks Trigger (custom-webhook), Simple Text, Update Contact. Pasting blast copy into the agency lead-gen site journey is how reports start.
One WABA, two brands, two agency lead-gen site-style journeys: quality is still one score. Split numbers before you publish.
Test on a cheap SIM for agency lead-gen site: Set starting step to Custom webhook + payload and open Configure webhook. then garbage input. Confirm tags on the contact before you spend on ads.
In a agency lead-gen site thread (2026), the failure was concrete: they POSTed without a WhatsApp-able phone path. The rewrite that stuck was mapped mobile and tested with a real +91 number. Repeat that, rather than adding decorative palette icons.
Stop it, staff the inbox for agency lead-gen site, template only when needed. Rating can take days. Delay nodes do not rewrite Meta’s window.
No. Wapilot must match or create a contact by phone. Fix the path before you wire production CRMs.
Delay until a weekday, then a utility template if agency lead-gen site went quiet. Do not assume session is still alive after Trigger (custom-webhook).
No. One thread, one clock. Two brands on one WABA share quality too. Split numbers before agency lead-gen site collides with another brand’s promos.
this journey only counts live. When you want Trigger (custom-webhook) on official Cloud API for agency lead-gen site, start a free trial on WAPilot.
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