Journey Builder FAQ

What you'll need

• A journey already created, or in progress

Steps

1. What happened to my old Automations? Nothing — the older single trigger→action Automations list still works and runs independently. Journey Builder is a separate, newer tool for multi-step sequences; it doesn't replace or migrate your existing automations.
2. Why don't I see more trigger options? The trigger list you see today reflects what's fully wired end-to-end right now. MyWiFi is actively expanding this list — if the trigger you need isn't there yet, contact support to check on timing.
3. Can I add a custom header or API key to my webhook step? Not today — a webhook step sends a URL, method, and (for POST) a JSON body, with a platform-generated X-MyWiFi-Signature header your endpoint can use to verify the request came from MyWiFi. There's no field for a custom header or bearer token.
4. Why didn't my journey enroll a guest who already matched the trigger? Journeys only enroll guests going forward from when you publish — they don't scan backward for guests who matched the trigger before the journey existed.
5. Can different steps in the same journey use different phone numbers or email accounts? No — a journey has one Twilio sender (SMS + WhatsApp) and one SendGrid sender (email) for its entire sequence. See Choose a sender for your journey.

Related articles

• Journey Builder overview
• Choose a trigger for your journey
• Add a tag or webhook step to a journey