← All ideas
0

Flow: Let webhooks reply with custom data and accept GET and header or basic auth

LaunchedFlowIdea

n8n's Webhook node accepts GET, POST, PUT, PATCH, DELETE and HEAD, supports basic, header and JWT auth, and can respond when the last node finishes or through a Respond to Webhook node with custom status, headers and body (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/, https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook/). Our hook route only exports POST and always answers 202 {runId} before the flow runs (app/api/flow/hooks/[token]/route.ts). That blocks verification handshakes (Meta/WhatsApp hub.challenge, Slack url_verification), form handlers that need a redirect, and small APIs built on Flow. First scope: GET support, an optional shared-secret header check, and a 'Respond to webhook' node that waits up to about 10 s for a synchronous answer. Priority: high. Effort: M. Compared with Zapier / n8n.

Comments 0

No comments yet.