enerflo

What this skill does

# Enerflo

Enerflo is a solar sales and project management platform. It's used by solar installation companies to manage leads, create proposals, and track projects from sale to installation.

Official docs: https://docs.enerflo.com/

## Enerflo Overview

- **Project**
  - **Customer**
  - **Proposal**
  - **Task**
- **User**
- **Product**
- **Document**
- **Note**
- **Attachment**
- **Order**
- **Form**
- **Email**
- **Installer**
- **Integration**
- **Price Plan**
- **Milestone**
- **Payment**
- **Rejection Reason**
- **Credit Report**
- **Credit Application**
- **Message**
- **Location**
- **Company**
- **Template**
- **Commission Rate**
- **Rebate Program**
- **Subscription**
- **Change Order**
- **System Size**
- **Tax Rate**
- **Inverter**
- **Panel**
- **Utility Company**
- **Loan Product**
- **Vendor**
- **Lead Source**
- **Cost Item**
- **Expense**
- **Permission**
- **Role**
- **Address**
- **Contact**
- **Material**
- **Labor**
- **Equipment**
- **Other Cost**
- **Task Template**
- **Notification**
- **Proposal Template**
- **Document Template**
- **Signature Request**
- **Workflow**
- **Workflow Task**
- **Report**
- **Dashboard**
- **Filter**
- **View**
- **Tag**
- **Territory**
- **Installer Profile**
- **Installer Availability**
- **Installer Skill**
- **Installer Certification**
- **Installer Review**
- **Installer Service Area**
- **Installer Team**
- **Installer Team Member**
- **Installer Tool**
- **Installer Vehicle**
- **Installer Insurance**
- **Installer License**
- **Installer Background Check**
- **Installer Safety Record**
- **Installer Project**
- **Installer Task**
- **Installer Material**
- **Installer Labor**
- **Installer Equipment**
- **Installer Other Cost**
- **Installer Note**
- **Installer Attachment**
- **Installer Message**
- **Installer Location**
- **Installer Company**
- **Installer Contact**
- **Installer Address**
- **Installer User**
- **Installer Permission**
- **Installer Role**
- **Installer Notification**
- **Installer Report**
- **Installer Dashboard**
- **Installer Filter**
- **Installer View**
- **Installer Tag**
- **Installer Territory**
- **Installer Commission Rate**
- **Installer Rebate Program**
- **Installer Subscription**
- **Installer Change Order**
- **Installer System Size**
- **Installer Tax Rate**
- **Installer Inverter**
- **Installer Panel**
- **Installer Utility Company**
- **Installer Loan Product**
- **Installer Vendor**
- **Installer Lead Source**
- **Installer Cost Item**
- **Installer Expense**
- **Installer Task Template**
- **Installer Proposal Template**
- **Installer Document Template**
- **Installer Signature Request**
- **Installer Workflow**
- **Installer Workflow Task**

Use action names and parameters as needed.

## Working with Enerflo

This skill uses the Membrane CLI to interact with Enerflo. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Enerflo

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://enerflo.com/" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
- **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  - `clientAction.type` — the kind of action needed:
    - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
    - `"provide-input"` — more information is needed (e.g. which app to connect to).
  - `clientAction.description` — human-readable explanation of what's needed.
  - `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
  - `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

  After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

- **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

### Searching for actions

Search using a natural language description of what you want to do:

```bash
membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json
```

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

## Popular actions

| Name | Key | Description |
|---|---|---|
| List Customers | list-customers | Retrieve a paginated list of all customers in Enerflo |
| List Deals | list-deals | Retrieve a list of all deals/surveys in Enerflo |
| List Installs | list-installs | Retrieve a list of all installation projects |
| List Tasks | list-tasks | Retrieve a list of tasks for the company |
| List Appointments | list-appointments | Retrieve all appointments for a customer |
| List Users | list-users | Retrieve a list of all users in the company |
| Get Customer | get-customer | Retrieve details of a specific customer by their Enerflo Customer ID |
| Get Deal | get-deal | Retrieve details of a specific deal/survey by ID |
| Get Install | get-install | Retrieve details of a specific installation project including company details, customer info, milestones, and files |
| Get User | get-user | Retrieve details of a specific user by ID |
| Get Company | get-company | Retrieve details about your company |
| Create Customer Note | create-customer-note | Create a new note associated with a customer |
| Create Appointment | create-appointment | Create a new appointment for a customer |
| Create Task | create-task | Create a new task associated with a customer |
| Add Lead | add-lead | Add a new customer/lead to Enerflo via the Lead Gen API |
| Update Customer | update-customer | Update the details of an existing customer |
| Update Task | update-task | Update an existing task |
| Update Install Status | update-install-status | Update the status and details of an installation project |
| List Products | list-products | Retrieve all available products |
| List Customer Notes | list-customer-notes | Retrieve all notes associated with a customer |

### Running actions

```bash
membrane action run <actionId> --