Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Diagnoses and auto-heals BlueBubbles ↔ OpenClaw iMessage connectivity. Use when: iMessages stop arriving after a gateway restart, webhook connection is broke...
Diagnoses and auto-heals BlueBubbles ↔ OpenClaw iMessage connectivity. Use when: iMessages stop arriving after a gateway restart, webhook connection is broke...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill when: iMessages aren't being delivered to/from OpenClaw After restarting the OpenClaw gateway User reports "messages not coming through" Periodic healthcheck (can be added to HEARTBEAT.md) Debugging BlueBubbles ↔ OpenClaw connectivity
Diagnoses and auto-heals the webhook connection between BlueBubbles and OpenClaw. This is a common failure mode: after gateway restarts, BlueBubbles can lose its webhook or enter backoff state. Diagnostic checks: BlueBubbles server reachable Webhook registered pointing to OpenClaw OpenClaw gateway endpoint responding Recent webhook delivery activity Auto-healing: Restarts OpenClaw gateway if endpoint is down Deletes stale webhooks and re-registers fresh Verifies fix after healing
BB_URL="http://127.0.0.1:1234" \ BB_PASSWORD="your-password" \ ~/.openclaw/workspace/skills/bluebubbles-healthcheck/scripts/diagnose.sh Interpret the output: All ✅ = healthy, no action needed Any ❌ = issue detected, consider running heal
BB_URL="http://127.0.0.1:1234" \ BB_PASSWORD="your-password" \ ~/.openclaw/workspace/skills/bluebubbles-healthcheck/scripts/heal.sh This will: Run diagnostics Identify what's broken Attempt to fix it (gateway restart, webhook reset) Re-run diagnostics to verify
BB_URL="http://127.0.0.1:1234" \ BB_PASSWORD="your-password" \ ~/.openclaw/workspace/skills/bluebubbles-healthcheck/scripts/heal.sh --dry-run
VariableRequiredDefaultDescriptionBB_URLYeshttp://127.0.0.1:1234BlueBubbles server URLBB_PASSWORDYes—BlueBubbles API passwordOPENCLAW_WEBHOOK_URLNohttp://127.0.0.1:18789/bluebubbles-webhookOpenClaw webhook endpoint You can also pass these as args: --bb-url, --password, --webhook-url
User reports iMessage issue ↓ Run diagnose.sh ↓ ┌────┴────┐ │ All ✅? │ └────┬────┘ Yes │ No ↓ │ ↓ Report │ Run heal.sh healthy │ ↓ │ ┌───┴───┐ │ │Fixed? │ │ └───┬───┘ │ Yes │ No │ ↓ │ ↓ │Report│ Escalate to user: │fixed │ - BB app not running? │ │ - Network issue? └──────┴─ Manual intervention needed
Symptoms: Messages stop after openclaw gateway restart Fix: heal.sh will reset webhook
Symptoms: Webhook exists but BB stopped trying to deliver Fix: heal.sh deletes and re-registers webhook (clears backoff state)
Symptoms: Check 3 fails (port 18789 not listening) Fix: heal.sh runs openclaw gateway restart
Symptoms: Check 1 fails (HTTP 000) Fix: Manual — user must start BlueBubbles.app on the Mac
skills/bluebubbles-healthcheck/ ├── SKILL.md ← You are here ├── README.md ← GitHub docs └── scripts/ ├── diagnose.sh ← Read-only diagnostics (exit 0 = healthy) ├── heal.sh ← Auto-heal orchestrator └── reset-webhook.sh ← Atomic webhook delete+re-register
reset-webhook.sh registers a webhook URL like: http://127.0.0.1:18789/bluebubbles-webhook?password=... This is a BlueBubbles → OpenClaw authentication constraint, not arbitrary exposure. When BlueBubbles fires webhook events, it calls this URL. OpenClaw's BB plugin uses ?password= to verify the incoming callback is from a trusted source. There is no other mechanism in the current BB↔OpenClaw integration for authenticating inbound webhook calls. Mitigations already in place: Both services run on 127.0.0.1 (localhost only — never exposed externally) The password is masked in all log output by the script The URL is only stored inside BlueBubbles' local config (not transmitted off-device) What you should know before installing: BB_PASSWORD will be stored inside BlueBubbles' webhook config on disk Only use on machines where both BB and OpenClaw run locally and are trusted Do not point BB_URL at a remote BlueBubbles instance
BinaryUsed byNotescurlAll scriptsHTTP calls to BB APIpython3diagnose.sh, reset-webhook.shJSON parsingncdiagnose.sh, heal.shPort check on 18789openclawheal.shGateway restart (gracefully skipped if not found) All of these are standard on macOS except openclaw — this skill is part of the OpenClaw ecosystem and expects the openclaw CLI to be available.
To run periodic healthchecks, add to HEARTBEAT.md: ## BlueBubbles Health Every 4 hours, run the BlueBubbles healthcheck skill. If any checks fail, run heal and report results.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.