Helpwise
ReviewAudited by ClawScan on May 10, 2026.
Overview
This Helpwise integration is mostly coherent, but it should be reviewed because it can use an authenticated Membrane connection to run destructive, customer-facing, or raw Helpwise API actions without clear confirmation limits.
Install only if you intend to let the agent work with Helpwise through Membrane. Before using it, verify the Membrane CLI package, connect a least-privileged Helpwise account, and require explicit confirmation before any reply, deletion, contact creation, assignment, or raw API request.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used carelessly, the agent could delete Helpwise conversations, send replies, create or modify records, or call arbitrary Helpwise API endpoints through the authenticated connection.
The skill documents authenticated mutation and deletion actions plus a raw API proxy with multiple HTTP methods, but it does not define confirmation, scoping, or rollback expectations for destructive or customer-facing operations.
Delete Conversation | delete-conversation | Permanently delete a conversation ... membrane request CONNECTION_ID /path/to/endpoint ... HTTP method (GET, POST, PUT, PATCH, DELETE)
Require explicit user approval before replies, deletes, assignments, contact creation, or raw API calls; prefer listed Membrane actions over proxy requests and use the least-privileged Helpwise connection available.
The connected account's Helpwise permissions determine what the agent can read or change.
The skill requires delegated Membrane and Helpwise authentication. This is expected for the integration, but it gives the agent access to actions available through the connected account.
Membrane handles authentication and credentials refresh automatically ... membrane login --tenant ... The user completes authentication in the browser.
Connect only accounts with permissions appropriate for the intended tasks and revoke the connection when it is no longer needed.
Installing the CLI runs third-party package code on the local machine with the user's privileges.
The setup instructs installation of a global npm CLI package without a pinned version. This is purpose-aligned for a Membrane integration, but it relies on npm package provenance and the current published package contents.
npm install -g @membranehq/cli
Verify the package publisher and repository, consider pinning a known-good version, and install only in an environment where running the CLI is acceptable.