> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/integrations/enate-integrations/sample-extracting-email-and-attachments-to-sharepoint-with-power-automate.md).

# Extract Emails & Attachments to SharePoint with Power Automate

Check out this explainer for how to use Power Automate to search for the latest email from an Enate Case work item, and then extract that Email and its attachments to a SharePoint directory.

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM5Nzk3MQ==>" %}

You can even download this Power Automate flow from Enate's GitHub page to get you up and running quickly with this:

{% embed url="<https://github.com/EnateLtd/Power-Flow-to-Export-Attachments-from-Enate-to-Sharepoint>" %}

Check out our Power Automate section for more information about how to integrate it with Enate here:

{% content-ref url="/pages/-M\_\_4VQhscfv-KXdDSIx" %}
[Power Automate](/enate-help/integrations/enate-integrations/power-automate.md)
{% endcontent-ref %}


---

# 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.enate.net/enate-help/integrations/enate-integrations/sample-extracting-email-and-attachments-to-sharepoint-with-power-automate.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.