> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/scanning/scanning-ci-cd-pipelines/integrating-source-control-platforms/app-pipeline-integration.md).

# App Pipeline Integration

The App method provides a seamless way to trigger pipeline scans without modifying the pipeline code. After installing and connecting a supported app, such as GitHub App or Bitbucket App, you can manage scan behavior using the OX platform.

This method is ideal for teams that want centralized control over scans without editing each repository’s configuration. It also enables advanced capabilities such as workflow assignment and selective scanning, defined per application inside the OX platform.

You can view or edit scan behavior under each application’s Pipeline Settings page once the integration is active.

#### App Integration in Pipeline Scanning

The App Integration method optimizes pipeline scanning by providing automation and centralized management. Once an app like GitHub or Bitbucket is installed and connected, it leverages OX platform features to streamline scanning processes.

**Key Advantages:**

* **Centralized Control**: Manage all scan settings through a unified interface without touching source code.
* **Advanced Customization**: Assign workflows and select specific scans tailored to each application's requirements.
* **Scalability**: Easily expand the scanning process across multiple applications or repositories with minimal setup.


---

# 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.ox.security/ox-code/scanning/scanning-ci-cd-pipelines/integrating-source-control-platforms/app-pipeline-integration.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.
