weclapp_skill

This skill enables seamless Weclapp data access and management through Membrane, simplifying connections, actions, and data retrieval for ERP and CRM workflows.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill weclapp

  • _meta.json267 B
  • SKILL.md9.8 KB

Overview

This skill integrates with Weclapp to manage organizations, customers, products, orders, invoices, tickets, and related ERP/CRM data. It uses the Membrane CLI to handle authentication and run pre-built actions or proxy API requests. The skill exposes listing, retrieval, creation, and custom request capabilities for common Weclapp objects.

How this skill works

The skill talks to Weclapp through Membrane, which manages OAuth, credential refresh, pagination, and error handling. Use Membrane commands to create a connection, list available actions (e.g., list-articles, get-party), run actions with JSON input, or proxy raw API requests when needed. Membrane injects authentication headers and the correct base URL so you only supply action IDs and parameters.

When to use it

  • Sync customer, supplier, or lead records from Weclapp into your app
  • List or paginate products, sales orders, invoices, purchase orders, tasks, or tickets
  • Create new records such as articles, parties, sales orders, or tickets from automation workflows
  • Run custom Weclapp API calls not covered by pre-built actions via the proxy
  • Inspect or debug integration behavior while Membrane handles auth and pagination

Best practices

  • Always create a Membrane connection rather than passing API keys—Membrane handles token refresh and security
  • Discover existing actions with membrane action list --intent=QUERY to avoid reinventing logic
  • Prefer pre-built actions (list-*, get-*, create-*) for pagination and field mapping instead of raw API calls
  • Use membrane request for edge cases or endpoints not exposed by actions, supplying --json, --query, or -X flags as needed
  • Keep input payloads explicit and validate required IDs (e.g., articleId, partyId, salesOrderId) before running actions

Example use cases

  • Bulk-sync product catalog: use list-articles then import into your database with incremental updates
  • Create a sales order from a form submission: run create-sales-order with order JSON input
  • Fetch customer details during support ticket handling with get-party or list-tickets
  • Generate a financial export by listing sales-invoices and downloading related documents via membrane request
  • Implement a webhook consumer that triggers Membrane actions to update Weclapp records automatically

FAQ

No. Membrane manages authentication and token refresh when you connect; you only create a connection and run actions.

How do I call an endpoint not covered by actions?

Use membrane request CONNECTION_ID /path with appropriate flags (-X, --json, --query) to proxy raw API calls through Membrane.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational