Freshdesk
AdvisoryAudited by Static analysis on May 6, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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.
The agent may be able to update customer-support records or ticket access in Freshdesk when the user asks it to.
The skill can invoke Freshdesk tools that may change tickets, notes, conversations, or watchers. The artifact includes preview and confirmation safeguards, so this is purpose-aligned but still important for users to notice.
For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user. Execute with `clawlink_call_tool`.
Review tool previews carefully and only confirm Freshdesk writes, bulk actions, or external-facing updates when the proposed change is correct.
Connecting Freshdesk may allow ClawLink-mediated tools to act with the permissions granted by the user’s Freshdesk account or workspace.
The skill delegates Freshdesk authorization to ClawLink. This is expected for the integration and is disclosed, but it gives the connected tools whatever Freshdesk permissions the user approves.
ClawLink ... handles hosted connection flows and credentials so you don't need to configure Freshdesk API access yourself.
Connect only the intended Freshdesk account, grant the minimum practical permissions, and revoke the connection in ClawLink or Freshdesk if no longer needed.
The actual Freshdesk tool implementation comes from the ClawLink plugin and hosted service, not from code reviewed in this skill package.
The instruction-only skill depends on an external plugin that is not included in the provided artifact set. The install step is user-directed and purpose-aligned, but users are relying on that plugin’s provenance and behavior.
Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
Install the plugin only from the expected ClawHub source and verify ClawLink’s documentation or verification page before pairing accounts.
Freshdesk ticket information and account actions may be mediated by ClawLink rather than going directly from OpenClaw to Freshdesk.
The skill routes authentication and tool calls through the ClawLink gateway. The destination is disclosed, but Freshdesk-related requests and responses may pass through that service.
The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`.
Use this only if you are comfortable with ClawLink handling the integration flow and related support data, and avoid sending unnecessary sensitive ticket content.