openwebhook.co
Open inspector →
developer guide

How to Test Webhooks in Pabbly Connect

See the request Pabbly Connect sends: webhook action or API step, paste an inspector URL, capture method, headers, and JSON.

By David Lorenzo García··5 min read

Pabbly Connect can catch a webhook (Pabbly gives you a URL) or send one (you give Pabbly a URL). Use OpenWebhook on the send path so you see the bytes Pabbly posts. A Pabbly webhook trigger already has its own history; do not swap that trigger URL for an inspector.

Create a URL in the inspector. Keep the tab open. The inspector basics are in how to test webhooks online.

Send a webhook to the inspector

  1. After the trigger, add an action that performs an HTTP request (Webhook / API by Pabbly, depending on your workspace).
  2. Method POST.
  3. Destination:
https://hooks.openwebhook.co/YOUR_UUID/pabbly
  1. Choose JSON and map fields. Add any auth headers the real endpoint will require.
  2. Save and Send Test Request (or run the workflow once).

You should see POST /pabbly, Pabbly’s headers, and the mapped body. If Pabbly shows success and the inspector does not, the workflow ran a different step or an old URL.

Webhook trigger (Pabbly as receiver)

Add a Webhook trigger, copy the Pabbly URL, and send a sample to Pabbly. Use cURL or replay from another inspector. That URL is not hooks.openwebhook.co.

When to use the CLI

If the consumer is on localhost, put a listen URL in the Pabbly action. While the CLI is connected, the status returned to Pabbly is the local handler’s status.

Related guides