Automations · Nodes · action
Ask WhatsApp location
action.whatsapp_ask_location · action
Ask the customer to share their location, wait for the pin, then continue with latitude and longitude.
When to use
- Ask the customer to share a location pin and continue with latitude/longitude.
- Use an HTTP request node afterward for store lookup, GIS, or delivery zones.
Configuration
| Field | Required | Notes |
|---|---|---|
| accountId | no | Channel account; leave empty to use context when available |
| bodyText | no | Message body; expressions allowed |
| text | no | Message body; expressions allowed |
| timeoutSeconds | no | Wait timeout in seconds (default 86400) |
Inputs
Upstream node output and execution context (contact, account, variables).
Outputs
After the customer shares a pin (or timeout): latitude, longitude, name, address, inboundMessageId, timedOut. Insert value paths use nodes.{id}.*.
Execute step (editor)
| Eligible? | Notes |
|---|---|
| Disabled | Needs multi-branch or wait/resume context — use a full Test run. |
See Test, Execute, debug, listen and limitations.
Common errors
| Symptom | Cause | Fix |
|---|---|---|
| Send failed on Test/Run | Outside window, bad template, or missing contact | Use template outside window; ensure contact/account in context. |
| Execute succeeds but nothing delivered | Execute is dry-run for channel sends | Use full Test run / Run now. |
Example
Message-received trigger → Ask location → on out use latitude/longitude in an HTTP request (e.g. nearest store) → continue the journey.