Webhooks
No customer-facing outbound webhooks yet — what exists internally, and the supported ways to react to events today.
Not verified yet
Outbound webhooks are not available today. You can't subscribe your own backend to events like "backup completed" or "Brand Monitor hit detected". The capability is on the roadmap — register interest via app.norcube.com.
What "webhooks" exist today
Two internal integrations you'll see referenced, neither subscribable:
- Stripe → Norcube billing. Stripe delivers payment events (payment succeeded/failed, card attached, SCA required) to the billing service — this is what drives dunning and card bookkeeping.
- Backup workers → Backup control plane. Each backup job's worker reports its outcome via an authenticated one-shot callback — internal machinery, described in Backup → Encryption and security.
Reacting to events without webhooks
Supported patterns, per event type:
- "Did last night's backups succeed?" — poll the Backup job list
(
nrc snapdb backup list -o jsonorGET /backups) and filter on status. See Browse backup history. - "A bulk domain check finished" — DomainRadar's bulk jobs offer a
Server-Sent Events stream that pushes each result live and a
doneevent at the end: streaming. - "Someone touched a sensitive resource" — LangSync and Backup both expose filterable audit-log APIs designed for exactly this kind of polling into a SIEM or notifier: LangSync audit log, Backup audit log.
- "A lookalike domain appeared" — Brand Monitor's own email alerts are the push channel; point them at a Slack channel address or ticketing intake for machine handling.
- "An invoice was issued / payment failed" — billing emails the org's invoicing email for every event that needs attention (dunning).
Related
- Billing → Dunning — the Stripe-driven state machine.
- CLI — the polling building block for cron-based integrations.