Current webhook ingress routes for workflow-triggered callbacks, including validation, wildcard path support, and catch-all method handling. Webhook ingress APIs live under /webhooks/v1/....

​
Endpoint Areas

AreaEndpoints
Registration validationHEAD /webhooks/v1/{workflowId}/{nodeId}, HEAD /webhooks/v1/{workflowId}/{nodeId}/*
Callback ingressGET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD/SEARCH /webhooks/v1/{workflowId}/{nodeId}, GET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD/SEARCH /webhooks/v1/{workflowId}/{nodeId}/*

​
Notes

  • These routes are trigger ingress endpoints, not CRUD endpoints for webhook configuration.
  • The controller uses a catch-all handler for callback ingress; the current generated schema enumerates GET, POST, PUT, PATCH, DELETE, OPTIONS, HEAD, and SEARCH on those paths.
  • The controller performs workflow lookup, optional plugin verification or preprocessing, event filtering, execution creation, and BullMQ enqueueing before returning.
  • Generic webhook triggers apply per-registration method checks and optional custom authentication before execution is created.
  • Some providers use the HEAD route for callback validation before they start sending webhook events.