Terminal
Terminal/Skill
Receives provider webhooks like Stripe or GitHub, verifies their signatures at the edge, and delivers them to a local or private service.
By ngrok
Works with
npx skills add ngrok/skills --skill receive-webhooksReceive an inbound webhook, verify the provider's signature at ngrok's edge, and deliver it to the user's service - without writing verification code and, when wanted, without exposing the service publicly.
Auth is required (ngrok-setup). This job uses a Traffic Policy - pull the verify-webhook and forward-internal mechanics, and the endpoint choice, from ngrok-engine.
Two actions in sequence:
verify-webhook - validate the signature (fails closed with 403 unless enforce: false).forward-internal to a private receiver for production.on_http_request:
- actions:
- type: verify-webhook
config:
provider: stripe
secret: "${secrets.get('webhooks', 'stripe-signing-secret')}"
- type: forward-internal
config: { url: https://billing.internal }
Provider list, per-provider secret setup, replay protection, and endpoint-verification challenges: references/providers.md.
forward-internal.ngrok-engine for why cloud+internal here.Attach the policy and bring up the endpoint(s) on the user's surface - see ngrok-surfaces. The policy body is identical on every surface; only attachment differs.
Give the user the public URL to paste into the provider's webhook settings.
forward-internal to an internal-bound receiver. No inbound firewall ports; the agent connects outbound on 443./stripe, /github, ..), each verifying its provider then forwarding to the right internal service - verification, routing, and secrets in one place instead of per-service code.curl with a valid signature header.verify-webhook replaces it.ngrok api secrets create) or an env var themselves, and reference it from the policy. A whsec_... in a transcript is a leaked secret.verify-webhook, or the signature check breaks.