Automations
In Beta

Automate by Healthie

Automate runs trigger-based clinical and administrative workflows inside Healthie, so routine follow-ups, task creation, and record updates happen without staff intervention. Describe the automation you want to the AI Builder and it runs every time the trigger fires.

Built by Core Engineering

The problem it solves

Care and operations teams spend hours each week on repetitive follow-through: noticing a no-show, chasing incomplete intake forms, creating a task when a payment fails, or updating a client record after a visit. Without automation, that work depends on someone catching the event, and it scales only by adding staff or accepting that steps get missed.

What's included

  • AI Builder chat inside Healthie that turns a plain-language description into a working automation and asks clarifying questions as it goes
  • Triggers across appointments, forms and chart notes, payments and insurance, and client accounts
  • Configurable steps including conditions, record lookups, and timed delays before acting
  • Actions such as creating tasks, sending chats from a provider, updating client or appointment records, applying tags, sending forms, and adding care team members
  • Automations page with per-automation trigger, run count, last run, and status, plus Edit with AI, Automation details, Recent runs, Copy as JSON, and on/off toggles
  • MCPB Builder for API customers who prefer to build through an AI assistant in Claude Desktop

How it works

  1. An org owner enables Automations permissions (view, create, delete) for each user under Organization > Members > Edit Settings > Permissions.
  2. The user opens Settings (gear) > Automations and clicks Build with AI.
  3. The user describes the automation in plain language. The AI Builder asks follow-up questions until the trigger, any conditions or delays, and the action are defined.
  4. The finished automation appears on the Automations page and is turned on with the toggle.
  5. When the trigger event occurs in Healthie, the automation evaluates its conditions and takes its action. It runs with the permissions of the user who created it.
  6. From the Automations page, users can filter by status, search by name, open Edit with AI to change an automation, view Automation details for the step flow, or open Recent runs to see each run's status and steps completed. Users with developer-tools permission also see options to build manually or import an automation as JSON.

Automate by Healthie is a trigger-based automation engine for clinical and administrative workflows. It is built for care teams that want to act on events like a no-show, a form answer, a failed payment, or a signed chart note without someone watching for them. Each automation pairs a trigger with optional conditions, lookups, or delays and one or more actions, and runs entirely inside Healthie with no third-party tools. Automations are built by describing them in plain language to the AI Builder and managed from the Automations page, where they can be toggled on or off and their runs reviewed.

Building on Healthie?

Talk to our team about API access, white-label, and enterprise architecture — or dive into the docs.