Troubleshooting

Find the broken step.

Webhook issues are easiest to fix when you test one part at a time: phone notifications, webhook URL, request payload, and source system logs.

General debugging steps

  1. Confirm notifications are enabled for PINGSLAP on your iPhone.
  2. Copy the webhook URL again from the correct Space.
  3. Use PINGSLAP's test alert to confirm notification delivery.
  4. Submit the real form or send the real webhook request.
  5. Check your form plugin, automation, or server logs for the HTTP status code.
  6. Reduce the payload to title and message, then add fields back one at a time.

For a consistent process, start with Verify Integration.

No notification

Check phone notification permissions, Focus modes, internet connection, and whether the alert was sent to the intended Space.

Invalid webhook

Copy the full URL again. Watch for missing characters, extra spaces, old URLs, or a URL pasted into the wrong field.

Payload missing or empty alert

Send JSON with clear title and message fields. Confirm the Content-Type header is application/json.

Duplicate alerts

Look for multiple form actions, multiple automation runs, retry settings, or both a form plugin and an automation tool sending the same event.

Browser CORS errors

If the browser console mentions CORS, move the request to a server, WordPress webhook, automation tool, or reverse proxy. See JavaScript and CORS.

Works in curl but not browser

The URL and payload may be fine. The browser may be blocking a cross-origin request, or your JavaScript may be exposing headers that trigger a preflight request.

WordPress webhook failures

Check the plugin's webhook log or submission log if available. Confirm the method is POST, the request format is JSON, and your host is not blocking outbound HTTP requests.

Rate limiting

If many alerts fire at once, slow the source system down, batch low-priority alerts, or add retry delays. Do not retry instantly in a tight loop.

What to send support

Email support@pingslap.com with your Space name, source system, approximate test time, HTTP status code, and a redacted sample payload. Do not email your webhook URL unless support asks for it.