with one click
apaas-oapi-node-client
apaas-oapi-node-client contains 8 collected skills from ennann, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use for aPaaS Node SDK attachment and avatar operations: uploading, downloading, and deleting files with client.attachment.file.*, uploading and downloading avatar images with client.attachment.avatar.*, and safely handling binary payloads and record attachment fields.
Use for aPaaS Node SDK Feishu/Lark identity exchange: converting user or department IDs between aPaaS/Lark internal IDs, external IDs, and external open IDs with client.department.* and client.user.*, including batch exchange, retry results, and feishu_app_id handling.
Use for aPaaS Node SDK object schema management with client.object.schema.*: creating objects, updating object labels/settings, adding/replacing/removing fields, deleting objects, field type mapping, lookup/reference field dependencies, SQL/ER conversion, staged creation, and schema change safety checks. client.schema.* remains a compatibility alias.
Use for aPaaS Node SDK shared setup and safety rules: client initialization, credentials, namespace, token cache, logger level, OpenAPI coverage, pagination defaults, retry expectations, write/delete confirmation, and error-code triage before using module-specific apaas skills.
Use for aPaaS Node SDK cloud function, automation flow, workflow, user task, and Lark integration token operations: invoking functions, executing v1/v2 flows, querying execution status, task approve/reject/transfer/rollback/chat, checking code/msg/data, and avoiding unsafe repeated workflow submissions.
Use for aPaaS Node SDK object/data operations: object metadata, fields, Markdown export, record CRUD, batch operations, OQL, cross-object search, constant objects, datasets, pagination, ID cursor pagination, and record-level error recovery.
Use for aPaaS Node SDK builder page operations: listing pages, paginating page metadata, reading page details, generating page access URLs with pageParams, parentPageParams, navId, or tabId, and verifying page IDs from live metadata.
Use for aPaaS Node SDK global data operations: reading global option details, listing global options, reading global variable details, listing global variables, paginating results, and resolving API names from live metadata.