public-ingress

Name: public-ingress
Availability: InStock
Author: Vellum

Expose a local Vellum gateway publicly via an ngrok tunnel.

1.0k|158|Updated Feb 7, 2026

Search Tags:#webhook #tunneling #local-development #ingress #public-url #ngrok #platform-callback

Ready to run

npx skills add https://github.com/vellum-ai/vellum-assistant --skill public-ingress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: public-ingress
Source: https://github.com/vellum-ai/vellum-assistant/tree/main/skills/public-ingress
Command: npx skills add https://github.com/vellum-ai/vellum-assistant --skill public-ingress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expose the local Vellum gateway publicly to receive external webhooks and OAuth callbacks, enabling integrations that require a reachable URL.

Core Features & Use Cases

Install and configure ngrok for tunneling from localhost to a public URL.
Discover, verify, and persist the public URL in the assistant's ingress configuration for platform integrations.
Use cases include Telegram webhooks, OAuth callbacks, and other inbound traffic for local development.

Quick Start

Start a tunnel to your local gateway by running the public-ingress skill and save the resulting public URL for webhook routing.

Frequently Asked Questions about public-ingress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I expose my local development environment to receive external webhooks?▼

You can expose a local development environment to external webhooks by establishing an ngrok-based tunnel. This creates a public URL that routes inbound traffic directly to your localhost gateway for platform integrations.

What is ngrok tunneling used for when handling local OAuth callbacks?▼

Ngrok tunneling provides a public ingress URL for local OAuth callbacks, allowing external services to reach your localhost. It handles authentication, port alignment, and persists the public URL configuration for routing.

Can I use a public URL to test Telegram webhooks on my local gateway?▼

Yes, you can test Telegram webhooks on a local gateway by generating a public URL via ngrok tunneling. The tunnel routes external Telegram webhook requests directly to your local development environment.

How to set up ngrok for local development ingress configuration?▼

Set up ngrok for local development ingress by starting a tunnel to your local gateway, verifying port alignment, and discovering the resulting public URL. The public URL is then persisted in the ingress configuration for platform integrations.

Does ngrok tunneling require port alignment checks for local gateway routing?▼

Yes, ngrok tunneling requires port alignment checks to ensure the public URL routes traffic to the correct local gateway port. This verification prevents inbound webhook and OAuth callback routing failures.

When do I need a public ingress URL for local development?▼

You need a public ingress URL when platform callback routing is unavailable and external services require a reachable URL. This occurs during local development when integrating external webhooks or OAuth callbacks.