# Ask @ngrok about your endpoints and traffic in Slack

> Connect Slack to your ngrok account, then mention @ngrok in a channel to ask about your endpoints, traffic, usage, and limits and get the answer in a thread.

- Date: 2026-10-28
- Author: Joel Hans
- Products: Gateway
- URL: https://ngrok.com/changelog/ai-chat-agent-slack

When an endpoint misbehaves, your team probably asks about it in Slack first. Until now, someone had to find the answer in the dashboard and carry it back. With the AI Chat Agent, mention `@ngrok` with a question in plain language, and it checks your ngrok account and replies in a thread everyone in the channel can read.

![The AI Chat Agent settings page in the ngrok dashboard, in dark mode. An Example usage card shows a Slack exchange. You ask "@ngrok is there a pattern in the 404s hitting example.com?" The ngrok reply lists three patterns: /favicon.ico is the dominant path, probes hit /index.php, HEAD /sitemap.xml, and POST /signin, and many 404s come from 203.0.113.66, an IP on the spamhaus blocklists. Below the card, the Slack row has an Add to Slack button.](https://ngrok.com/blog-assets/images/2026-10-28-ai-chat-agent-slack/ai-chat-agent-settings-dark.png)

That exchange comes from our own Slack. We swapped the host and IP for documentation values. The agent grouped 404s from Traffic Inspector by path and client IP, and found mostly browsers asking for a missing `/favicon.ico` and a blocklisted scanner probing for PHP and sign-in pages. To follow up, mention `@ngrok` again in the thread, such as "show me one of those requests."

## What you can ask

The agent can look up:

- Endpoints, connected ngrok agents, and the requests and connections in [Traffic Inspector](https://ngrok.com/docs/obs/traffic-inspection).
- Gateway resources, such as domains, TCP addresses, IP policies, and certificates.
- Your account, team, usage, and limits, including which limits block your requests right now.
- The ngrok docs, so it can explain the `ERR_NGROK` code on an error page.

It also writes and validates [Traffic Policy](https://ngrok.com/docs/gateway/traffic-policy) rules, but it doesn't apply them. Copy the policy from the thread into your endpoint's configuration.

## What the agent can see and do

- It matches your Slack profile email to a member of the connected ngrok account and answers with that member's [role](https://ngrok.com/docs/iam/rbac).
- It reads messages that mention `@ngrok` and their threads. A mention that starts a new thread also gives it up to five earlier channel messages for context.
- It never returns secret values, authtokens, or API keys.
- It can't change your account. For an AI agent that makes changes, use the [ngrok MCP server](https://ngrok.com/docs/mcp-server).
- Your plan's Traffic Inspector retention sets how far back it can look at traffic.

The AI Chat Agent is available on the [Pay-as-you-go plan](https://ngrok.com/pricing). One ngrok account connects to one Slack workspace. Slack is the only chat platform today. Request Microsoft Teams or Discord support from the settings page.

## Get started

1. [Sign in to the dashboard](https://dashboard.ngrok.com/login) as an admin of a Pay-as-you-go account. New to ngrok? [Sign up](https://dashboard.ngrok.com/signup), then upgrade to Pay-as-you-go.
2. Open [**Settings → AI Chat Agent**](https://dashboard.ngrok.com/settings/ai-chat-agent) and click **Add to Slack**.
3. Pick your workspace in the Slack window and approve the install. A Slack workspace admin or owner must approve it.
4. Back in the dashboard, check that your workspace shows a **Connected** badge.
5. In Slack, run `/invite @ngrok` in a channel, then ask a question, such as `@ngrok which of my endpoints are online right now?`

The [AI Chat Agent docs](https://ngrok.com/docs/for-agents/ai-chat-agent) cover workspaces with more than one ngrok account, disconnecting, and troubleshooting.