CallRail
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is a coherent CallRail integration, but it uses a Maton API key/OAuth connection and can read or change CallRail account data, so users should review permissions carefully.
Before installing, confirm that you trust Maton to proxy CallRail requests, use the correct CallRail connection ID when multiple accounts exist, and require clear confirmation before any create, update, or delete action.
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.
Anyone or any agent action using this key may be able to access the connected CallRail account within the granted permissions.
The skill requires a bearer API key that authorizes access to a managed CallRail OAuth connection.
All requests require the Maton API key in the Authorization header: Authorization: Bearer $MATON_API_KEY
Store the Maton API key securely, connect only the intended CallRail account, and revoke the key or OAuth connection when it is no longer needed.
If approved incorrectly, the agent could change or delete CallRail resources such as connections, companies, trackers, or tags.
The skill supports write/delete actions against CallRail resources, but it documents an approval requirement before those actions.
All write operations require explicit user approval. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
Review every proposed write or delete action, confirm the account/resource ID, and avoid approving broad or unclear changes.
CallRail request and response data may pass through Maton, including potentially sensitive call/account information.
CallRail API traffic and OAuth token handling are routed through the Maton service rather than directly to CallRail.
Maton proxies requests to `api.callrail.com` and automatically injects your OAuth token.
Install only if you trust Maton as the OAuth/API proxy and are comfortable routing CallRail data through that service.
