> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog.md). # Provider Catalog Connect your services to StackAI and choose the actions your workflows need. Integrations let your agents and workflows use the services your team already works with. Select a provider from the sidebar to find its connection methods, available actions, and event triggers. ### Choose the capability you need * **Connections** give StackAI access to a provider account. The connector defines how you sign in. * **Actions** perform a task in the connected service, such as finding a record or updating an item. * **Triggers** start a workflow when a configured event occurs. * **Knowledge retrieval** uses connected content as a source for answers. Each provider page identifies the supported retrieval methods. ### Before you connect Use an account with access to the records and operations your workflow needs. Check the provider page for required permissions and configuration. Some capabilities depend on your deployment or organization settings. ### Find a provider Browse the 514 provider entries under Integrations, or use search to find a provider by name. Each entry lists the capabilities defined in the provider catalog. Deprecated or unavailable integrations are marked on their pages. --- # 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.stackai.com/integrations/catalog.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.