> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/power-platform-and-logic-apps.md).

# Power Platform & Logic Apps

The **9A Raptor Document Warehouse connector** provides a standardized integration layer between the Raptor document management platform and Microsoft Power Platform services, including Power Automate, Azure Logic Apps, and Copilot Studio. It exposes a set of actions and triggers that allow workflows to interact directly with the Raptor API in a secure and scalable manner.

The connector supports core document management operations such as retrieving documents and metadata, uploading and updating files, and executing repository-specific actions. These operations can be embedded into automated flows, enabling event-driven and scheduled processes that interact with the document warehouse as part of larger enterprise integrations.

For details, refer to the official documentation:\
<https://learn.microsoft.com/en-us/connectors/raptordocmanagement/>

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-06826d1d0515548d1c1be318b158d7abdf399666%2Fimage%20(4).png?alt=media" alt=""><figcaption><p>The Raptor Document Warehouse connector being used in a Power Automate flow</p></figcaption></figure>


---

# 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.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/power-platform-and-logic-apps.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.
