Chrome extension usage
Once installed and signed in, use the extension to stay close to your webhook traffic without leaving the browser.
Monitoring webhooks in the background
The extension can keep a lightweight connection (or periodic sync, depending on implementation) so new requests show up even when the HookNexus tab is not focused.
- Open the extension popup and select an endpoint.
- Turn on monitoring / listen (labels may vary by version).
- Leave Chrome running; incoming webhooks appear in the popup or badge when enabled.
For heavy debugging, the web dashboard and CLI (hooknexus listen) still offer the deepest detail.
Forwarding rules
Configure forwarding so traffic received by HookNexus is passed to a local or staging URL (availability depends on your subscription—Pro features often mirror the CLI forwarding behavior).
- Set the target URL (for example
http://localhost:3000/webhooks). - Use path rules that match how your server expects routes (similar to CLI
--preserve-pathsemantics where supported). - Save rules per endpoint so you can switch projects without retyping URLs.
Desktop notifications
Enable desktop notifications in the extension or Chrome site settings to get alerted when:
- A new webhook hits a monitored endpoint.
- A forward fails or times out (if the extension surfaces errors).
You can usually mute notifications per endpoint or during focus hours.
Local request history (IndexedDB)
The extension may cache recent requests locally using IndexedDB so you can scroll through history quickly without refetching everything.
- History is on-device and subject to browser storage limits.
- It is not a full backup—use the dashboard for authoritative retention per your plan.
- Clearing site data for the extension removes local history.
Account and subscription management
From the popup or linked dashboard:
- View current plan and usage hints.
- Open billing or upgrade flows (often redirecting to the main HookNexus site).
- Sign out to revoke the session on this browser profile.