> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-configuration/approval-automation/configuring-the-awa-email-capture-plug-in.md).
# Configuring the AWA Email-Capture Plug-In
### **Abstract**
Administrators must complete a few required setup steps before configuring *Approval Workflow Automation (AWA)* settings. One of the first tasks is enabling the email-capture plug-in, which allows *AWA* to receive and process approval instructions submitted via email. This setup supports workflows where users can approve transactions by replying to an email notification.\
\
This article explains how to configure the *AWA* email-capture plug-in in **Charted**.
### Configuring the AWA Email-Capture Plug-In
Configuring the *AWA* email-capture plug-in is one of the initial setup tasks after installing the *Approval-Automation Bundle*. This step allows the system to generate the unique email string required later in the approval workflow configuration.
Follow these steps to set up the *AWA* email plug-in:
1. After installing the **Approval-Automation Bundle**, you need to set up a couple of prerequisites before configuring **AWA** settings.\
2. First, set up the **email plug-in**. To do that, hover over the **Customization** menu, then **Plug-ins**, and select the **Custom Plug-in Types** option. This will take you to the **Manage Plug-In Implementations** page:\
3. On this page, check the **AWA EMAIL CAPTURE** box and click the **Save** button to apply the changes:\
\
\
This will generate an email string. It is recommended that you copy and paste it into a separate document, as you will need to paste it soon into the process.
This concludes the process of configuring the **AWA** email-capture plug-in.
---
# 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.charted.com/ap-automation/charted-configuration/approval-automation/configuring-the-awa-email-capture-plug-in.md?ask=&goal=
```
`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.