↑↓ selectEnter openEsc close

    1. Elbuz
    2. Connecting a PBX

    How to connect RingCentral to Elbuz: a JWT API app and event subscription without a webhook

    6 min readUpdated

    Elbuz connects the RingCentral API to the CRM: managers see the customer card while the phone rings, call from the card in one click, and every call lands in the log and customer history.

    When you need this:

    • A customer calls — their card pops up: name, city, recent orders.
    • Nobody answered a group call — “Pulse” gets a “Call back” task.
    • Need to call back — “Call” in the card: RingCentral rings the manager, then the customer.
    • A supervisor wants to hear calls — recordings and AI summaries reach the log hourly, after reconciliation.

    Where to start: create a REST API app in the Developer Console.

    What the RingCentral integration does

    Through a server app with JWT, Elbuz starts RingOut calls, reconciles the account's call log every hour, plays call recordings and receives call events. You don't need to enter an event address in RingCentral: Elbuz creates and renews the subscription itself.

    • Caller card. An “Incoming call” pop-up with the customer's name, city and orders appears for the employee being called (call card).
    • A missed call becomes a task. The manager gets a “Missed call” pop-up with a “Call back” button, and “Pulse” gets a high-priority task; it closes by itself after a conversation with that number.
    • Calls from the customer card. Via RingOut: first to the manager's extension, then to the customer (how the call goes).
    • Recording, transcript and summary. After reconciliation, the recording plays from the log, and AI analysis writes a summary to the customer's feed (AI call analysis).
    • All account calls in one log. Incoming and outgoing, with the outcome; reconciliation refines the duration (call log).

    What you need from RingCentral

    • A app with JWT auth flow in the Developer Console — it gives you the Client and Client Secret.
    • Six app permissions — see the table in step one.
    • An administrator's JWT (Super Admin) — otherwise Elbuz won't see the numbers and calls of the whole account.
    • A production account — sandbox keys won't work.

    Console items are named as in the RingCentral interface. The paths come from the RingCentral documentation; if an item is named differently, go by these pages or ask RingCentral support:

    How to connect RingCentral

    Four steps: an app in the Developer Console, a JWT, keys in Elbuz and extensions.

    Step one: an app in the Developer Console

    1. Sign in to the RingCentral Developer Console (developers.ringcentral.com) with a user of your RingCentral account → Apps → Create App.
    2. App type — REST API App → Next.
    3. In the Authentication section, select JWT auth flow.
    4. In the Security section, add the permissions listed in the table below and select “This app is private and will only be callable using credentials from the same RingCentral account”.
    5. Create the app and copy the Client ID and Client Secret from its page.
    RingCentral permissionWhy Elbuz needs it
    Read Accounts (ReadAccounts)the list of extensions for “Test connection”
    Read Call Log (ReadCallLog)hourly call log reconciliation
    RingOutthe “Call” button
    Call Control (CallControl)call events — without it, RingCentral won't allow the subscription
    Webhook Subscriptions (WebhookSubscriptions)the subscription itself, delivering events to the Elbuz address
    Read Call Recording (ReadCallRecording)playing call recordings

    Step two: JWT

    1. In the Developer Console, hover over your name in the top right → Credentials → Create JWT.
    2. Under “What apps are permitted to use this credential?”, select “Only specific apps of my choice”, paste the Client ID of the app from step one → Add app.
    3. Click Create and copy the JWT.

    The JWT belongs to the user who created it, and all Elbuz requests run with that user's permissions. Create the JWT under an administrator user (Super Admin). Calls from the “Call” button are also logged under this user in RingCentral.

    Elbuz works only with the RingCentral production server, platform.ringcentral.com. Sandbox keys and JWTs won't work: “Test connection” returns an authorization error.

    Steps three and four: how to enter the keys and extensions in Elbuz

    Open the RingCentral row in the “Telephony” group. The “Active” switch is already on — leave it that way. Fields:

    Form fieldWhat to enter
    “Client ID”the app's Client ID
    “Client Secret”the Client Secret of the same app
    “JWT credential”the JWT from step two
    “Line for outgoing calls”the company's RingCentral number the customer sees when you call from Elbuz. Empty — the default number, usually the company's main number
    The “Telephony connection” card of the RingCentral form with Client ID, Client Secret, outgoing line and JWT credential
    1Client ID
    2Client Secret
    3Line for outgoing calls
    4JWT credential
    1. Client ID — the ID of your app from the RingCentral Developer Console.
    2. Client Secret — the app secret; it is stored hidden.
    3. Line for outgoing calls — the number the customer sees when you call.
    4. JWT credential — the credential of an admin user; calls are placed on their behalf.

    The form saves itself about a second after each edit: “Saving...” shows at the bottom, then “Saved”. Then click “Test connection”. Elbuz gets a token, reads the list of active RingCentral users with extensions and replies “Connected to the PBX. Employees in the PBX: ‹count›”. The same click creates the call event subscription in RingCentral.

    Events: no address to enter

    The form has a “PBX webhook address” card, but for RingCentral you don't need to paste the address anywhere — the hint in the card says so. Elbuz registers this address in RingCentral itself, and RingCentral checks during registration that the address responds. After that, the hourly reconciliation renews the subscription.

    The address is built from the domain Elbuz is running on at that moment: click “Test connection” from a different domain, and Elbuz removes the old subscription and creates a new one. So test the connection from the domain you use day to day.

    The “PBX webhook address” card with the automatic subscription hint and a masked key
    1Automatic subscription hint
    2Webhook address with masked key
    3Copy
    1. The hint says the event subscription is created automatically on “Test connection”, so nothing needs pasting into RingCentral.
    2. The webhook address; the key at the end is masked.
    3. Copy — copies the address to the clipboard.

    The keys can be correct and the subscription still not created: the app is missing the Call Control or Webhook Subscriptions permission. Then “Test connection” replies “Connected to the PBX…”, but adds “webhook subscription:” and the RingCentral error text at the end.

    Until the subscription exists, the incoming call card doesn't pop up, and calls appear in the log only after reconciliation. Add the permissions and click “Test connection” again — or wait for reconciliation, which also creates the subscription.

    Step four: extensions

    In the “Internal phone” field of the Elbuz employee card, enter the employee's RingCentral extension number — a short number such as 101. After the test, the “PBX extensions without an Elbuz employee” line shows the numbers and names of RingCentral users not yet assigned to any employee.

    This number tells Elbuz who to show the incoming call card to, whose name to put in the “Manager” column for incoming calls, and which number RingCentral should ring first when the manager clicks “Call”.

    To get RingCentral working with Elbuz

    What reaches Elbuz

    FeatureHow it works with RingCentral
    Calls from the card and the log (“Call”)yes, via RingOut on behalf of the user whose JWT is entered in Elbuz
    Incoming and outgoing calls in the logyes: from the call-ended event; the hourly reconciliation refines the duration and start time
    Incoming call card in Elbuz while ringingyes: the employee whose “Internal phone” matches the extension being called sees it
    Event subscriptionautomatic: no need to enter an address in RingCentral
    Call recordingyes, after the hourly reconciliation: Elbuz downloads the recording itself and passes it to the player, so the administrator's token never reaches the browser. “Play recording” and AI analysis work. You can seek once the recording has fully loaded; a file over 25 MB won't play
    Hanging up from the incoming call cardno: the card has no “Hang up” button
    Wait time separate from talk timeno: the wait time column is always zero for RingCentral
    Voice AI employeeno: RingCentral isn't among the operators in the “Voice on the phone” section

    RingCentral specifics

    How a call from the “Call” button works

    Elbuz asks RingCentral for a RingOut call: RingCentral rings the manager's extension, and once they pick up, calls the customer. RingCentral allows RingOut only on behalf of the user whose JWT is in Elbuz, so its own log records the call under that user. The customer sees the number from “Line for outgoing calls” or the default number.

    Elbuz immediately logs the attempt under the manager. If an event for the same number arrives within 30 minutes, Elbuz adds the RingCentral data to that row — and with it, the JWT owner in the “Manager” column: RingCentral sees the call as theirs. Without the event, reconciliation adds a separate row for this call.

    Which events Elbuz uses

    Elbuz subscribes to all calls of the account and looks at the side of the call that has your employee and an external number. Calls between employees don't go to the log.

    • An incoming call rings an employee — Elbuz looks up the customer by number and shows the “Incoming call” card. While the call is in the IVR menu or a queue, there's no card: there's no one to show it to yet.
    • The call has ended — a row in the log with the outcome. The event has no duration, so the call gets its duration after the hourly reconciliation.
    • A group call — if one employee picked up, no “missed” call is logged for the others and no missed call card pops up.
    How a RingCentral event becomes an outcome in the log
    What happened in RingCentral“Result” in the log
    busy or declinedBusy
    the customer hung upCanceled
    voicemailVoicemail
    no answer or missedNo answer
    transferredTransferred
    internal error, invalid or blocked number, international calls not allowed, insufficient fundsConnection failure
    anything elseAnswered

    The hourly reconciliation refines the outcome from the RingCentral log: for example, an incoming call where the caller hung up becomes “No answer” there.

    Hourly reconciliation

    At minute 25 of every hour, Elbuz fetches the RingCentral account's call log for the past 24 hours: it refines durations, adds what events didn't bring, updates the extension list once a day and renews the event subscription.

    Scenarios

    Incoming calls go to a group of managers

    Enter each manager's extension number in “Internal phone”. The incoming call card pops up for the employee whose phone is ringing. If one of them picks up, no “missed” call is logged for the others and no missed call card pops up.

    The customer should see the company's main number

    Leave “Line for outgoing calls” empty — RingOut uses the default number, usually the main one. Need a different company number — enter it in this field.

    Elbuz moved to a different domain

    Open the RingCentral row from the new domain and click “Test connection”. Elbuz removes the old subscription and creates a new one for the new address (events).

    What to do when RingCentral won't connect

    What the app says and what to do about it
    What you seeWhyWhat to do
    “The PBX rejected the request: authorization failed (check Client ID, Client Secret and JWT)” One of the three fields is empty, the keys are from the sandbox, or the JWT isn't allowed for this app or has been revoked (if it was revoked after connecting, the message is “HTTP 401”) Check all three fields; in Credentials, allow the JWT for the app's Client ID or create a new one
    “Connected to the PBX…” with “webhook subscription: …” added; the incoming call card doesn't pop up, and calls reach the log once an hour The event subscription wasn't created: the app is missing Call Control or Webhook Subscriptions Add the app permissions and click “Test connection” again
    “The PBX rejected the request: HTTP 403: …” on “Test connection” or “Call” A permission is missing (Read Accounts or RingOut), or the JWT wasn't created by an administrator Add the permission to the app; create the JWT as an administrator
    “Your employee card has no extension number” The “Internal phone” field is empty: RingCentral has nowhere to call first Enter the manager's extension number (step four)
    A call in the log with no duration The call-ended event doesn't include the duration Nothing: the duration appears after the next reconciliation, at minute 25 of the hour

    Other cases where a call didn't show up are covered in the general troubleshooting of Telephony in Elbuz.

    FAQ

    Where do I get the Client ID, Client Secret and JWT for RingCentral?

    The Client ID and Client Secret are on the page of the REST API app with JWT auth flow in the Developer Console (Apps → Create App). The JWT: your name in the top right → Credentials → Create JWT, as the account administrator, allowed for this app's Client ID.

    Which permissions should the RingCentral app have?

    Read Accounts, Read Call Log, RingOut, Call Control, Webhook Subscriptions and Read Call Recording. Without Call Control, RingCentral won't allow subscribing to call events; without RingOut, “Call” won't work; without Read Call Recording, call recordings won't.

    Where in RingCentral do I paste the webhook address?

    Nowhere. Elbuz creates the event subscription itself when you click “Test connection”, and renews it with the hourly reconciliation.

    Why are calls from Elbuz logged under one user in RingCentral?

    RingCentral allows RingOut only on behalf of the user whose JWT is entered in Elbuz. RingCentral first rings the manager's extension, then the customer, but in the RingCentral log the call belongs to the JWT owner.

    Can I listen to a RingCentral call recording from Elbuz?

    Yes, after the hourly reconciliation. Elbuz downloads the recording itself and passes it to the player; the token never reaches the browser. The app needs the Read Call Recording permission.

    Can I hang up a RingCentral call from Elbuz?

    No, the incoming call card has no “Hang up” button for RingCentral.

    Can I put a voice AI employee on a RingCentral number?

    No: RingCentral isn't among the operators in the “Voice on the phone” section. Supported operators are listed in Voice AI employee.

    Where to find it and who has access

    Menu
    Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → RingCentral
    Extension
    “Users” → employee card → “Internal phone”
    Call log
    Directories → Contacts → Call log
    Access right
    system settings and the “Call log” window; you don't need any rights just to make calls
    Prepare
    sign-in to the RingCentral Developer Console as the account administrator

    The window that opens from the operator row is called “API access settings for external services”; for RingCentral, the first card has three keys instead of two. Without the right to “Call log”, “Test connection” doesn't work, and neither does the event subscription. The general mechanics — log, call card, permissions — are in Telephony in Elbuz.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free