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

# Weights & Biases Webhook Setup Guide

> Configure Weights & Biases to deliver events to StackOne.

## Prerequisites

Before continuing, you should have already completed the following for this connector:

<Steps>
  <Step title="Configure the Connector">
    Enable the connector and set up its connector profile in your project. See <a href="/guides/explore-connectors">Managing Connectors</a>.

    <Columns cols={2}>
      <Card title="Connector Profile" href="/connectors/weightsandbiases/guides/connector-profile/api-key" icon="https://stackone-logos.com/api/weights-and-biases/icon/png" horizontal>
        Weights & Biases - API Key
      </Card>
    </Columns>
  </Step>

  <Step title="Link an Account">
    Connect an account using <a href="/guides/embedding-stackone-hub">StackOne Hub</a> or <a href="/guides/auth-link">Auth Link</a>.

    <Columns cols={2}>
      <Card title="Link Account" href="/connectors/weightsandbiases/guides/link-account/api-key" icon="https://stackone-logos.com/api/weights-and-biases/icon/png" horizontal>
        Weights & Biases - API Key
      </Card>
    </Columns>
  </Step>
</Steps>

<section data-guide-section data-guide-scopes="">
  <h2>1. Get your W\&B team slug</h2>

  <p>The team slug is the segment right after `wandb.ai/` in any W\&B URL. It also appears in the left sidebar of the W\&B home page.</p>

  <Steps>
    <Step title="Copy it from any W&B URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Open a team or project page. The part right after `wandb.ai/` is your team slug — for `https://wandb.ai/acme-research/model-training` the slug is `acme-research`.</p>
      </div>
    </Step>

    <Step title="Or read it from the sidebar">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Open <a href="https://wandb.ai/home" target="_blank" rel="noopener noreferrer">wandb.ai/home</a>. In the left sidebar, the <strong>Teams</strong> section lists every team you belong to — each entry is a team slug. Pick the one you want events for.</p>

        <img src="https://mintlify.s3.us-west-1.amazonaws.com/stackone-60/connectors/images/custom-webhook-team-slug.png" alt="Weights & Biases home page with the left sidebar Teams section highlighted, showing the team slug that also matches the URL segment used in W&B project links." />
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>2. Get your W\&B project names</h2>

  <p>Project names are the URL segment right after your team slug. StackOne registers one webhook trigger per project per event, so list them comma-separated.</p>

  <Steps>
    <Step title="Copy a name from any project URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Navigate to a project. The URL pattern is `https://wandb.ai/<team>/<project>` — the `<project>` part is the name to paste.</p>
      </div>
    </Step>

    <Step title="Or open your team's projects list">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Go to `https://wandb.ai/<team>/projects` (swap in your team slug). The <strong>Name</strong> column lists every project — each value is exactly what you paste into the connection.</p>

        <img src="https://mintlify.s3.us-west-1.amazonaws.com/stackone-60/connectors/images/custom-webhook-projects-list.png" alt="Weights & Biases team projects page with the Name column showing project slugs — matching the value used in per-project URLs and in the W&B Project Names field." />
      </div>
    </Step>

    <Step title="Enter them comma-separated">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>In <strong>W\&B Project Names</strong>, enter one or more names separated by commas with no spaces — for example `model-training,data-pipeline,experiments`. Toggling an event on then creates one trigger per project.</p>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>3. What happens after you enable an event</h2>

  <p>StackOne handles all W\&B provisioning through the GraphQL API — no clicks in the W\&B UI are needed after connect time.</p>

  <Steps>
    <Step title="One webhook per team + one trigger per project">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Each event you enable creates one webhook <strong>integration</strong> on your team (visible under <strong>Team Settings → Webhooks</strong>) and one <strong>automation trigger</strong> per project (visible in the team's <strong>Automations</strong> tab). Toggling the event off removes both.</p>
      </div>
    </Step>

    <Step title="The API key must belong to a team admin">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Creating integrations and triggers requires the API-key holder to be an <strong>admin or owner</strong> of the team named in <strong>W\&B Team</strong>. A non-admin key will fail when you enable an event.</p>
      </div>
    </Step>

    <Step title="Payloads are unsigned by default">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>StackOne registers webhooks without a signing secret because W\&B requires Team Secrets to be created manually in the UI (no public secrets API). Delivery authenticity relies on the unguessable callback URL. To turn on HMAC-SHA256 signatures, create a Team Secret in <strong>Team Settings → Secrets</strong> and edit the auto-generated integration to reference it — the `X-Wandb-Signature` header will then carry `HMAC-SHA256(rawBody, secretValue)` hex-encoded.</p>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.