Skip to main content

Connect Five9 to Qvasa: Send Your Five9 Events with an Integration Token

Connect Five9 to Qvasa: Send Your Five9 Events with an Integration Token

Five9's Event Subscription can push your contact center's events (calls starting and ending, agents changing state) to an address you choose, as they happen. Point it at Qvasa, and Qvasa stores every event it receives for your account, as it arrives.

The connection runs one way. Five9 sends events to Qvasa; Qvasa never signs in to Five9 and holds no Five9 login. Five9 proves each delivery is yours with an integration token: a key you generate in Qvasa that can do exactly one thing, deliver Five9 events to your account.

Setup takes about ten minutes: one button in Qvasa, one subscription in Five9, then a test call.


Before you start

  • A Qvasa admin generates the token. The Five9 page is under Settings > Integrations > Five9. If you don't see it, ask your Qvasa team to turn the Five9 connector on for your account.

  • A Five9 administrator creates the event subscription, in Five9's ES – Configuration.

  • Have both people on hand, or pass the token from one to the other safely: it's shown only once.


1. Generate a Five9 token in Qvasa

Open Settings > Integrations > Five9. The page reads Not set up and walks through the same three steps as this article.

Click Generate a Five9 token. There's nothing to choose: the token is made for this connection, can make one request (delivering a Five9 event) and nothing else in Qvasa, and is limited to 300 deliveries a minute and 100,000 a day.

Qvasa shows the value Five9 needs, Bearer followed by the token's secret. Click Copy and keep it for step 2. It's shown only once: Qvasa keeps only a fingerprint of the secret, so nobody can read it back. If you lose it, generate another token.


2. Create the event subscription in Five9

The Qvasa page lists every Five9 setting with its value. In Five9's ES – Configuration, your Five9 administrator creates a subscription with:

  • Delivery method: HTTPS.

  • HTTP method: POST.

  • URL endpoint: the address on the Qvasa page (use its Copy button).

  • Header Authorization: the value you copied in step 1, Bearer, a space, then the secret.

  • Header Content-Type: application/json.

Then choose the events and fields to send. Qvasa stores whatever arrives, as it arrives, so pick everything you may want reported on later: call events and agent state changes.


3. Start it, then check it in Qvasa

Save the subscription and press Start. Five9 begins delivering from that moment. Place a test call, then reload the Five9 page in Qvasa.

What done looks like: the status beside the title reads Receiving, Last delivery shows the time of your test call, and both Connection health checks read Working:

  • Authentication: Five9's token is accepted.

  • Storing deliveries: every delivery is being stored.

Further down, Latest deliveries lists the 25 most recent, with when each arrived, the token it came with, its format and size. The contents of a delivery are never shown on the page.


How the connection is secured

  • Qvasa holds no Five9 login. Five9 sends events to Qvasa; Qvasa never signs in to Five9 or calls it.

  • The token can do one thing: deliver Five9 events to your account, at the one address in step 2. It can't read any of your data.

  • You stay in control. In Settings > Integration Tokens you can limit the token to Five9's IP ranges, roll its secret with no outage, or revoke it at any time.

  • Refused requests are recorded, on the Five9 page and in the token's activity.


Troubleshooting

The Five9 page's Refused and unstored deliveries list says what went wrong with each delivery Qvasa could tie to your token, at most one a minute for each reason.

  • Five9 reports a 401, and nothing appears in Qvasa. The Authorization header is missing or its secret is mistyped. A request Qvasa can't recognize can't be tied to your account, so it isn't listed. Paste the secret again after Bearer and a space, or generate a new token.

  • Came from outside the token's IP ranges. The token is limited to IP ranges that don't include the address shown. Add Five9's ranges to the token in Settings > Integration Tokens.

  • Over the rate limit. Five9 sent more than 300 deliveries in a minute or 100,000 in a day. Ask your Qvasa team to raise the limit.

  • Over the 1 MB limit. One delivery was larger than 1 MB. Send fewer fields in the subscription.

  • Waiting for first event. The token exists but nothing has arrived. Check the subscription is started in Five9, then place a test call.

Did this answer your question?