On this page

On this page

Generic Webhooks

SpidyLabs works with any service that sends HTTP requests. This guide covers the general setup pattern.

Setup Pattern

  1. Create a bin in SpidyLabs
  2. Copy the webhook URL (https://spidylabs.com/hook/your-bin-slug)
  3. Paste the URL into your service's webhook configuration
  4. Trigger an event in the service
  5. Inspect the captured request in SpidyLabs

Testing with cURL

Before configuring a service, test your bin with cURL:

# Simple GET request
curl https://spidylabs.com/hook/your-bin

# POST with JSON body
curl -X POST https://spidylabs.com/hook/your-bin \
  -H "Content-Type: application/json" \
  -d '{"test": true}'

# POST with form data
curl -X POST https://spidylabs.com/hook/your-bin \
  -d "name=test&event=webhook"

# POST with custom headers
curl -X POST https://spidylabs.com/hook/your-bin \
  -H "Content-Type: application/json" \
  -H "X-Webhook-Secret: my-secret" \
  -H "X-Event-Type: order.created" \
  -d '{"order_id": 12345}'

Common Webhook Providers

SpidyLabs works with any provider that sends HTTP webhooks, including:

  • Payment: Stripe, PayPal, Square, Paddle
  • Communication: Twilio, SendGrid, Mailgun, Postmark
  • E-commerce: Shopify, WooCommerce, BigCommerce
  • DevOps: GitHub, GitLab, Bitbucket, CircleCI
  • CRM: HubSpot, Salesforce, Pipedrive
  • Other: Zapier, IFTTT, Make (Integromat), n8n

Troubleshooting

Requests Not Arriving

  1. Check the URL — Make sure you copied the full bin URL including the slug
  2. Check the service — Look for delivery logs in the webhook provider's dashboard
  3. Check your plan limits — Free plan allows 200 requests/day
  4. Test with cURL — Verify the bin is working by sending a manual request

Unexpected Response Codes

If your service reports errors:

  • SpidyLabs returns 200 OK by default
  • If you get 429, you've hit the daily request limit
  • Check auto-response settings to ensure you haven't configured an error response

Missing Request Body

Some providers send empty bodies for certain events. Check:

  • The Content-Type header — if missing, the body may not be parsed
  • The provider's documentation — some events are header-only notifications

Tips

  • Name your bins descriptively (e.g., "shopify-orders", "twilio-sms")
  • Use separate bins for different services to keep traffic organized
  • Check the Headers tab first — many providers include event type and delivery ID headers
  • Use auto-response to simulate different response scenarios