> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/document-intelligence/integrations/email-inbox.md).

# Email Inbox

Process emails & documents pulled automatically from your email inbox.

#### Allowed Domains

Any email sent from these domains will be processed. You may only specify domains from your Feathery account emails.

#### Allowed Addresses

Any email sent from these addresses will be processed. You may only specify addresses from your Feathery account emails.

#### Recipient Extension

If specified, only emails sent to <documents+@feathery.io> will trigger this extraction

#### New Form Submissions

(Optional) Automatically start new form submissions from the extracted document data.

#### Extract Linked Files

Toggle to extract files that are hyperlinked inside of the email content.

#### Ignore Emails with No Attachments

Toggle to only process emails that have file attachments

#### Notify on Emails with No Attachments

If emails without attachments are ignored, select addresses to notify when an email with no attachments is received.

#### Save Email Information

Save information from processed emails to hidden fields. Email data that can be saved includes:

* Subject
* Body
* Sender Name
* Sender Email
* Email Attachments

#### Configure Groups for Email Forwarding

You can configure email groups that can be accessed within server-side logic rules for email forwarding. Email groups require a non-empty name and a list of emails belonging to the group. You may only specify domains from your Feathery account emails.

The usage within the logic rule is `await feathery.forwardInboxEmail(<group_name>)` where the `<group_name>` is a string reflecting the name of the email group configured on the integration. This will forward the email that triggered the extraction to the list of configured recipients.

<div align="center"><figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2Fws2eZgGrIligCu4O3pWb%2Fimage.png?alt=media&amp;token=1ed7ba9f-7784-48f0-99f1-dd81d1bc03df" alt="" width="359"><figcaption></figcaption></figure></div>


---

# 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.feathery.io/platform/document-intelligence/integrations/email-inbox.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.