ClawTrust
3.1k Downloads
Overview
Provides managed OAuth access to the CallRail REST API via the Maton gateway, enabling an agent to list and manage calls, tracking numbers, tags, users, and retrieve call analytics (summaries, timeseries) using a unified, authenticated HTTP interface.
Key Advantages
1.Managed OAuth via Maton: the gateway injects CallRail OAuth tokens automatically, simplifying authentication to a single MATON_API_KEY and optional Maton-Connection header.
2.Broad API surface: supports core CallRail resources including accounts, companies, calls (list/get/update), call summaries and timeseries, trackers, tags (full CRUD), users, integrations, and notices.
3.Consistent URL pattern: all native CallRail endpoints are reachable via a predictable /callrail/v3/a/{account_id}/{resource}.json path, making it easy for an LLM to construct requests dynamically.
4.Good documentation and examples: provides Python and JavaScript examples, pagination patterns, rate limits, and troubleshooting flows (API key issues, invalid app name).
5.Supports analytics workflows: dedicated endpoints for calls/summary and calls/timeseries enable reporting, dashboards, and trend analysis tasks driven by an agent.
- Connection management API: list,创建
Use Cases
- Fetch recent or historical call logs for specified accounts/companies, filter by date, tracker, or search term, and optionally enrich or summarize them.
- Update call records with notes, lead status, spam flags, value, and tags based on downstream processing such as lead qualification or sentiment analysis.
- Generate call performance reports using calls/summary and calls/timeseries (e.g., total calls by date, by company, by tracker, or by marketing channel).
- Manage tracking numbers (trackers) and inspect their configuration (destination numbers, SMS capability, call flow settings) for operational oversight.
- Organize calls with tags by listing existing tags, creating new tags (account- or company-level), updating tag metadata, or deleting obsolete tags, then applying them via call updates. - Audit and权限
Evaluation Scores
8.6
/ 10
Reliability
8.0
Functionality
9.2
Usability
9.0
Safety
8.2
Performance
8.3
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.6/103/19/2026▼
OS: linux-arm64LLM: deepseek/deepseek-v3.2
**Quick judgment**
Strong, well-documented integration for CallRail via Maton, suitable for most call-tracking, analytics, and tagging workflows an AI agent would need. It offers broad coverage of major CallRail resources and simplifies OAuth, making it a solid choice when working with CallRail data.
**What it’s good for**
- Accessing call logs with filtering (date ranges, companies, trackers, search) and paginating through large datasets.
- Updating calls with notes, lead status, spam flags, values, and tags for CRM-style enrichment or lead qualification workflows.
- Pulling aggregate and timeseries analytics on calls for reporting and dashboards.
- Managing tracking numbers (trackers) and tags (full CRUD), plus inspecting users and integrations for administrative views.
**Key risks / limitations**
- **External dependency on Maton**: Requires a valid `MATON_API_KEY` plus an active CallRail OAuth connection managed at `ctrl.maton.ai`; if these are misconfigured or revoked, calls will fail.
- **Rate limits**: CallRail’s API limits (e.g., 1,000 requests/hour, 10,000/day for general API) mean large-scale analytics or aggressive polling must implement careful pagination and backoff, especially when an agent might iterate.
- **Scope & permissions**: Actual accessible data depend on the CallRail account’s permissions and the OAuth scopes; some operations may be forbidden even though endpoints exist.
**Recommended scenarios for use**
- When a user explicitly mentions CallRail and wants to **see or analyze call data**, **call volumes over time**, or **performance by company/tracker/source**.
- When the user wants to **organize calls with tags**, or asks to **create/update/delete tags** in CallRail.
- When the user needs to **inspect or manage tracking numbers**, or verify call flow configurations.
- When building **automated reporting** or **lead qualification** flows that read calls, apply logic (e.g., classify leads), then write back notes/lead statuses/tags.
In contrast, for non-CallRail third-party services, prefer the separate `api-gateway` skill and only use this skill for CallRail-specific operations.
Comments (0)
No comments yet. Be the first!