Cualify.
Get started

Connect Plivo

Store and verify your Plivo credentials in Cualify. ~5 minutes. Calls run on Exotel only today.

Calls don't run on Plivo today. Cualify places every call — campaigns, REST API calls and test calls — on Exotel, from a Cualify number or your own Exotel account. You can connect Plivo so your credentials are verified and stored, but no call is dialled through it. For live calling, use Exotel.

What connecting Plivo does today

Cualify checks your Auth ID + Auth Token against Plivo's Account API, then stores them encrypted. The connection shows under Connected accounts on /integrations/telephony, where you can re-verify or disconnect it. That's all it does for now: it doesn't change which number your calls go out from.

Prerequisites

  • An email address Plivo can verify
  • A phone number Plivo can SMS for verification
  • Admin or owner access to your Cualify workspace

You don't need to top up Plivo or rent a Plivo number for this: Cualify only verifies the credentials.

Step 1 — Create a Plivo account

  1. Sign up at console.plivo.com/accounts/register
  2. Verify your email (link in inbox) and phone number (SMS code)
  3. Plivo's onboarding asks "What are you building?" — pick Voice. Choose your billing currency (USD recommended).

Step 2 — Get Auth ID + Auth Token

  1. Plivo console Overview page (loads by default after sign-in)
  2. Top-right Account card shows Auth ID (starts with MA, ~20 chars) and Auth Token (40-char string, masked — click reveal)
  3. Copy both somewhere safe
Security note: Plivo's Auth Token is full-access. Cualify stores it AES-256 encrypted and never logs it. If you generate a new token in Plivo later (Plivo Console → Account → Auth Token), connect again in Cualify with the same connection name to replace the stored one.

Step 3 — Connect Plivo in Cualify

  1. In Cualify, go to /integrations/telephony
  2. Under Connect a phone provider, click the Plivo tile
  3. Paste your Auth ID + Auth Token
  4. Click Verify & connect — we hit Plivo's Account API (GET /v1/Account/<authId>/) to confirm. Nothing persisted if Plivo rejects.

Troubleshooting

Error: "Plivo rejected those credentials"

Either the Auth ID/Token combo is wrong (re-fetch from the Plivo console Overview) or your account is suspended. Plivo returns 403 on suspended accounts, which Cualify surfaces with this same error message — log into the Plivo console to check account status.

What's next?