Connect CrewAI Cloud

In CrewAI Cloud → open the deployment for the crew you want Dobby to observe → Status tab → copy the Bearer Token.

You’ll paste this into Dobby’s wizard in the next step. Same token will also appear in your kickoff payload — Dobby validates the two match so we know the webhook is really from your crew.

In Dobby → Workloads → Connect Workflow → CrewAI Cloud. Pick the default Paste token mode and paste the bearer from step 1. Dobby encrypts it server-side with your tenant key (AES-256-GCM) and stores ciphertext only — no GCP Secret Manager access needed on your side.

The wizard will probe the token shape, then create a connector and emit your webhook URL on the final step. It looks like:

https://dobby-ai.com/api/v1/webhooks/workloads/wc_xxxxxxxxxxxx

CrewAI Cloud doesn’t expose a UI for saving webhook config at the crew level, so the webhook lives inside each kickoff request body. Add the webhooks block below to every kickoff you want Dobby to scan.

import os
import requests

# Same bearer you pasted into Dobby (env var keeps it out of source).
CREWAI_BEARER = os.environ["CREWAI_BEARER"]
CREW_ID = "your-crew-id"  # from your CrewAI Cloud dashboard URL
DOBBY_WEBHOOK_URL = "https://dobby-ai.com/api/v1/webhooks/workloads/wc_xxx"

response = requests.post(
    f"https://app.crewai.com/api/crews/{CREW_ID}/kickoff",
    headers={
        "Authorization": f"Bearer {CREWAI_BEARER}",
        "Content-Type": "application/json",
    },
    json={
        "inputs": {
            # your crew inputs here
        },
        "webhooks": {
            "events": [
                "crew_kickoff_started",
                "crew_kickoff_completed",
                "crew_kickoff_failed",
            ],
            "url": DOBBY_WEBHOOK_URL,
            "realtime": True,
            "authentication": {
                "type": "bearer",
                "token": CREWAI_BEARER,
            },
        },
    },
    timeout=30,
)
response.raise_for_status()
print("Kickoff fired:", response.json())

Replace wc_xxx with the connector ID Dobby gave you in step 2, and your-crew-id with your CrewAI crew ID (visible in the dashboard URL).

Run your kickoff once. CrewAI Cloud will execute the crew and POST crew_kickoff_started / completed / failed events to Dobby in real time.

A typical kickoff completes in 10-60 seconds. Dobby buffers events keyed by execution_id until the terminal event arrives, then writes one workload run + triggers a Policy Scanner pass.

Open Dobby → Workloads. Within ~60 seconds of your test kickoff completing, you should see:

• A new row for the crew with the run status pill
• Last scan verdict (compliant / partial / violated / unverifiable)
• Click through to the scan to see violation details