> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-to-email-rule.md).

# LCT - To Email Rule

The To Email Rule allows users to define specific alarm types and designate up to 5 email recipients. When the selected alarm type is triggered, an email notification is sent to the specified recipients, ensuring timely alerts.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfnXt2VeRZt0K_m2_7Bo4qkkyGU82u2fqDGoI97P27BNM9l8ncmAUTTjBUpRTeuEUc3K4ZPkfOOiUULnv2X5lD8843bRbjx7eNbUcYea35z2p17oVxqiVLjeWO18daNVT69yVOk?key=Kl1KyU1gDzenB_F0xjN17rry" alt=""><figcaption><p>LCT Send Email Rule</p></figcaption></figure>

## Steps to Set Up the To Email Rule for LCT:

1. **Access the Rule Page:**\
   Navigate to the **LCT device**, open the **Device Dashboard**, go to the **Rules** section, click on the **+** icon, and select the **To Email Rule**.
2. **Activate the Rule:**\
   Toggle the switch at the top to enable the rule.
3. **Enter Rule Name:**\
   Provide a name to identify the rule.
4. **Select Alarm Type:**\
   Type in the name of the alarm (e.g., `giot-temperature-min-alarm`, `device-tamper-alarm`, `device-temperature-max-alarm`, `device-motion-start-alarm`) to trigger the email notification.
5. **Add Email Recipients:**\
   Input up to 5 email addresses for the intended recipients of the alarm notifications.
6. **Click Save:**\
   Save the rule to finalize the configuration. The designated email recipients will now receive notifications whenever the specified alarm is triggered.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-to-email-rule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.