Webhook Gateway Integration

Receive external events from any system to trigger automated knowledge base syncing, context updates, or agent alerts.

What it does

The Webhook Gateway acts as an incoming event handler. It allows external platforms (billing services, custom database scripts, CRM setups) to send real-time JSON payloads to Verabase. Upon receipt, Verabase automatically parses the event schema to update contact context metadata, update agent routing cues, or trigger content delivery pipelines.

Data Flow & Request Signature

Verabase acts as the receiving listener server. Events are evaluated instantly on delivery:

Data Read: Inbound JSON payloads including event types, customer metadata, and transaction parameters.
Data Written: None. The gateway is a one-way receiver, sending a standard HTTP `200 OK` handshake response.
Sync Frequency: Event-driven. Actions trigger immediately when HTTP POST payloads hit the custom gateway endpoint.

Scope & Limits

Payload Constraints: Payloads must be valid JSON format, with a maximum size limit of 1MB.
Security Signatures: Signature verification is enabled by checking the headers for HMAC SHA256 digests. Refer to the GitHub Webhook Specifications for details on payload validation strategies.

Setup guide

Estimated setup time: ~6 minutes. Authentication type: HMAC Signature Verification (Signing Secret Key). Developer level credentials required in source application.

Activate Gateway Endpoint

Go to Settings → Integrations → Webhook Gateway and toggle the Gateway state to active.

Copy Custom Endpoint URL

Verabase compiles a unique destination link. Copy this URL along with the generated webhook signing secret key.

Configure Webhook in Source app

Open your source application (e.g. Stripe, custom CRM node). Paste the Endpoint URL into the webhook endpoint configuration manager. Select the target events you want to dispatch.

Implement Signature verification

Input the copied webhook signing secret into the verification field of the source system. This signature secures the request channel and prevents spoofing.

Where it shows up

Integration Logs: Displays real-time request lists inside the Webhook Gateway panel, logging response codes, payload schemas, and errors.
Automation Pipeline: Shows up as a trigger source when creating or updating custom automation routing rules.

Troubleshooting & Common Issues

HTTP 401 Unauthorized: This error is thrown if the incoming request payload fails signature checks. Check if the webhook secret configured in the dispatching server matches your Verabase secret.
HTTP 504 Timeout: If the connection drops or times out, verify that the payload size is under the 1MB limit and that the dispatching server resolves Verabase's DNS records correctly.

Frequently asked questions

Can the Webhook Gateway receive nested JSON payloads?

Yes, the gateway parses nested JSON structures. You can map nested attributes directly to Verabase context variables in the settings.

How does Verabase verify incoming webhook signatures?

You can configure webhook verification using shared secret tokens, HMAC-SHA256 signatures, or standard API keys.

What happens if our server is down when a webhook fires?

Verabase automatically retries failed webhook deliveries with exponential backoff for up to 24 hours.

Related integrations

Ready to deploy webhooks?

Join the waitlist for early access to the self-healing knowledge platform.

Get early access to Webhook Gateway