> For the complete documentation index, see [llms.txt](https://degreetpro.gitbook.io/nestgram/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://degreetpro.gitbook.io/nestgram/handling-updates/entities-url-email-and-other.md).

# Entities: url, email and other

## What are entities?

Entity it's part of a message with unique content (e.g. url, email, phone\_number, hashtag, cashtag and other). You can read about entity and see all entity types [here](https://core.telegram.org/bots/api#messageentity)

## Listen to text message with some entity

To listen to a text message with some entity, use `@OnEntity` decorator

{% hint style="info" %}
Optional. `@OnEntity` takes the entity type that you want to listen to as argument
{% endhint %}

{% code title="app.controller.ts" %}

```typescript
import { OnEntity, Controller } from 'nestgram';
import { AppService } from './app.service';

@Controller()
export class AppController {
  constructor(private readonly appService?: AppService) {}

  @OnEntity('email')
  async onEmail(): Promise<string> {
    return 'I got your email!';
  }
}
```

{% endcode %}

## Get entity from a text message

To get an entity from a text message, use @Entity parameter decorator, and pass the entity type you want to get

{% hint style="info" %}
Optional. `@Entity` takes the entity type you want to get to as argument
{% endhint %}

{% code title="app.controller.ts" %}

```typescript
import { OnEntity, Controller, Entity, IEntity } from 'nestgram';
import { AppService } from './app.service';

@Controller()
export class AppController {
  constructor(private readonly appService?: AppService) {}

  @OnEntity('email')
  async onEmail(@Entity('email') email: IEntity): Promise<string> {
    return `I got your email! ${email?.result}`;
  }
}
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://degreetpro.gitbook.io/nestgram/handling-updates/entities-url-email-and-other.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.