> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlog.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect your alerts, code, and cloud to Superlog, and see which integrations automations and tag mode can use.

Integrations connect Superlog to the tools you already use. Connect them once per workspace, then use them as automation triggers, as automation connectors, or as context for tag mode.

## Connect an integration

Click **Integrations** in the sidebar. Find the tool under **Marketplace** and click **Add**. Depending on the tool, you approve access in the provider's sign-in page, paste an API key, or deploy a template in your cloud account. Connected tools move to **Connected integrations**, where **Manage** opens their settings.

You can also connect a tool from the automation editor. Click **Connect** on a trigger or in the connector picker. Your draft stays open while you approve access.

Credentials are encrypted before storage and scoped to your workspace.

## What each integration does

| Integration | Automation trigger | Automation connector | Tag mode |
| - | - | - | - |
| [GitHub](/integrations/github) | — | Repositories, pull requests | Read-only code |
| [Slack](/integrations/slack) | Messages and mentions | Read and post messages | Where questions are asked |
| [Sentry](/integrations/sentry) | New issues and regressions | Read | Read |
| [Datadog](/integrations/datadog) | Through Slack alerts | Read | Read |
| [Linear](/integrations/linear) | — | Read, create issues | Read |
| [Discord](/integrations/discord) | `/automate` command | — | — |
| [Custom MCP](/integrations/custom-mcp) | — | All server tools | Read |
| [AWS](/integrations/cloud#aws) | Through Slack alerts | — | Read |
| [Google Cloud](/integrations/cloud#google-cloud) | — | — | Read |
| [Dash0](/integrations/more#dash0) | — | — | Read |
| [PostHog](/integrations/more#posthog) | Through Slack alerts | — | Read |
| [Grafana](/integrations/more#grafana) | Through Slack alerts | — | Read |
| [Axiom](/integrations/more#axiom) | — | — | Read |
| [ClickStack / HyperDX](/integrations/more#clickstack) | — | — | Read |
| [Langfuse](/integrations/more#langfuse) | — | — | Read |
| [Upstash](/integrations/more#upstash) | — | — | Read |
| [Supabase](/integrations/more#supabase) | — | — | Configurable |
| [Vercel](/integrations/more#vercel) | — | — | Read |

"Through Slack alerts" means the tool posts alerts to a Slack channel, and a Slack **New message in channel** trigger on that channel starts the run.

## How access is limited

* Most built-in integrations expose only read-only tools, plus the write actions listed above.
* Datadog and custom MCP servers pass their tools through without filtering. Supabase allows writes only if you choose **Full database SQL access**. Scope the credentials you give them.
* Provider credentials stay outside the agent's sandbox. Superlog calls the provider on the agent's behalf.
* If an integration cannot be reached during a run, the agent gets a reconnect tool with the error and decides whether to retry. The run continues.

See [Security](/security) for more detail.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.