frappe-webhook-manager

Secure webhook receivers in Frappe require HMAC-SHA256 signature verification to authenticate incoming requests from external services. This Skill generates Python endpoints that verify signatures against stored webhook secrets, parse JSON payloads, and route events to appropriate handlers, ensuring only legitimate notifications are processed.

Yes, outgoing webhooks trigger on specific Frappe document events like on_submit. This Skill generates sender functions that post document details to external systems with built-in retry logic and asynchronous processing via Frappe's enqueue system, preventing application performance bottlenecks.

Real-time payment notifications require webhook receivers that verify authenticity and update records automatically. This Skill generates secure endpoints that receive payment success webhooks, validate signatures using HMAC-SHA256, parse gateway payloads, and trigger handlers to update corresponding Sales Invoices without manual intervention.

Asynchronous webhook integration uses Frappe's enqueue system to process outbound webhooks in background jobs. This Skill implements async sending with retry logic, allowing your application to queue webhook events without blocking user operations or delaying document processing.

Webhook secrets should be loaded from Frappe configuration files rather than hardcoded. This Skill handles secret management and HMAC-SHA256 signature verification against configured values, ensuring secure authentication without exposing sensitive credentials in code.

Event-driven webhooks in ERPNext trigger on document lifecycle events like on_submit, on_update, or custom events. This Skill generates webhook senders for these Frappe document events, enabling integrations with external CRM systems, payment gateways, and third-party services automatically.