Ngrok, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Ngrok account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Developer Tools
- Connects with a key
- 9 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Ngrok is
Ngrok creates secure tunnels to locally hosted applications, enabling developers to share and test webhooks or services without configuring complex network settings
You paste in a key from your own Ngrok account. It is kept encrypted, and you can withdraw it from inside Ngrok whenever you like.
One message in, the work done in Ngrok.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Ngrok. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Ngrok account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Ngrok
These are the ready-made tools your AI employee already has in Ngrok. It is not limited to them, but it never has to be taught these.
- Create API KeyCreates a new api key for authenticating with the ngrok api. this tool allows programmatic creation of api keys that can be used to access ngrok's api services.
- Delete API KeyDelete an api key by its id. this action permanently removes the specified api key from your ngrok account. this is an important security feature that allows users to revoke access
- Get IP Restriction DetailsThis tool retrieves detailed information about a specific ip restriction by its id. it is used to control which ip addresses can access ngrok resources, including the api, by fetch
- List Active TunnelsList all active tunnels in the ngrok account. this tool lists all active tunnels in the ngrok account, providing details such as tunnel id, public url, start time, protocol, config
- List All EndpointsList all active endpoints on the ngrok account. this tool will list all active endpoints on the ngrok account, providing visibility into running tunnels and endpoints. it requires
- List API KeysThis tool lists all api keys owned by the user. the api keys are used to authenticate api requests to ngrok's rest api. the endpoint returns a paginated list of api keys.
- List HTTPS EdgesLists all https edges in your ngrok account. https edges are configurations that tell ngrok how to handle https traffic. the action returns a paginated list of all https edges asso
- List IP Policy RulesThis tool lists all ip policy rules associated with your ngrok account. it retrieves detailed information including rule id, creation timestamp, description, metadata, cidr, the as
- List IP RestrictionsThis tool retrieves a list of all ip restrictions configured on the ngrok account. it allows users to audit and review all ip-based access restrictions on their ngrok account for e
You stay the boss of your Ngrok account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Ngrok account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Ngrok is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Ngrok and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Ngrok
- Can an AI employee really work inside Ngrok?
- Yes. It signs in to your own Ngrok account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Ngrok?
- No. Nothing moves and nothing is replaced. Your records stay in Ngrok, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Ngrok account?
- You paste in a key from your own Ngrok account. It is kept encrypted, and you can withdraw it from inside Ngrok whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Ngrok?
- It has 9 ready-made tools in Ngrok today, among them Create API Key, Delete API Key and Get IP Restriction Details. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Ngrok and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Ngrok and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Ngrok?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Ngrok is written down with what it did and when.