Troubleshooting
Common errors
| Error | What to do |
|---|---|
401 connection expired or revoked | Reconnect the Bahasha account in Zapier |
402 insufficient wallet balance | Top up the organization wallet, then replay the Zap run |
403 permission or organization access denied | Reauthorize with an integrations manager and use records from the same organization |
404 number, template, contact, or segment not found | Refresh the Zap field and select a current record |
409 customer-service window closed | Use Send Template Message instead |
| Media URL rejected | Use a public direct HTTPS file URL with a supported media type |
No live trigger records
Trigger testing displays a static sample and Bahasha does not replay historical events. To receive a live record:
- Finish configuring the Zap.
- Turn the Zap on.
- Send a new message or produce a new delivery-status transition.
- Check Zap History for the resulting run.
If no event arrives, verify that:
- The Zap is enabled.
- The selected WhatsApp number is still connected to Bahasha.
- The authorized Bahasha connection has not been revoked.
- The status event matches the statuses selected in the trigger.
A dropdown is empty or outdated
- Confirm the phone number, template, contact, or segment belongs to the authorized organization.
- Confirm templates are approved.
- Refresh the field in the Zap editor after creating or changing a record.
- Reconnect the Bahasha account if its permissions changed.
Free-form or media sending fails
Free-form text and media only work while the recipient’s 24-hour customer-service window is open. Send an approved template when the window is closed. Also confirm the recipient opted in and the wallet has enough balance.
Trigger delivery health
Open Bahasha → Integrations → Zapier to review active subscriptions, delivery health, failures, and last activity. Bahasha retries temporary trigger delivery failures four times with exponential backoff.
Connection remains invalid after reconnecting
Revoke the affected connection in Bahasha, remove or reconnect it in Zapier, then authorize it again with a user who has Integrations: Manage.