Skip to app details
Back to app library
APPNEURAL APP FAMILYAutomation & Integrations

Webhooks

Every event delivered, or a clear reason why not

Deliver your app's events to customers' endpoints, signed, logged and retried until they arrive.

01 / OVERVIEW

See where it fits in your day.

Each domain keeps event types (name, description, sample payload; an unknown type registers itself on its first event), consumers (a customer by the business's own id, or one of its own apps) and their endpoints: public https URLs only, event filters with * wildcards, extra headers, on or off, and a whsec_ signing secret per endpoint, rotated with 24 hours of two signatures. Requests are signed per the Standard Webhooks spec (webhook-id, webhook-timestamp, webhook-signature v1 HMAC-SHA256). POST /api/v1/events (secret key) takes a type, data, an optional consumer and an idempotency key, with a payload limit and a rate limit per domain, and fans out to every matching endpoint. The first try goes at once with an inline 5-second retry, then a cron every minute retries at 5 minutes, 30 minutes, 2, 5 and 10 hours (eight tries), logging each attempt's status, the first 2 KB of the answer, duration and error. An endpoint that keeps failing for the domain's set number of days is turned off, with emails to the team and the consumer. Retry one delivery, replay a message, recover everything failed since a time, or send a test event. Consumers manage their own endpoints and see their delivery log at /portal/<token> in the domain's brand, after an email code or a one-time grant from the API. Verification snippets for Node, Python and PHP on /guide, and Claude to explain a failing endpoint from its recent attempts.

A LOOK INSIDEExample layout · sample content
Deliveries and their attempts
EventEndpointStatus
order.createdwebhooksEXAMPLE
invoice.paideventsEXAMPLE
subscription.renewedendpointsEXAMPLE
webhook.testdeliveryEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Webhooks does for you.

01

Signed endpoints

Event filters, extra headers and a signing secret per endpoint, rotated without downtime.

02

Reliable delivery

Retries with backoff, an attempt log, replay, recovery and auto-disable for endpoints that keep failing.

03

Consumer portal

Each consumer adds endpoints and reads their own delivery log on a branded page.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Webhooks. What you can do depends on your access in the app.

01

Describe the events

Add event types with a sample payload, or let the first event register its type.

02

Add consumers

Create a consumer and its endpoints, or send them their portal link.

03

Send events

Call POST /api/v1/events and watch the attempts.

YOUR NEXT MOVE

Make Webhooks part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each domain keeps event types (name, description, sample payload; an unknown type registers itself on its first event), consumers (a customer by the business's own id, or one of its own apps) and their endpoints: public https URLs only, event filters with * wildcards, extra headers, on or off, and a whsec_ signing secret per endpoint, rotated with 24 hours of two signatures. Requests are signed per the Standard Webhooks spec (webhook-id, webhook-timestamp, webhook-signature v1 HMAC-SHA256). POST /api/v1/events (secret key) takes a type, data, an optional consumer and an idempotency key, with a payload limit and a rate limit per domain, and fans out to every matching endpoint. The first try goes at once with an inline 5-second retry, then a cron every minute retries at 5 minutes, 30 minutes, 2, 5 and 10 hours (eight tries), logging each attempt's status, the first 2 KB of the answer, duration and error. An endpoint that keeps failing for the domain's set number of days is turned off, with emails to the team and the consumer. Retry one delivery, replay a message, recover everything failed since a time, or send a test event. Consumers manage their own endpoints and see their delivery log at /portal/<token> in the domain's brand, after an email code or a one-time grant from the API. Verification snippets for Node, Python and PHP on /guide, and Claude to explain a failing endpoint from its recent attempts.

Event delivery from a connected domain's apps: event types, consumers and signed endpoints, retries with backoff, attempt logs, replay, auto-disable and a consumer portal.

Business automations belong to Workflows; cron jobs belong to Scheduling; the business's own alert webhook stays in each catalog's settings.

Priority
P2
Portfolio
Automation & Integrations
Capability
Automation & Integrations
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

webhook schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

webhooks.appneurox.com DEPLOYED

webhooks.appneurox.com

Worker
webhook-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:12
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/webhook-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app