callrail@1.2.7

Publisher claims: "CallRail API integration with managed OAuth. Track and analyze phone calls, manage tracking numbers, companies, and tags. Use this skill when users want to access call data, manage tracking numbers, view call analytics, or organize calls with tags. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a CallRail connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a CallRail action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with CallRail examples; they add no CallRail capability - CallRail is not an event source, a trigger cannot read CallRail data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.