> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/integrations.md).

# Integrations

- [Integrations Overview](https://learning.contextqa.com/integrations/integrations.md): A guide to all the systems ContextQA connects with, including bug trackers, CI/CD pipelines, project management tools, and notification systems.
- [Jira](https://learning.contextqa.com/integrations/jira.md): Connect ContextQA to Jira to generate test cases from tickets, report defects with AI root cause analysis, and sync test execution status bidirectionally.
- [Azure DevOps](https://learning.contextqa.com/integrations/azure-devops.md): Connect Azure DevOps to ContextQA, generate tests from Azure Boards work items, report failed runs as bugs, and link execution evidence.
- [GitHub Actions](https://learning.contextqa.com/integrations/github-actions.md): Prepare GitHub Actions secrets, variables, triggers, and branch protection for a ContextQA test-plan quality gate.
- [Jenkins](https://learning.contextqa.com/integrations/jenkins.md): Prepare Jenkins credentials, pipeline stages, timeouts, and build-result handling for a ContextQA test-plan quality gate.
- [GitLab CI](https://learning.contextqa.com/integrations/gitlab-ci.md): Prepare GitLab CI/CD variables, stages, environments, and result handling for a ContextQA test-plan quality gate.
- [CircleCI](https://learning.contextqa.com/integrations/circleci.md): Prepare CircleCI variables, contexts, workflows, and result handling for a ContextQA test-plan quality gate.
- [Slack](https://learning.contextqa.com/integrations/slack.md): Connect Slack, choose an organization or workspace notification channel, and recover missing permissions or private-channel access safely.
- [Webhooks](https://learning.contextqa.com/integrations/webhooks.md): ContextQA webhook notifications — send test plan results to any HTTP endpoint on completion, enabling integrations with PagerDuty, custom dashboards, and internal tools.


---

# 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://learning.contextqa.com/integrations.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.