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

# Integrating Varo Cloud with GitHub, Slack, and Datadog

> Connect Varo Cloud to GitHub, Slack, Datadog, and other tools. Automate deployments, route alerts, and sync metrics with your existing stack.

Varo Cloud integrates with the tools your team already uses so you can automate deployments, route notifications to the right channels, and pipe metrics into your existing observability stack — without changing the way you work. Integrations are managed from **Settings → Integrations** in your dashboard at [varo.cloud](https://varo.cloud).

## Available integrations

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/guides/integrations#connect-github">
    Automatically trigger a deployment whenever you push to a branch or merge a pull request. Map branches to environments so `main` always deploys to production and `dev` deploys to staging.
  </Card>

  <Card title="Slack" icon="slack" href="/guides/integrations#connect-slack">
    Receive deployment notifications directly in your Slack channels. Choose which events to surface — deployment started, succeeded, or failed — and which channels should receive them.
  </Card>

  <Card title="Datadog" icon="chart-line" href="/guides/integrations#cicd-pipeline-integration">
    Forward application metrics and structured logs from your Varo Cloud deployments to Datadog. Correlate deployment events with your existing dashboards and alerting rules. Requires a Pro or Enterprise plan.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/api-reference/webhooks">
    Send deployment lifecycle events to any HTTP endpoint you control. Use webhooks to build custom automations, update internal tooling, or fan out notifications to systems not covered by native integrations.
  </Card>
</CardGroup>

## Connect GitHub

Connecting GitHub lets Varo Cloud watch your repositories and trigger deployments automatically when you push new code.

<Steps>
  <Step title="Open the GitHub integration settings">
    In your dashboard, go to **Settings → Integrations → GitHub**.
  </Step>

  <Step title="Click Connect GitHub">
    Click the **Connect GitHub** button to start the OAuth flow.
  </Step>

  <Step title="Authorize the OAuth app">
    You will be redirected to GitHub. Review the requested permissions and click **Authorize VaroCloud**. You will be returned to your dashboard once authorization is complete.
  </Step>

  <Step title="Select repositories">
    Choose which repositories Varo Cloud should have access to. You can grant access to all repositories in your GitHub organization or select specific ones.
  </Step>

  <Step title="Configure auto-deploy rules">
    For each repository, define branch-to-environment mappings. For example, map the `main` branch to your `production` environment and the `develop` branch to `staging`. Varo Cloud will automatically queue a deployment whenever a push is detected on a mapped branch.
  </Step>
</Steps>

## Connect Slack

Slack notifications keep your team informed about deployment activity without anyone needing to watch the dashboard.

<Steps>
  <Step title="Open the Slack integration settings">
    In your dashboard, go to **Settings → Integrations → Slack**.
  </Step>

  <Step title="Click Add to Slack">
    Click the **Add to Slack** button. You will be redirected to Slack to authorize the Varo Cloud app for your workspace.
  </Step>

  <Step title="Choose a notification channel">
    After authorizing, select the Slack channel where Varo Cloud should post messages. You can configure separate channels for different projects or environments.
  </Step>

  <Step title="Select notification events">
    Choose which deployment events trigger a message:

    * **Deployment started** — notifies your team when a new build begins
    * **Deployment succeeded** — confirms when a deployment goes live
    * **Deployment failed** — alerts your team immediately if a build or deploy step fails
  </Step>
</Steps>

## CI/CD pipeline integration

If your team uses a CI/CD pipeline, you can call the Varo Cloud API directly from your workflow to trigger a deployment after your tests pass. The example below shows a GitHub Actions workflow that deploys to production on every push to `main`.

```yaml theme={null}
name: Deploy to Varo Cloud
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger deployment
        run: |
          curl -X POST https://inference.varo.cloud/v1/deployments \
            -H "Authorization: Bearer ${{ secrets.VARO_API_KEY }}" \
            -H "Content-Type: application/json" \
            -d '{"project_id": "${{ vars.VARO_PROJECT_ID }}", "environment": "production"}'
```

Store your API key as an encrypted secret (`VARO_API_KEY`) and your project ID as a repository variable (`VARO_PROJECT_ID`) in your GitHub repository settings. Never commit credentials directly in your workflow file.

## Custom webhooks

For events or destinations not covered by the built-in integrations, you can configure a custom webhook to POST deployment lifecycle events to any endpoint you control. See the **API Reference → Webhooks** page for the full list of event types, payload schemas, and signature verification details.

<Note>
  Integration availability depends on your Varo Cloud plan. GitHub and Slack integrations are available on all plans, including Starter. Datadog integration requires a **Pro** or **Enterprise** plan. Custom webhooks are available on all plans.
</Note>