Enerflo integration. Manage Organizations. Use when the user wants to interact with Enerflo data.
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/
Use action names and parameters as needed.
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 Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search enerflo --elementType=connector --json
output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
When you are not sure if connection already exists:
membrane connection list --json
connectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| 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 |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the Enerflo API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.ZIP package — ready to use