> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/integrations.md). # Integrations Connect Argos to your Git provider for pull request statuses, authenticate your CI uploads, and get notified in Slack. Argos integrates with your Git provider to post build statuses on pull requests, and with Slack, Microsoft Teams, or Discord to notify your team. Which notifications go where is decided by [automations](/docs/learn/review-workflow/automations.md). ### Git providers * [GitHub integration](/docs/learn/integrations/github-integration.md) – Install the Argos GitHub App for statuses, comments, and merge queue support * [GitLab integration](/docs/learn/integrations/gitlab-integration.md) – Connect GitLab to get statuses on merge requests * [Other Git providers](/docs/learn/integrations/other-git-providers.md) – Bitbucket and Azure DevOps status, and how to use Argos without a native integration ### CI authentication * [GitHub Actions authentication](/docs/learn/integrations/github-actions-authentication.md) – Authenticate uploads with a token, OIDC, or tokenless authentication {% hint style="info" %} Looking for how to sign in to Argos itself? See [Account & access](/docs/learn/account-and-access.md) for GitHub and SAML single sign-on. {% endhint %} ### Notifications * [Slack integration](/docs/learn/integrations/slack-integration.md) – Send build notifications to Slack channels with automations * [Microsoft Teams integration](/docs/learn/integrations/microsoft-teams-integration.md) – Send build notifications to a Teams channel with automations * [Discord integration](/docs/learn/integrations/discord-integration.md) – Send build notifications to a Discord channel with automations ### Webhooks Argos does not offer user-configurable outgoing webhooks. To react to build events, use [Slack](/docs/learn/integrations/slack-integration.md), [Microsoft Teams](/docs/learn/integrations/microsoft-teams-integration.md), or [Discord](/docs/learn/integrations/discord-integration.md) notifications, the commit statuses posted on your Git provider, or poll builds from the [REST API](https://argos-ci.com/docs/api-reference) or the [CLI](/docs/reference/argos-command-line-interface-cli.md#inspecting-builds-and-tests). If webhooks would unblock your workflow, [tell us about your use case](https://argos-ci.com/contact). --- # 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://argos-ci.com/docs/learn/integrations.md?ask=&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.