Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Get Help
  • Troubleshooting
  • Dialpad error: Error parsing ProtoRPC request (Unable to parse request content: Invalid enum value "disposition")
Question

Dialpad error: Error parsing ProtoRPC request (Unable to parse request content: Invalid enum value "disposition")

  • September 26, 2023
  • 2 replies
  • 28 views
K

Hi community,

I’m trying to set up a flow with Dialpad disposition as the trigger and got this error:
 

Step 1 - Call State Changed in Dialpad

The app returned "Error parsing ProtoRPC request (Unable to parse request content: Invalid enum value "disposition")".

 

Does it anyone know what’s happening?

 

Thanks!

Did this topic help you find an answer to your question?

2 replies

K
  • klarityITBeginner
  • Author
  • Beginner
  • 3 replies
  • September 26, 2023

For context, if I choose disposition as the trigger, after I publish the zap, it will be immediately switched off, and then I receive the above error notice through Email from Zapier.

ken.a
Forum|alt.badge.img+6
  • ken.aZapier Staff
  • Zapier Staff
  • 6466 replies
  • September 27, 2023

Hi there @klarityIT,

I did some digging into the error, and I haven’t really seen much related. I’d recommend reaching out to our Support Team so that they can dig deeper into the logs of the Zap and determine the cause of the issue.

You can reach our Support Team here: https://zapier.com/app/get-help

Thank you for your patience and understanding.

Reply


Terms & Conditions