> For the complete documentation index, see [llms.txt](https://docs.sedai.io/get-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sedai.io/get-started/platform/integrations.md). # Integrations Learn how to connect IaC, notification, and ticketing integrations. To add an integration, navigate to the Settings > Integrations page and click the **Add Integration** button in the upper right-hand corner. You can also view, modify, and enable/disable existing integrations from this screen. ## Infrastructure as Code (IaC)


Bitbucket	iac_bitbuket.png	Infrastructure as Code (IaC)
GitHub	iac_github.png	Infrastructure as Code (IaC)
GitLab	Iac_gitlab.png	Infrastructure as Code (IaC)

*** ## Notifications


Asana	notification_asana.png	Notifications
Datadog	notification_datadog.png	Notifications
Jira	notification_jira.png	Notifications
Microsoft Teams	notification_mt.png	Notifications
PagerDuty	notification_pagerduty.png	Notifications
Slack	notification_slack.png	Notifications

*** ## Ticketing & Service Management


Jira	Ticketing & Service Management	ticketing_jira.png
ServiceNow	Ticketing & Service Management	ticketing_servicenow.png

*** {% hint style="info" %} Contact **** for help setting up custom runbook automations with StackStorm or Rundeck. {% endhint %} --- # 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.sedai.io/get-started/platform/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.