n8n-nodes-callcast

Official n8n community node for CallCast. Verified against
n8n-workflow@2.16.0 (tsc --noEmit and eslint-plugin-n8n-nodes-base's community
ruleset both pass clean against the files in this package).

Credential

CallCast API (credentials/CallCastApi.credentials.ts) — a single API key, sent as
X-API-Key on every request. Create the key in the CallCast dashboard under
Settings → API Keys, scoped to whichever operations below you plan to use.

The credential has a "Test" button (GET /api/v1/auth/probe, added 2026-07-14) — it
accepts any active, non-expired key for any org regardless of scope, so it only
proves "this is a valid CallCast API key." A green test does not guarantee a
particular scope; Start a Call / List Campaigns / Get Call each still
enforce their own scope and return a clear 403 if the key lacks it.

Node: CallCast

Three operations, each gated on its own API-key scope:

campaigns.read / calls.read are read-only: list/retrieve only, no create/update/
delete — a key holding either scope gets 403 on any write attempt against those
endpoints, even from outside this node.

History — the 401 this section used to warn about is fixed

Until 2026-07-14, CampaignViewSet and CallViewSet used Django REST Framework's
project-wide default authentication classes (JWT + session — voiceai/settings.py),
which don't recognize an API key at all, so a request that only carried X-API-Key
hit those two views as an anonymous user and got a 401 — regardless of what scope the
key had. Both viewsets now also accept APIKeyAuthentication, gated on the
campaigns.read / calls.read scopes above (list/retrieve only). See
docs/integrations/directory-apps-setup.md §0 for the full write-up.

Build & test locally

cd integrations-apps/n8n
npm install
npm run build
npm link
cd ~/.n8n/custom   # or wherever N8N_CUSTOM_EXTENSIONS points
npm link n8n-nodes-callcast

Full publish runbook (npm publish + community-node verification + n8n Cloud listing)
is in docs/integrations/directory-apps-setup.md.

Full control via MCP

This node covers the common no-code cases. For anything else — agent config,
knowledge base, contact lists, DNC management, call transcripts/QA, analytics — connect
an AI assistant (Claude, etc.) directly to CallCast's MCP server, which exposes the
full read/write surface. See mcp_server/README.md (if present) or
https://docs.callcast.ai/mcp for connection details.