> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.console/templates/events/custom-events/events-content-events.md).

# Content Events

## Create Content Event

1. Open Blynk.Console
2. Navigate to **Templates** -> Your Template
3. Click **Edit** button
4. Switch to **Events tab**
5. Click **Add New Event**
6. Select the type of event: **Content**
7. Fill in the fields:
   1. **Name** – name of the Event
   2. **Subtitle** – (e.g. category name, content type)
   3. **Image Link** – URL to an image that will be shown on the event card
   4. **Description** – event's reason and/or purpose, other information
   5. **Action Title** – description or appeal (e.g. “Get update”, “Proceed to the shop”) to Action Link
   6. **Action Link** – URL to new library, firmware, application version, your/partner's website, etc.
8. **Apply Tag** – enable for the Device to be tagged when this Event is recorded. The tag can’t be removed manually. When event is resolved, the tag will be removed automatically.
9. Switch to Notifications tab
10. Enable Notifications – lets you set notifications about events occured to Devices so you get them via SMS, Push or E-mail
11. Select the type of notification (email, push, sms) and recipients
12. Set [Notifications Limit](/en/blynk.console/templates/events/custom-events/events-content-events.md) if necessary and turn on [Notifications management](/en/getting-started/notification-management.md)
13. Click **Create** button
14. **Save** Template

## **Send API request**

The event content can be sent using the API by placing a request in the browser line now:

HTTPS API for Log event testing:

`https://{server_address}/external/api/logEvent?token={token}&code={event_name}`

`https://{server_address}/external/api/logevent?token={token}&code={event_name}&description={event_description}`

## **Check Content Event**

#### **Email: Check specified email**

### **Check your Device's Timeline:**

<figure><img src="/files/shIH1FnEwwyLOlFyfWMT" alt=""><figcaption></figcaption></figure>

**Web application**

1. Navigate to the Device which token you've specified in the request,
2. switch to Timeline tab
3. specify the time period you want to view and select the Content type of event
4. click Action Link

You will see all the content of this notification

**Mobile app:**

1. Sign in to Blynk.Apps
2. Go to the Notifications tab (29)
3. Follow this link (30)

You will see all the content of this notification


---

# 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://docs.blynk.io/en/blynk.console/templates/events/custom-events/events-content-events.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.