Freshservice
ReviewAudited by ClawScan on May 16, 2026.
Overview
This is a coherent Freshservice integration that relies on ClawLink for credentials and tool calls; it can make Freshservice changes, but the artifacts require preview and user confirmation for writes.
Install this only if you are comfortable connecting Freshservice through ClawLink. Verify the ClawLink plugin before installing, review the Freshservice scopes you approve, avoid pasting raw credentials into chat, and only confirm write or bulk actions after checking the preview.
Findings (4)
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.
Using the skill requires installing and trusting the ClawLink plugin in addition to this instruction-only skill.
The skill depends on a separate plugin that is not included in the reviewed artifacts. This is disclosed and central to the skill, but users are trusting an external component.
Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
Verify the ClawLink plugin source and publisher before installing it, and install it only if you intend to use ClawLink for Freshservice access.
The plugin will have delegated access to the connected ClawLink/Freshservice account according to the scopes the user approves.
The skill creates delegated ClawLink access and stores a local device credential. The artifact describes this behavior and avoids asking for raw Freshservice credentials.
The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.
Review the Freshservice permissions granted in ClawLink and revoke the connection when it is no longer needed.
If approved, the agent may create or update Freshservice records such as tickets, requesters, assets, changes, or catalog data.
The skill can invoke tools that modify Freshservice data, but it includes an explicit preview-and-confirmation workflow for writes.
For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user. Execute with `clawlink_call_tool`.
Check previews carefully and only confirm write, destructive, external-facing, or bulk actions that match your intent.
Freshservice-related requests and responses may be handled by ClawLink as part of the integration.
Freshservice connection handling and tool access are routed through the ClawLink service. This is disclosed and purpose-aligned, but it is an external gateway for account data.
Powered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials
Review ClawLink's documentation, privacy posture, and connected-account scopes before using it with sensitive Freshservice data.