calltrackingmetrics_skill

This skill helps you manage CallTrackingMetrics data by interacting with accounts, campaigns, contacts, and calls via the Membrane CLI.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill calltrackingmetrics

  • _meta.json291 B
  • SKILL.md6.1 KB

Overview

This skill provides an integration with CallTrackingMetrics to manage accounts, tracking numbers, contacts, calls, campaigns, and reports. It uses the Membrane CLI as the transport layer so authentication, token refresh, and request plumbing are handled for you. Use it to automate call-tracking workflows, query activity, and manage account resources from scripts or automation pipelines.

How this skill works

The skill exposes CallTrackingMetrics functionality via Membrane actions and a proxy request surface. Discover available actions with membrane action list, create or reuse a connection via membrane connect, then run actions with membrane action run passing JSON inputs. For unsupported endpoints, use membrane request to call the API directly while Membrane injects auth headers and handles refresh.

When to use it

  • Automating purchase, routing, or assignment of tracking numbers across campaigns.
  • Syncing contacts, calls, and form submissions into a CRM or analytics pipeline.
  • Running account-level audits: list accounts, billing orders, integrations, and users.
  • Sending SMS messages or managing inbound/outbound call details programmatically.
  • Querying reports and call logs for date-filtered analytics or attribution tasks.

Best practices

  • Prefer Membrane pre-built actions to reduce token usage and handle pagination automatically.
  • Always create a connection via membrane connect — never ask users for API keys or tokens.
  • Discover actions with membrane action list before building custom requests to reuse existing behavior.
  • Use membrane request for one-off or new API endpoints; rely on Membrane for auth and header management.
  • Test actions in a non-production account first when modifying routing, purchasing numbers, or deleting contacts.

Example use cases

  • Batch purchase and assign tracking numbers to a new marketing campaign across multiple regions.
  • Daily job to list calls and push new leads into a CRM with enriched contact updates.
  • Automated cleanup: find and delete duplicate contacts across a sub-account.
  • Send appointment reminders via send-sms from a tracking number using a scheduled action.
  • Proxy a custom reporting endpoint to retrieve date-filtered call metrics not covered by built-in actions.

FAQ

No — Membrane handles authentication. Create a connection with membrane connect and complete browser-based auth; you never store API keys locally.

Can I call any CallTrackingMetrics endpoint?

Yes. Use pre-built actions where available and membrane request to proxy arbitrary endpoints; Membrane will append the base URL and inject auth headers.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational