# CircleCI

### What is CircleCI integration in ZigiOps?

CircleCI is a cloud-based continuous integration and delivery (CI/CD) platform used to automate build, test, and deployment pipelines.

ZigiOps enables secure, agentless integration between CircleCI and ITSM, DevOps, and enterprise systems. Using ZigiOps, CircleCI build events, pipeline results, and related metadata can be synchronized with downstream systems to support DevOps-to-ITSM workflows and automated operational processes.

With ZigiOps, CircleCI can:

* Trigger incidents or tasks based on pipeline failures
* Send build and job information to ITSM systems
* Support CI/CD-driven automation workflows
* Integrate without custom scripts or plugins

### Which CircleCI versions are supported?

Using a supported version is mandatory.

| Product  | Supported Deployment Types | Supported Versions |
| -------- | -------------------------- | ------------------ |
| CircleCI | All                        | All                |

### Are there any environmental prerequisites for CircleCI?

**Note:** There are no environmental prerequisites for this product.

Before configuring CircleCI, always confirm the prerequisites of the corresponding integration template, as some templates may introduce additional requirements.

> See the **Related Templates** section at the end of this page.

### How do I connect CircleCI to ZigiOps?

#### CircleCI - Connected System Configuration

Follow the steps below to add CircleCI as a connected system in ZigiOps.

{% stepper %}
{% step %}
Log in to ZigiOps

Log in to your **ZigiOps** instance.
{% endstep %}

{% step %}
Add CircleCI as a connected system

Navigate to **Connected Systems > Add New System > CircleCI**.
{% endstep %}

{% step %}
Configure the following parameters

**Server URL**\
Enter the URL of your CircleCI instance.\
Example: `https://circleci.com`

**API Key**\
Enter the API key used for authentication against your CircleCI instance.

**VCS**\
Enter the version control system used with CircleCI.\
Example: `github`

**Organization**\
Enter the name of your CircleCI organization.\
Example: `zigiwave`

**Proxy Settings (optional)**\
Enable this option if a proxy server is required for outbound communication.
{% endstep %}

{% step %}
Review and save the configuration

Review the configuration.

Click **Save** to store the connected system.
{% endstep %}
{% endstepper %}

Once saved, CircleCI becomes available for use in ZigiOps integration templates.

### What are the most common CircleCI integration use cases?

#### Use case 1: Creating ITSM incidents from failed pipelines

When CircleCI pipelines or jobs fail, ZigiOps can forward the failure details to ITSM systems, automatically creating incidents or tasks with contextual build information.

#### Use case 2: CI/CD-driven DevOps workflows

CircleCI build and job data can be synchronized with DevOps and ITSM platforms, enabling traceability between code changes, builds, and operational issues.

#### Use case 3: Automated operational response

ZigiOps can trigger automated workflows based on CircleCI events, allowing organizations to respond to build and deployment issues without manual intervention.

### What integration templates are available for CircleCI?

ZigiOps provides prebuilt integration templates for CircleCI, documented individually in the Integration Catalog.

#### Related Templates

For detailed information about available CircleCI integration templates, please contact:

**Email:** <support@zigiwave.com>

Each template includes:

* Predefined entity mappings
* Direction of synchronization
* Entity-specific logic and filtering rules

### Summary

The CircleCI integration in ZigiOps enables:

* Secure, agentless connectivity to CircleCI
* Support for all CircleCI versions and deployment models
* API key-based authentication
* Optional proxy support
* Ready-to-use templates for CI/CD and ITSM workflows


---

# Agent Instructions: 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:

```
GET https://docs.zigiwave.com/available-systems/circleci.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.