Sanaf AI
Start free
URL Shortener

L2s, 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 L2s 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.

  • URL Shortener
  • Connects with a key
  • 4 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What L2s is

L2S is a professional URL shortener offering advanced analytics, QR code generation, and team collaboration features.

You paste in a key from your own L2s account. It is kept encrypted, and you can withdraw it from inside L2s whenever you like.

How a run works

One message in, the work done in L2s.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in L2s. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own L2s account, inside the access you granted it, doing the thing you asked for.

  4. 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.

4 tools it already has

What it can do in L2s

These are the ready-made tools your AI employee already has in L2s. It is not limited to them, but it never has to be taught these.

  • Get URL DetailsTool to retrieve details of a shortened url. use when you need metadata about a specific shortened link. use after obtaining a valid url id.
  • Get User SettingsTool to retrieve current user's settings. use after authentication to fetch email, notification, and appearance preferences.
  • List Shortened URLsTool to list all shortened urls. use after user authentication to retrieve the user's urls with pagination details.
  • Shorten URL with L2STool to shorten a given long url. use when you need a concise link representation.
Access, and who is in charge of it

You stay the boss of your L2s 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 L2s 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 L2s is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in L2s 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.

See every app

Questions people ask about L2s

Can an AI employee really work inside L2s?
Yes. It signs in to your own L2s 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 L2s?
No. Nothing moves and nothing is replaced. Your records stay in L2s, 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 L2s account?
You paste in a key from your own L2s account. It is kept encrypted, and you can withdraw it from inside L2s 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 L2s?
It has 4 ready-made tools in L2s today, among them Get URL Details, Get User Settings and List Shortened URLs. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use L2s 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 L2s 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 L2s?
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 L2s is written down with what it did and when.