> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/integrations.md).

# Integrations

Soda offers seamless integrations with many tools across your data stack. Whether you're aligning data governance efforts, collaborating across teams, or triggering workflows, you can enhance Soda’s observability capabilities with the following connections:

## Supported integrations

### Messaging and collaboration

* [MS Teams](/integrations/ms-teams.md)
* [Slack](/integrations/slack.md)
* [Jira](/integrations/jira.md)
* [ServiceNow](/integrations/servicenow.md)
* [Webhook](/integrations/webhook.md)

> For more details on notification rules, see the [Notification rules documentation](/manage-issues/notifications.md).

### Catalogs and governance tools

* [Alation](/integrations/alation.md)
* [Atlan](/integrations/atlan.md)
* [Collibra](/integrations/collibra.md)
* [data.world](/integrations/data.world.md)
* [Metaphor](/integrations/metaphor.md)
* [Purview](/integrations/purview.md)

### BI tools

* [Sigma](/integrations/sigma.md)

### Data transformation and code repositories

* [GitHub](/integrations/github.md)

***

## Create an integration

To create an integration:

{% stepper %}
{% step %}
Go to the **Integrations** section in **Settings**.
{% endstep %}

{% step %}
Click the **+** button to add a new integration.
{% endstep %}

{% step %}
Select the integration type (**Slack**, **Microsoft Teams**, or **Webhook**).
{% endstep %}

{% step %}
Follow the setup steps for the chosen integration
{% endstep %}

{% step %}
Click **Save** to activate the integration.
{% endstep %}
{% endstepper %}

***

## Edit an integration

You can update existing integrations if connection details or configurations change.

To edit an integration:

{% stepper %}
{% step %}
Go to the **Integrations** section in **Settings**.
{% endstep %}

{% step %}
Find the integration you want to update.
{% endstep %}

{% step %}
Click the context menu and select **Edit Integration Settings**.
{% endstep %}

{% step %}
Update the configuration as needed.
{% endstep %}

{% step %}
Click **Save** to apply the changes.
{% endstep %}
{% endstepper %}

## Pause an integration

You can temporarily pause an integration if you want to stop sending notifications and incident updates without fully deleting the configuration. The integration will no longer be available in notification rules.

To pause an integration:

{% stepper %}
{% step %}
Go to the **Integrations** section in **Settings**.
{% endstep %}

{% step %}
Locate the integration you want to pause.
{% endstep %}

{% step %}
Change the status to "Paused" in the table
{% endstep %}

{% step %}
Select **Pause**.
{% endstep %}
{% endstepper %}

While paused, the integration will no longer send any notifications. You can resume it at any time by following the same steps and selecting **Active**.

<br>

***

{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/reference/documentation-access-and-licensing.md).
{% 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.soda.io/integrations.md?ask=<question>&goal=<user_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.