What you'll need
- A journey in progress
- For a webhook step, an endpoint on your side ready to receive a POST or GET request
Steps
- In the journey editor, open Add Step, choose Integrations, then Tag or Webhook.
- Tag step: choose Add or Remove, then type the tag name. There's no picker of existing tags — type the exact name you want. Adding a tag a guest already has, or removing one they don't have, is a safe no-op.
-
Webhook step: enter the endpoint URL, choose POST or GET, and — for POST — write a JSON request body. You can use merge-field syntax like
{{first_name}}in the body. - There's no field for custom headers or an API key/bearer token in a webhook step today. Instead, every webhook MyWiFi sends carries an
X-MyWiFi-Signatureheader — a signature your receiving endpoint can verify to confirm the request genuinely came from MyWiFi, rather than you supplying a shared secret on our side. - If a webhook step's URL is left blank, that step is skipped silently rather than failing the rest of the journey.
- Webhook and tag sends still respect guest consent — if a guest hasn't consented to marketing communications, a webhook step that counts as a "send" is withheld rather than fired.
Best practice: if your receiving endpoint needs to trust that a request really came from MyWiFi, verify the
X-MyWiFi-Signatureheader rather than asking us for a shared secret to put in the URL or body — there's no field for that, by design.
Comments
Please sign in to leave a comment.