Advanced: Security, Pause & Queue, Health
Learn about Advanced: Security, Pause & Queue, Health in WaymakerOS.
HMAC Signature Verification
For extra security, you can verify that incoming webhooks are genuinely from your external service — not from someone who guessed your URL.
How It Works
Many services sign their webhook payloads with a secret key using HMAC (Hash-based Message Authentication Code). When you add the signing secret to your connection, Commander verifies the signature on every incoming request. Requests with invalid or missing signatures are rejected.
Setting It Up
- Open your webhook connection
- Go to Settings > Webhook Security
- Paste the signing secret from your external service into the HMAC Signing Secret field
- Save
The field is a password input (hidden by default) and is optional — leave it empty if your service doesn't support HMAC signing.
Supported Signature Formats
Commander automatically detects the signature format based on the HTTP header:
| Service | Header | Format |
|---|---|---|
| Stripe | stripe-signature | Stripe's timestamp + signature scheme |
| GitHub | x-hub-signature-256 | HMAC-SHA256 hex digest |
| Shopify | x-shopify-hmac-sha256 | HMAC-SHA256 base64 |
| Generic | x-signature or x-webhook-signature | HMAC-SHA256 hex digest |
If your service uses a different header, it may still work with the generic format. Test with a real webhook to verify.
Where to Find the Signing Secret
- Stripe — Dashboard > Developers > Webhooks > click your endpoint > Signing secret
- GitHub — Repository > Settings > Webhooks > edit your webhook > Secret field
- Shopify — Settings > Notifications > Webhooks > scroll to "All your webhooks will be signed with..."
Pause & Queue
You can temporarily pause a webhook connection without losing any events. Events received while paused are queued and can be processed when you resume.
Pausing a Connection
- Open your webhook connection
- Go to Settings
- In the Danger Zone, click Pause connection
The connection status changes to paused (yellow dot). External services can still POST to your URL — events are accepted and queued, but not processed.
What Happens While Paused
- Events are received and stored with a Queued status (amber badge)
- No field mapping or table writes occur
- The event count continues to increment
- Your external service gets a success response (so it doesn't retry)
Resuming and Processing the Queue
- Click Resume connection in the Danger Zone
- A Queued Events banner appears showing the count: "{count} event(s) queued — Events received while paused. Process them now to apply field mapping."
- Click Process Queue to process all queued events
Processing applies your current field mapping configuration. This means you can:
- Pause the connection
- Update your field mapping
- Resume and process the queue with the new mapping
Queue Processing Results
After processing, Commander reports:
- Processed — how many events were successfully processed
- Errors — how many failed during processing
- Total — total events in the queue
When to Use Pause
- Updating field mapping — Pause, update mapping, resume, process queue with new mapping
- Maintenance — Temporarily stop processing while you restructure your table
- Debugging — Pause to examine events without new ones coming in
Health Monitoring
Each webhook connection shows real-time health stats so you can monitor reliability at a glance.
Health Cards
Three cards at the top of the webhook overview:
| Card | Description |
|---|---|
| Events Today | Total webhook events received today |
| Success Rate | Percentage of successful events (color-coded) |
| Errors Today | Number of failed events today |
Success Rate Colors
| Rate | Color | Meaning |
|---|---|---|
| 95% or higher | Green | Healthy |
| 80% to 94% | Amber | Degraded — investigate |
| Below 80% | Red | Down — needs attention |
Last Error
If your connection has had a recent error, a red banner appears below the health cards showing:
- The error message
- When it occurred
Extended Stats
The connection also tracks:
- Events (7 days) — total events in the last week
- Queued count — events waiting to be processed (when paused)
Health Dashboard
The Connections tool also has an overall Health Dashboard that shows all your connections at a glance:
- Summary cards — total connections, active, errors, paused
- Events (24h) — aggregate event count, success rate, and error count across all connections
- Attention Required — connections that currently have errors
- Sync Schedule — last sync and next scheduled sync times
Use the Health Dashboard to monitor all your connections from one place, then drill into individual connections for details.