> For the complete documentation index, see [llms.txt](https://docs.zigiwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigiwave.com/integration-guides.md). # Integration Guides This section contains detailed, step-by-step guides for every integration available in ZigiOps. Whether you are connecting Jira with ServiceNow, syncing Azure DevOps with Salesforce, or automating incident data between monitoring and ITSM tools, each guide walks you through the full setup process from start to finish. Each integration guide covers the required prerequisites, connected system configuration, template loading, field mapping, and any system-specific notes you need to know before going live. You do not need coding or API knowledge to follow these guides. ZigiOps handles all communication between systems through its no-code interface. Use the links below to navigate to the integration you need. If you are looking for a specific system's connection setup rather than a full integration walkthrough, visit the [Supported Systems](https://docs.zigiwave.com/available-systems) page instead. ### **Integration Guides** * Jira and ServiceNow Integration Guide * Jira and Azure DevOps Integration Guide * Jira and Salesforce Integration Guide * Jira and Remedy Integration Guide * ServiceNow and Azure DevOps Integration Guide --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zigiwave.com/integration-guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.