---
title: "Ngrok integration for LuumenAI"
url: "https://www.luumen.ai/integrations/ngrok/"
entity: SoftwareIntegration
category: "Source control & CI/CD"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Ngrok integration for LuumenAI

Read ngrok edges and credentials, then change routing as an approved step

## What LuumenAI can do with Ngrok

LuumenAI connects to Ngrok with an API token and exposes 102 tools (56 read-only · 26 write · 20 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 102 tools (56 read-only · 26 write · 20 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: Source control & CI/CD

## About Ngrok with LuumenAI

Connect ngrok and Luumen can answer questions about your tunnels without you opening the dashboard: which edge routes exist, what IP restrictions and OIDC settings they carry, who holds tunnel credentials and API keys. When something needs to change — a new route, a fresh credential for an agent — Luumen shows the plan first and, by default, waits for your approval. Authentication is by API key.

## Example tools

Read-only (56 in total):

- `NGROK_GET_API_KEY` — Get the details of an API key by ID.
- `NGROK_GET_CREDENTIALS` — Retrieve detailed information about a tunnel authtoken credential by ID.
- `NGROK_GET_EDGE_ROUTE_BACKEND_MODULE` — Retrieves the backend module configuration for an HTTPS edge route.
- `NGROK_GET_EDGE_ROUTE_CIRCUIT_BREAKER_MODULE` — Retrieve the circuit breaker module configuration for a specific HTTPS edge route.
- `NGROK_GET_EDGE_ROUTE_COMPRESSION_MODULE` — Retrieves the compression module configuration for a specific HTTPS edge route.
- `NGROK_GET_EDGE_ROUTE_IP_RESTRICTION_MODULE` — Retrieves the IP restriction module configuration for a specific HTTPS edge route.
- `NGROK_GET_EDGE_ROUTE_OIDC_MODULE` — Retrieves the OIDC (OpenID Connect) module configuration for a specific HTTPS edge route.
- `NGROK_GET_EDGE_ROUTE_REQUEST_HEADERS_MODULE` — Retrieves the request headers module configuration for a specific HTTPS edge route.

Write and destructive (46 in total, subject to configured approval policy):

- `NGROK_CREATE_API_KEY` — Creates a new API key for authenticating with the ngrok API.
- `NGROK_CREATE_CREDENTIAL` — Creates a new tunnel authtoken credential for authenticating ngrok agents.
- `NGROK_CREATE_ENDPOINT` — Create a cloud endpoint on the ngrok account.
- `NGROK_CREATE_EVENT_SOURCE` — Add a new event source to an event subscription.
- `NGROK_CREATE_EVENT_SUBSCRIPTION` — Creates a new event subscription in ngrok.
- `NGROK_CREATE_HTTPS_EDGE` — Creates a new HTTPS edge in your ngrok account.
- `NGROK_CREATE_HTTPS_EDGE_ROUTE` — Creates a new route on an HTTPS edge in ngrok.
- `NGROK_CREATE_SSH_CREDENTIAL` — Creates a new SSH credential from an uploaded public SSH key.

## Frequently asked questions

### How does LuumenAI connect to Ngrok?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Ngrok on its own?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### Is there an audit trail?

Every call to Ngrok — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/ngrok/