Browse+
Explore all topics
Easy-to-follow VICIdial guides
Automate tasks
Connecting VICIdial to other tools safely. Start with the guide that matches what you are trying to learn or fix.
Learn about automate tasks
Guides for automate tasks
15All guides shown
96Automate tasksMessaging integrationWhatsApp with VICIdial: a safe, opt-in integration planConnect a consented WhatsApp conversation to the right VICIdial lead without pretending that a phone dialer is a WhatsApp inbox.97Automate tasksFollow-up workflowSend an email after a VICIdial call without creating an open relayDesign a consented, auditable post-call email handoff that starts with VICIdial's own Dispo Call URL and keeps mail credentials and customer data protected.AI01Automate tasksAI and call recordingsAdd AI transcription to VICIdial safely: a test-only call-recording workflowTurn one consented lab recording into a transcript without routing live calls through an AI service.CRM01Automate tasksCRM integrationConnect VICIdial to Vtiger or Salesforce safely: a test-only CRM sync patternStart with VICIdial's own CRM Popup, Web Form and Call URL fields, then build a small, traceable test sync for whatever they can't reach.54Automate tasksSMS and OmnichannelAdd SMS to VICIdial: no native feature, just an integrationVICIdial has no native SMS sending: no outbound texting screen, no carrier connection, no message table in its schema. This guide wires a real SMS provider into VICIdial's existing extension points — a Call URL fires on a call event, your own relay calls the provider's HTTPS API, and the Non-Agent API's update_lead writes the delivery result back onto the lead, with inbound replies handled the same way.62Automate tasksCRM IntegrationIntegrating VICIdial with Salesforce: no native connector, just extension pointsVICIdial has no built-in Salesforce connector: there is no app to install and no setting that turns it on. This guide starts with the three agent-facing mechanisms it already ships — Web Form, CRM Popup, and Start Call URL — then shows the architecture you build beyond them: Call URLs and the Non-Agent API on the VICIdial side, the REST API and OAuth 2.0 on the Salesforce side, how to give a lead the same identity in both systems using vendor_lead_code and a Salesforce external ID field, and why every write has to be idempotent, because a call event can duplicate, arrive late, or never arrive at all.69Automate tasksPer-minute economicsAmazon Connect vs VICIdial: no seat license on either sideAmazon Connect publishes no per-seat price at all: $0.038 per voice minute plus telephony, the same usage-based shape VICIdial already runs on. This article prices that structural match, contrasts it with the seat-priced quotes already verified on this site, and hands over the query and formula to price your own connected minutes against either rate card.73Automate tasksIntegration surface, not a top-10 rankingAI SDR tools next to a VICIdial call centerEight AI SDR (sales development representative) tools verified against their own websites, mapped to the one integration surface that actually exists on a self-hosted VICIdial system: Call URLs out, the Non-Agent API back, and a hard line around anything that wants call audio.16Automate tasksAPI boundariesVICIdial Agent API vs Non-Agent API: choose the boundary before automatingUse the Agent API for a logged-in agent session and the Non-Agent API for administrative data and reporting work.17Automate tasksIntegration boundariesVICIdial webhooks and events: Call URLs, Agent Events Push, CORS, WebSockets and SSE boundariesBuild idempotent integrations around documented VICIdial extension points without calling browser events a transactional webhook stream.26Automate tasksSchema decision frameworkVICIdial custom fields: dynamic tables, APIs and migration safetyTreat list-specific custom fields as runtime schema, then test imports, API writes, backups and list moves without guessing at a table definition.13Automate tasksAgent APIThe VICIdial Agent API with real code: curl, JavaScript and agc/api.phpA practical, code-heavy walkthrough of the VICIdial Agent API at agc/api.php: how to authenticate, the shape of a request and response, and runnable curl and JavaScript for pause, resume, dial, hangup, disposition, and transfer.18Automate tasksVICIdial APIsThe VICIdial Non-Agent API, with real codeA hands-on tour of `/vicidial/non_agent_api.php`, cited against VICIdial's own shipped docs: authentication, per-function permission levels, and working curl and JavaScript calls covering all 59 functions across leads, lists, campaigns, users, DIDs, phones, recordings, monitoring, housekeeping, and reports.20Automate tasksWebhooks and CRM integrationVICIdial Call URLs: trigger an external system on call eventsHow VICIdial's built-in Call URL feature fires an HTTP request to your own endpoint on lifecycle events like start, disposition, and dead call, including the --A--field--B-- substitution syntax and why every receiver must be idempotent.09Automate tasksIntegration patternsVICIdial API automation that does not hide failuresNeither API gives you an idempotency key or a request ID — build your own operation key, classify SUCCESS, ERROR and NOTICE separately, and verify writes outside the writer account.