> For the complete documentation index, see [llms.txt](https://changelog.impler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.impler.io/july-2024/v0.22.0-email-alerts-sdk-optimization-and-enhancements.md).

# v0.22.0: Email Alerts, SDK Optimization, and Enhancements

Introducing time and effort-saving features and enhancements to level up the data import process in any product.

### ✨ New Features

* **Email Alerts:** Impler will send email alerts for cases like webhook data sending fails, bubble data sending fails or validation code throws any error.
* **Close Widget Method:** Exported `closeWidget` method from react hook to close import widget programmatically.

### ➕ Enhancements

* **Null as default value:** By default newly created columns and bubble-mapped columns will have `null` as default value.
* **SDK Size Optimization:** Reduced react SDK size by 70%.
* **Services Library:** Separated reusable services from `@impler/shared` to `@impler/services` package.

### 🔧 Bug Fixes

* **Data seeding issue:** Fixed provided data was only filling one row.

**Stay Connected and Share Your Thoughts**

We’re constantly improving how to deliver the best CSV Excel Import Experience for your product, and we value your input.

Your feedback is crucial in guiding our development efforts and making Impler better. Feel free to send a message to <bhavik@impler.io> and join our [Discord](https://discord.impler.io).


---

# 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://changelog.impler.io/july-2024/v0.22.0-email-alerts-sdk-optimization-and-enhancements.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.