Lessaccounting
by @gora050
LessAccounting integration. Manage Organizations. Use when the user wants to interact with LessAccounting data.
clawhub install lessaccountingπ About This Skill
name: lessaccounting description: | LessAccounting integration. Manage Organizations. Use when the user wants to interact with LessAccounting data. compatibility: Requires network access and a valid Membrane account (Free tier supported). license: MIT metadata: author: membrane version: "1.0" categories: ""
LessAccounting
LessAccounting is a simple accounting software designed for small business owners and freelancers. It helps users track income, expenses, and generate basic financial reports. The target audience is non-accountants who need an easy way to manage their finances.
Official docs: https://help.lessaccounting.com/
LessAccounting Overview
Working with LessAccounting
This skill uses the Membrane CLI (npx @membranehq/cli@latest) to interact with LessAccounting. Membrane handles authentication and credentials refresh automatically β so you can focus on the integration logic rather than auth plumbing.
First-time setup
npx @membranehq/cli@latest login --tenant
A browser window opens for authentication. After login, credentials are stored in ~/.membrane/credentials.json and reused for all future commands.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with npx @membranehq/cli@latest login complete .
Connecting to LessAccounting
1. Create a new connection:
npx @membranehq/cli@latest search lessaccounting --elementType=connector --json
Take the connector ID from output.items[0].element?.id, then:
npx @membranehq/cli@latest connect --connectorId=CONNECTOR_ID --json
The user completes authentication in the browser. The output contains the new connection id.Getting list of existing connections
When you are not sure if connection already exists: 1. Check existing connections: npx @membranehq/cli@latest connection list --json
If a LessAccounting connection exists, note its connectionIdSearching for actions
When you know what you want to do but not the exact action ID:
npx @membranehq/cli@latest 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.Popular actions
Use npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json to discover available actions.
Running actions
npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
npx @membranehq/cli@latest action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
Proxy requests
When the available actions don't cover your use case, you can send requests directly to the LessAccounting 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.
npx @membranehq/cli@latest 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" |
You can also pass a full URL instead of a relative path β Membrane will use it as-is.
Best practices
npx @membranehq/cli@latest 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.π Tips & Best Practices
npx @membranehq/cli@latest 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.