# Typical Integration Flow

This section outlines the standard workflow used by CI/CD systems to authenticate, trigger Drizz test executions, and evaluate results as part of automated build and release pipelines.

### End-to-End Pipeline Flow:

1. CI/CD pipeline requests an Auth0 access token
2. Optional: Uploads a new APK build artifact
3. Triggers one or more Drizz test plans
4. Parses execution response for status and execution IDs
5. Fails or passes the pipeline based on test execution outcome


---

# Agent Instructions: 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:

```
GET https://docs.drizz.dev/drizz-api-integration/ci-cd-platform-integration/typical-integration-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.