Install
openclaw skills install weclappWeclapp integration. Manage Organizations. Use when the user wants to interact with Weclapp data.
openclaw skills install weclappWeclapp is a cloud-based ERP and CRM software designed for small and medium-sized businesses. It helps companies manage sales, marketing, service, and finance operations in one integrated platform. Weclapp is used by businesses looking to streamline their processes and improve efficiency.
Official docs: https://developers.weclapp.com/
Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Weclapp. 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@latest
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:
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
Use connection connect to create a new connection:
membrane connect --connectorKey weclapp
The user completes authentication in the browser. The output contains the new connection id.
membrane connection list --json
Search using a natural language description of what you want to do:
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).
| Name | Key | Description |
|---|---|---|
| List Articles | list-articles | List articles (products) with optional filtering and pagination |
| List Parties | list-parties | List parties (customers, suppliers, leads) with optional filtering and pagination |
| List Sales Orders | list-sales-orders | List sales orders with optional filtering and pagination |
| List Sales Invoices | list-sales-invoices | List sales invoices with optional filtering and pagination |
| List Purchase Orders | list-purchase-orders | List all purchase orders with optional filtering and pagination |
| List Users | list-users | List users with optional filtering and pagination |
| List Tasks | list-tasks | List tasks with optional filtering and pagination |
| List Tickets | list-tickets | List support tickets with optional filtering and pagination |
| List Opportunities | list-opportunities | List all sales opportunities with optional filtering and pagination |
| Get Article | get-article | Get an article by ID |
| Get Party | get-party | Get a party by ID |
| Get Sales Order | get-sales-order | Get a sales order by ID |
| Get Sales Invoice | get-sales-invoice | Get a sales invoice by ID |
| Get Purchase Order | get-purchase-order | Get a purchase order by ID |
| Get User | get-user | Get a user by ID |
| Get Task | get-task | Get a task by ID |
| Get Ticket | get-ticket | Get a ticket by ID |
| Create Article | create-article | Create a new article (product) |
| Create Party | create-party | Create a new party (customer, supplier, or lead) |
| Create Sales Order | create-sales-order | Create a new sales order |
If no suitable action exists, describe what you want — Membrane will build it automatically:
membrane action create "DESCRIPTION" --connectionId=CONNECTION_ID --json
The action starts in BUILDING state. Poll until it's ready:
membrane action 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.
READY — action is fully built. Proceed to running it.CONFIGURATION_ERROR or SETUP_FAILED — something went wrong. Check the error field for details.membrane action run <actionId> --connectionId=CONNECTION_ID --json
To pass JSON parameters:
membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json
The result is in the output field of the response.
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.