Automate by Healthie: Set-Up Guide (MCPB Builder for API Customers)

Automate is Healthie's trigger-based automation engine for clinical and administrative workflows. It lets you define a trigger (an event that happens in Healthie) and pair it with an action that fires automatically, without manual staff intervention. 

There are two ways to build automations:

What is the MCPB Builder?

The MCPB Builder is an AI-powered tool that lets you describe an automation in plain language, then builds and tests it in your staging environment. You review it there, then import it to production through your browser.

It is distributed as an MCP Bundle (.mcpb   ), an installable extension file that connects Claude Desktop to your Healthie account. Opening the file installs it in one click. Because MCPB is an open format, it also installs in other desktop AI apps that support it, including Claude Code.

Before you Start (Prerequisites)

• These instructions assume the Claude Desktop app. It works on the free plan and up, though a paid plan is recommended.
  • For customers using the Enterprise version of Claude, the extension will need t to be added to your "orgs allow" list. Once it's added to said list, users have to download the package from the 'Discover' view of Claude Connectors.
• Automate Builder is distributed as an MCP Bundle (.mcpb), so it also installs in any other AI desktop app that supports the format, including Claude Code.
• You will need a staging API key.
• If you use a white-labeled Healthie front end, or your organization is on a dedicated shard, see step 4b before you begin. You will need two values from your Healthie contact.

Step-by-Step Instructions for MCPB Installation

Step 1. Turn on Automate for your user account(s)

Confirm the automations permissions are enabled within your production account. An org owner, or anyone who can edit member settings, can do this.

1. Click your avatar in the upper right, then go to Organization > Members.
2. Find the user, click the three dots next to them, and choose Edit Settings.
3. Open the Permissions tab and scroll to Automations.
4. Enable view, create, and delete automations.

Step 2. Download the installer

Download the Automate Builder installer: Link Here

Step 3. Install into Claude Desktop

Open the downloaded file. It installs in one click.

If nothing happens when you open it, make sure Claude Desktop is installed and up to date, then try Settings > Extensions > Advanced settings > Install Extension and select the file.

Step 4. Connect Automate Builder to your Healthie account

Ask Automate Builder to initiate. It will prompt you for your connection details.

4a. Staging API key (required)

Automate Builder needs a staging API key. Automations are built and tested in staging, then imported into production through your browser session, so no production key is required.

Generate a staging key at Settings > API Keys (https://securestaging.gethealthie.com/settings/api_keys) and paste it in when prompted.

4b. Advanced settings (only if this applies to you)

Skip this section unless you use a whitelabeled Healthie front end or your organization is on a dedicated shard. If you are not sure, ask your Healthie contact before entering anything here.

White-labeled front-end URL

If your team signs into Healthie at your own domain rather than secure.gethealthie.com, enter that URL.

Automate Builder uses it to build the links it hands you at the end, so "view your automation" and the production import link open in your environment. Leaving it blank does not break the build. You will get default-domain links that you have to swap by hand.

Authorization Shard header

If your organization is on a dedicated shard, enter your shard ID.

• It is a UUID, for example 0196266f-0c59-792c-ad8e-b55b030b50b5.
• It is not your organization's name. A value like myorg is invalid.
• Staging and production have different values. Use the one for the environment you are connecting to.
• Get it from your Healthie contact. If your organization is a sub-organization under a parent org, get it from the parent.

Important: if this value is wrong or malformed, it is treated as though the header were never sent. Your requests route to the default database and you will not see an error about the header itself. Instead you will see an authentication failure, "user not found," or empty results that look like a permissions problem. If verification in step 5 fails and you are on a shard, check this value first.

Step 5. Let Automate Builder verify the connection

Automate Builder confirms it can reach your account before doing anything else.

Step 6. Describe the automation you want

Ask for the automation in plain language. Automate Builder walks through every step needed to create it.

Not sure what to ask for?

Browse the Product Catalog for examples of what Automate can do. Filter or group by Type and look at the Automation items. Each one lists the problem it solves along with its trigger, logic, and action, which maps directly to how you would phrase the request here.

Step 7. Review the automation in staging

When it finishes, Automate Builder links you to the automation in staging. Review it there before going further.

Step 8. Import to production

Ask for a production import link. Make sure you are already signed into production first. If you have not done so already, you will need to give yourself Automate permission within your production account (see Step 1) 

Because the import runs in your browser session, Automate Builder does not need production credentials or your production shard ID. It just needs to send you to the right URL, which is why the whitelabel URL in step 4b matters if you use one.

Step 9. Reconfigure and enable

Import the automation, re-configure any variables for production, then enable it.

Your successfully created automation will now be visible within your account.

FAQs for MCPB Builder

Do I need a production API key to use Automate Builder?

No. Automations are built and tested in staging. The import to production happens through your browser session, so no production API key is needed.

Will Automate Builder make changes to my production environment?

Not automatically. You review the automation in staging first, then manually import it to production and enable it yourself.

I am on a dedicated shard and verification keeps failing. What should I check?

Confirm the AuthorizationShard value with your Healthie contact. It must be the UUID for your staging environment specifically, not your organization name, and not your production shard ID. See Step 4b for details.