> ## Documentation Index > Fetch the complete documentation index at: https://docs.rubixkube.ai/llms.txt > Use this file to discover all available pages before exploring further. # Integrations overview > The two ways to connect a tool to RubixKube: alert sources that open incidents, and connections Rubix can read. You already have tools that watch your systems and hold your team's knowledge. Connecting them means RubixKube hears about problems sooner, and Rubix has more to read when it works out why. There are two ways to connect a tool. An alert source sends RubixKube a webhook, and its events become incidents. A connection lets Rubix read a tool while it investigates and chats with you. Many tools can do both, and you set each one up separately. ![Alert sources send webhooks into RubixKube and create incidents. Connections let Rubix read the tool. Do both for the best result](https://mintcdn.com/rubixkube/SyizuPSfyhbZBL9u/images/guides/two-ways-light.png?fit=max\&auto=format\&n=SyizuPSfyhbZBL9u\&q=85\&s=a8813b173899abfecd22f8b66badcd40) ## Which one do you need? * **You want Datadog alerts to become incidents.** Set up an alert source. * **You want Rubix to read Datadog logs in an RCA.** Add a connection. * **You want both.** An RCA is only as good as what Rubix can read, so a webhook alone gives it less to work with. * **You want Rubix to read your code or docs.** GitHub, GitLab and Notion are connections. * **Your tool isn't listed, or it's your own system.** Use [your own webhook](https://docs.rubixkube.ai/integrations/webhooks.md) to send alerts, or a [custom integration](#your-own-tools) so Rubix can read it. ## Alert sources An alert source is a tool that tells RubixKube when something breaks. It connects like any other source, under **Environments > Connect**. You pick the tool and RubixKube makes it a webhook of its own. You paste that URL into the tool. The source registers itself and shows up on **Environments**, and a built-in automation turns its events into incidents. Each tool's page lists exactly which events open an incident and which resolve it. ## Connections A connection lets Rubix read a tool. It adds evidence to an RCA and answers to your questions in chat. For example, Rubix can look through Datadog logs for `payments-api` while it works out why the service is crash-looping. ![Customize, Integrations page with tools in use and more to add](https://mintcdn.com/rubixkube/uw89AXMFP3BXpNNP/images/console/customize-integrations-light.png?fit=max\&auto=format\&n=uw89AXMFP3BXpNNP\&q=85\&s=6a7e2c9187dc198ce6d796e236a5d029) An admin connects a tool under **Customize > Integrations**. Open a tool under **Add more** and sign in, or paste a token, depending on what the tool offers. Some tools ask for a site, region or customer id first. A few need an admin at the other tool to allow RubixKube before anyone can sign in, and the page tells you when that's the case. See [Sign-in and tokens](https://docs.rubixkube.ai/integrations/oauth-and-auth-types.md). A connection's **Tools** list shows everything the tool offers, with a switch for each one. During an RCA, Rubix only calls tools that read. In chat, any tool that changes something follows your [modes](https://docs.rubixkube.ai/using/modes.md). ## What's available in each | Tool | Alert source | Connection | | - | - | - | | [Datadog](https://docs.rubixkube.ai/integrations/datadog.md) | Yes | Yes | | [PagerDuty](https://docs.rubixkube.ai/integrations/pagerduty.md) | Yes | Yes | | [Grafana](https://docs.rubixkube.ai/integrations/grafana.md) | Yes | Grafana Cloud | | [Sentry](https://docs.rubixkube.ai/integrations/sentry.md) | Yes | Yes | | [Jira](https://docs.rubixkube.ai/integrations/jira.md) | Yes | Through [Atlassian Rovo](https://docs.rubixkube.ai/integrations/atlassian-rovo.md) | | [Linear](https://docs.rubixkube.ai/integrations/linear.md) | Yes | Yes | | [Observe](https://docs.rubixkube.ai/integrations/observe.md) | Yes | Yes | | [Your own webhook](https://docs.rubixkube.ai/integrations/webhooks.md) | Yes | No | | [GitHub](https://docs.rubixkube.ai/integrations/github.md), [GitLab](https://docs.rubixkube.ai/integrations/gitlab.md), [Notion](https://docs.rubixkube.ai/integrations/notion.md), [New Relic](https://docs.rubixkube.ai/integrations/new-relic.md) | No | Yes | The [catalog](https://docs.rubixkube.ai/integrations/catalog.md) has the full list. ## See what a connection can read A connection that signs in doesn't always reach anything useful. A token can have the wrong scope, or the logs can live somewhere else. So RubixKube checks. After you connect, sign in or press **Test**, RubixKube makes real reads against the tool over the last hour. The tool's **Reads** section shows one row for each kind of evidence, such as Logs, Metrics, Alerts or Tickets, and each row says what happened. | Status | What it means | | - | - | | Reads | Rubix read data from this place | | Nothing in the last hour | The read worked and came back empty | | Refused | The tool said no. The row shows its words and the fix | | Failed | The read didn't work. The row shows the error | The same rows appear on an alert source's page under **Environments**. Datadog, PagerDuty, Observe and Atlassian Rovo get a read for each kind of evidence. Other tools get one read that shows the connection answers. ## Your own tools To connect something that isn't in the catalog, choose **Add your own** under **Customize > Integrations**. You can add an [MCP server](https://docs.rubixkube.ai/integrations/custom-mcp-servers.md) or a [REST API](https://docs.rubixkube.ai/integrations/custom-rest.md). Custom integrations are **Business and Enterprise**. ## Related pages > [card] [Catalog](https://docs.rubixkube.ai/integrations/catalog.md) > > Everything you can connect. > [card] [Your own webhook](https://docs.rubixkube.ai/integrations/webhooks.md) > > Send incidents from anything that can post JSON. > [card] [Slack](https://docs.rubixkube.ai/integrations/slack.md) > > Talk to Rubix and follow incidents in Slack. > [card] [Rubix MCP](https://docs.rubixkube.ai/integrations/mcp.md) > > Use RubixKube from your AI tools. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.