Zapier, Make, n8n & viaSocket

Guide: Zapier, Make, n8n & viaSocket

Looking to connect WhatsApp, a CRM, Google Sheets, Razorpay, a calendar, or a form? Those have built-in connectors — you don't need an automation platform. Connect the vendor once under Workplace → Integrations and add it to any agent as a one-click tool. See Integrations & connectors. This page is for automation platforms specifically (Zapier / Make / n8n / viaSocket) and the REST-hook API that drives them.

Automation platforms let you wire Telenow into workflows in two directions:

1. They react to Telenow — a call ends, analysis lands, a recording is ready → a Zap / scenario / workflow runs (CRM update, Slack alert, spreadsheet row).
2. Your agent calls them mid-conversation — the agent invokes a workflow as a tool and can speak the result back to the caller. (For a fixed third-party action — send WhatsApp, create a lead, append a sheet — a built-in connector is simpler and faster than a workflow.)

Both directions authenticate with an API key from Developers → API Keys.

Three ways to extend an agent — pick the simplest that fits: a built-in connector (connect once, one-click tool — best for WhatsApp/CRM/Sheets/payments/forms/calendars), an MCP server or aggregator (a whole API surface — including Zapier/Make/n8n via their own MCP), or an automation-platform workflow behind a webhook (this guide — best for fan-out side-effects and multi-step recipes).

What you can build

When something happens on a call, your workflow runs (triggers):

• Call Analyzed — the strongest trigger: the AI's post-call summary, sentiment, disposition and action items flow straight into your CRM. A "hot lead" disposition can create a deal or ping a salesperson instantly.
• Call Ended — log every call with its transcript and recording link to HubSpot, Salesforce, Google Sheets, or a Slack channel.
• Call Started — live notifications the moment a conversation begins.
• Recording Ready — auto-archive recordings to Drive/S3 for compliance.
• Tool Invoked — an audit trail of what the agent did mid-call.

Every trigger can fire org-wide or be scoped to a single agent.

Your workflow makes things happen in Telenow (actions):

• Place an AI Agent Call — a lead fills a website form and the agent calls them back within a minute, greeting them by name via context variables. Works from any trigger: abandoned cart, failed payment, appointment reminder, renewal due.
• Get Call / Find Calls — pull transcripts and call details into reports, QA queues, or a daily digest.

Your agent reaches into your tools during a live call (agent tools):

• Caller asks "where's my order?" → the agent calls your workflow → the workflow queries your store → the agent speaks the answer seconds later.
• Book an appointment mid-call (workflow → calendar → spoken confirmation). (For a plain Google Calendar or Calendly booking, the built-in connector needs no workflow.)
• Add the workflow as an HTTP or MCP tool in the agent builder's Tools step. (For the platforms' own MCP servers, paste the MCP URL under Tools → Connect MCP server — see Integrations.)

Recipes our customers start with

End-to-end, zero code: form lead → AI calls in 60 seconds → call analyzed → CRM updated → WhatsApp follow-up sent.

The integration API (/api/v1)

A flat, key-authed surface built for automation platforms. The organization always comes from the key — no org ID to pass. Send the key as X-API-Key.

Placing calls stays on the existing endpoint: POST /api/sessions/initiate-call (it accepts the same API key).

Subscribing to events (REST hooks)

curl -X POST https://api.telenow.ai/api/v1/hooks \
  -H "X-API-Key: vai_live_…" -H "Content-Type: application/json" \
  -d '{
    "event": "call.ended",
    "target_url": "https://hooks.example.com/abc",
    "include_transcript": true,
    "source": "zapier"
  }'
# → 201 { "id": "…", "events": ["call.ended"], "target_url": "…", … }

• event (one) or events (array); valid values: call.started, call.ended, transcript.ready, tool.invoked, recording.ready, call.analyzed, or *. Unknown names are rejected with the valid list.
• Optional agent_id scopes the subscription to one agent.
• source labels the hook in the dashboard (zapier, make, n8n, viasocket, …) and filters GET /api/v1/hooks.
• Deliveries are HMAC-signed and retried like every webhook — see receive & verify webhooks. If your receiver answers 410 Gone, the subscription is disabled immediately.

n8n

Install the community package n8n-nodes-telenow (Settings → Community Nodes on self-hosted; on n8n Cloud once verified). It ships:

• Telenow Trigger — pick events + optionally one agent; activating the workflow registers the webhook via /api/v1/hooks automatically.
• Telenow — Place an outbound AI call (agent dropdown, context variables, opening line, AMD behavior), Get call (with transcript), Get many calls, list agents/numbers. Usable as a tool by n8n AI agents.

Agent → n8n as a tool (round-trip): add a Webhook node (Header auth) + Respond to Webhook node, then create a Telenow agent tool of kind HTTP pointing at the production webhook URL. The agent receives whatever JSON you respond with — keep the workflow under ~10s. n8n's MCP Server Trigger node also works: paste its URL + bearer token into a Telenow MCP tool.

Zapier

Until the Telenow Zapier app is listed, wire it directly:

• Trigger a Zap from Telenow: Zap trigger = Webhooks by Zapier → Catch Hook; register the catch-hook URL via POST /api/v1/hooks (or the Webhooks page).
• Act on Telenow from a Zap: Webhooks by Zapier → Custom Request to POST /api/sessions/initiate-call with your X-API-Key header.
• Agent → Zapier as a tool: Catch Hooks can't return data to the caller, so use them for fire-and-forget actions with a handoff line ("I've logged that for you"). For round-trips, create a Zapier MCP server at mcp.zapier.com and paste its URL into a Telenow MCP tool (each call uses 2 Zapier tasks).

Make

• Trigger a scenario: Webhooks → Custom webhook, subscribe its URL via POST /api/v1/hooks.
• Synchronous agent tool: end the scenario with Webhook response returning JSON — the agent speaks the result. Keep the scenario fast; the agent tool times out at 15 s.
• Make MCP: Make's cloud MCP server exposes your on-demand scenarios as callable tools — paste the MCP URL into a Telenow MCP tool.

viaSocket

• Trigger a flow: use Webhook as trigger, subscribe the generated URL via POST /api/v1/hooks.
• Synchronous agent tool: add a custom Response step to the flow and point a Telenow HTTP tool at the flow's webhook URL.
• viaSocket MCP: paste your viaSocket MCP server URL into a Telenow MCP tool to reach its app catalog from a live call.

Example: log every analyzed call to a CRM

1. POST /api/v1/hooks with {"event": "call.analyzed", "target_url": "<platform webhook url>", "source": "make"}.
2. The payload carries analysis.summary, analysis.sentiment, analysis.disposition, analysis.actionItems — map them onto your CRM fields.
3. Need the recording too? Subscribe recording.ready, or set include_recording on a call.ended subscription.

See also

• Integrations & connectors — built-in vendor connectors (WhatsApp, CRM, Sheets, payments, calendars, forms) + MCP servers and aggregators
• Receive & verify webhooks — HMAC signature verification and retries for hook deliveries
• Webhook events reference — the exact payload of each event type
• Tools & function calling — HTTP, request-template (curl), and MCP tools an agent calls mid-conversation
• Programmatic phone calls — POST /api/sessions/initiate-call to place AI calls from a workflow
• Chat API — drive a text agent over /api/v1/chat from a workflow
• Authentication — creating and scoping API keys