> 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 Step-by-step integration guides for ZigiOps. Connect Jira, ServiceNow, Azure DevOps, Salesforce, and 60+ enterprise systems without writing a single line of code. 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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 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.