Skip to main content

Installation

Install the Arlo Health plugin with a single command:

Requirements

  • Node.js 18 or higher
  • OpenClaw CLI v2.0+

What It Does

The arlo-health plugin gives your OpenClaw agent everything it needs to act in healthcare for its user. Once installed, your agent can:
  • Start conversations — Gather symptoms and connect users with healthcare providers
  • Handle triage — AI-powered symptom assessment before provider connection
  • Track prescriptions — View prescription orders and their fulfillment status
  • Send messages — Async communication with providers during active visits

How It Works

The plugin wraps Arlo’s REST API into an OpenClaw-compatible interface. Under the hood, it uses the same endpoints documented in our API Reference.
1

Install the plugin

Run openclaw plugins install arlo-health
2

User authenticates

When a user needs healthcare, the plugin initiates OAuth signup
3

Start a consultation

Your agent gathers symptoms and starts a consultation
4

Provider connects

A licensed clinician reviews and responds

Available Tools

Once installed, these tools are available to your OpenClaw agent:

Authentication

Conversations

Messaging

Profile & Onboarding

Prescriptions

Pharmacy selection is not an agent tool: US prescriptions are fulfilled by Photon Health, which texts the patient to pick a pharmacy and track the order. (Legacy Canadian orders are managed in the Arlo patient portal.)

Billing

Webhooks

Tool names are prefixed with arlo_ to avoid conflicts with other plugins.

Configuration

Authentication is handled per-user through OAuth 2.1 with PKCE.

Webhook Setup (Required for Notifications)

Critical: After a user authenticates, you must explicitly call register_webhook with deliveryContext and conversationSessionKey. These fields are not auto-populated from openclaw.json — without them, notifications will not be routed to the user’s conversation.
For real-time notifications when providers respond, configure webhooks with all required fields:

Notification Handling

When Arlo fires a webhook, OpenClaw wakes the agent session and delivers the notification as a system message. The agent is then responsible for deciding what to do.
Simply replying to the session is not enough — heartbeat-triggered replies don’t auto-deliver to the user’s channel. The agent must proactively push using its channel messaging tool (e.g. message action=send for WhatsApp/Telegram, a channel post for Discord, etc.).
The simplest and most reliable approach is OpenClaw’s built-in /hooks/wake endpoint. Register it as your webhook URL — no custom server needed.
When Arlo fires, OpenClaw wakes the agent with the notification text as a system message. The agent runs, fetches the consultation, and decides how to respond.

Agent Prompting (Required)

hooks/wake requires your agent to know what to do on receipt. Add this to your HEARTBEAT.md, system prompt, or equivalent agent instructions:
The arlo_register_webhook tool description already includes this guidance inline — any agent using the tool at runtime will see it. The prompting above reinforces it at the environment level for more consistent behavior.

Alternative: Custom Endpoint

If you need custom processing (filtering, multi-channel fan-out, logging), run your own webhook server and register that URL instead. The plugin makes no assumptions about delivery — it calls whatever URL you register. See the Webhooks tool reference for payload details.

Correct Post-Connect Flow

After a user successfully authenticates, always register webhooks explicitly:
The hasDeliveryContext: true response only indicates an object exists — it does not confirm that to or channel are set. Always pass these explicitly.

View on npm

arlo-health

View package on npm for version history and changelog

Next Steps

Quickstart

Step-by-step guide to your first consultation

Webhooks

Configure real-time notifications

Consultation Lifecycle

Understand the consultation flow

API Reference

Full REST API documentation