RingCentral Call End → Google Sheets

[madmoneymike5]

Your Task History ID

IjU3NjUwNTZkMDYzMzA0Mzc1MjZiNTUzYzUxMzQ1MTY2NTQzMjBmMzEi_pc

Objective: Log every call for every user to Google Sheets as they end so that we can see live call stats using pivot tables.
There isn't enough information transmitted in the call end event to grab the data we need so I have to try to run a custom API command.

The workflow I have setup:

1. Trigger: RingCentral Call Ended
2. Action: Custom API Request
   1. Request Method: GET
   2. API Endpoint URL: https://platform.ringcentral.com/restapi/v1.0/account/[account number redacted]/extension/[redacted]/call-log?view=Simple&TelephonySessionId=[1. Body TelephonySessionId : s-randomnumbersandlettershere
   3. Payload Type: JSON
   4. Add Headers: Unchecked
   5. Set Parameters: Unchecked
   6. Data: Blank
   7. Simple Request Toggle: On
3. Action: Google Sheets : Add New Row
   1. Select Spreadsheet: Sales Hub
   2. Select Sheet: Call Logs
   3. From: Records 0 PhoneNumber : +[redacted]
   4. To: Records 0 To PhoneNumber : +[redacted]
   5. Result: Records 0 Result : Call connected
   6. Duration: Records 0 Duration : 46
   7. Recording: Records 0 Recording ContentUri : https://media.ringcentral.com/restapi/v1.0/account/[redacted]/recording/[redacted]/content

All testing works in Pabbly as expected. However, I'm experiencing two issues...
1. It is logging the call before the call that just ended rather than the call that is triggering the workflow. So if a call is placed to 888-888-8888 at 1:00 pm and then ends, it will log the call that preceded it. It won't log the call to 888-888-8888 at 1:00 pm until whenever the next call ends.
2. It logs the above call multiple times. What's strange is that the number of repeat entries varies seemingly randomly from call to call.

 

[Luv]

Hey @madmoneymike5

Upon looking into your issue we found out that the trigger is getting multiple responses for the same call. This is because you have used the "Save and Send Test Request" button multiple times. Please refer to the image below which shows the warning when you click on the button.

To rectify your issue, Kindly clone this workflow and use the cloned one. Also, please make sure that you do not use "Save and Send Test Request" button multiple times. You can refresh responses and capture the latest one.

Let us know if it works for you.

 

[madmoneymike5]

I have cloned and disabled the original workflow as instructed. However, no new calls are being logged now.

 

[ArshilAhmad]

Please click on 'Save & Send Test Request', capture a new response in your trigger step, and see if that fixes your issue.

If the issue persists, create a new workflow from scratch (without cloning) and set up RingCentral as the trigger application in this new workflow. Once you have done that, you can copy the remaining steps from your other workflow, paste them into this workflow, and save each step.