Webhooks
A webhook connection gives you a unique URL that external services can POST data to. When an event happens in another tool — a Stripe payment, a GitHub push, a form submission — that tool sends an HTTP request to your webhook URL, and the data appears in your Commander workspace.
Overview
A webhook connection gives you a unique URL that external services can POST data to. When an event happens in another tool — a Stripe payment, a GitHub push, a form submission — that tool sends an HTTP request to your webhook URL, and the data appears in your Commander workspace.
Webhooks are one of four connection types in Commander, alongside Signal Analytics (website tracking), API Connections (REST API sync), and MCP Connections (AI tool connections).
What You Can Do
| Feature | Description |
|---|---|
| Receive data | Get a unique URL, paste it into any service, and start receiving events |
| View events | See every incoming event with full payload, status, and timing |
| Map fields | Route webhook data into your Commander Tables automatically |
| Discover schemas | Analyze incoming payloads and auto-suggest table columns |
| Monitor health | Track success rates, error counts, and processing times |
| Get alerts | Configure notifications when errors exceed your threshold |
| Retry and replay | Retry failed events or replay any event for reprocessing |
| Pause and queue | Temporarily pause a webhook without losing events |
| Verify signatures | HMAC security for Stripe, GitHub, Shopify, and more |
Quick Start
- Open your Connection Canvas
- Click "+" and select Webhook
- Name it (e.g., "Stripe Payments" or "Contact Form")
- Copy the webhook URL
- Paste it into your external service
That's it. Events start flowing immediately.
Guides
- Setting Up — Create a webhook, copy the URL, paste it into your service, and send a test event
- Event Log — View, filter, search, export, retry, and replay events
- Field Mapping — Map webhook data to your Commander Tables with auto-detect or manual mapping
- System Alerts — Get notified when errors exceed your threshold
- Advanced — HMAC signature verification, pause and queue, health monitoring
How It Works
External Service → POST → Your Webhook URL → Commander processes it
↓
Event logged
Field mapping applied (if configured)
Data written to table (if mapped)
Alerts checked (if enabled)
Each webhook connection gets a unique URL with an embedded token for authentication:
https://apps.waymakerone.com/functions/v1/connection-webhook-receiver?connection_id=YOUR_ID&token=whk_xxxxx
The connection_id and token parameters authenticate incoming requests. Keep the full URL private — anyone with the URL can send events to your connection.
Supported Services
Webhooks work with any service that can send an HTTP POST request. We've tested with 380+ services. Browse by category with setup guides.
Next Steps
Ready to get started? Head to Setting Up to create your first webhook connection.