Dialpad test mode issue with webhook integration in Zapier

Hi ​@tim ballering 

Help links for using Dialpad in Zaps: https://help.dialpad.com/docs/using-zapier-with-dialpad

For us to have more info about what you are referring to post screenshots showing:

• how your Zap steps are outlined
• how your Zap steps are configured
• the DATA IN/OUT for the Zap steps involved

Thanks.  This is frustrating because I can see from the sample test that it will do as we need, bringing DialPad data into our on prem database to match calls with clients.  

I looked at the DialPad help doc before posting here.  I have never seen this screen, enven after deleteing and reconnecting DialPad to Zapier:
 

My Zap is:

 

​@tim ballering 

This looks like an old outdated version of the Dialpad Zap app integration.

Notice these:

• Logo
• “By Invite”
• (1.0.1) 

​@tim ballering 

Have you tried turning the Zap ON and testing live?

Zaps work while turned ON for new data going forward.

Then check your Zap Run history to see activity. https://zapier.com/app/history/ 

If there is activity, then you can click into a Zap Run to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot.

Hey ​@tim ballering,

Make sure to use a real API Dialpad key instead of a Sandbox one. Also while connecting Dialpad to Zapier, Select ‘No’ for the Sandbox option.

 

Helpful article about how to setup Dialpad with Zapier- https://www.dialpad.com/app-marketplace/zapier/#how-to-setup. Try to see if it fixes the issue. Hope it helps!

​@Sparsh from Automation Jinn 

This screen does not appear nor is there option for adding the DialPad API key. It just connects with oAuth.  I have disconnected DialPad from Zapier and reconnected a few times, hoping to find a place to enter the API key.

​@Troy Tessalone 

As soon as I turn the Zap on, it turns off, without recording anything in the history.  The only items in the history on this Zap is the original tests, which work without error

Thanks

Hey ​@tim ballering,

Don’t you also see this screen? 

 

See more about in this article here- https://help.dialpad.com/docs/using-zapier-with-dialpad. Can you try deleting the connection and reconnecting to see if it helps? If the issue still persists, you can reach out to Zapier Support here- https://zapier.com/app/get-help. Hope it helps!

Yes, I see that screen, just not the one where the API key can be added

Thanks

​@tim ballering 

Help for what to check when a Zap automatically turns OFF: 

Thanks.  I am fairly sure it is a permissions error, but cannot find any logs 

Hey ​@tim ballering,

Nice you were able to figure it out and see that screen. I think the screen with API key is not available anymore as it just connects with OAuth and it’s probably from some past documentation. Hope it helps!

Hi there ​@tim ballering 👋 Have you have any luck in getting the Zap fixed?

If not, can you confirm whether your Dialpad account is on one of their Pro or Enterprise paid plans, or on their Dialpad Connect, Dialpad Sell or Dialpad Support licenses? Looks like they have that listed as a requirement in the help guide that others have previously referenced here:

Wondering if that might be the issue, since it sounds like the account should have the correct permissions as it’s got the required Company Admin role.

Looking forward to hearing from you!

It is a Pro plan, one we’ve had for five years.  I was able to get the automation to work with a different tool, but never with Zapier.  It seems to be the method Zapier uses to authenticate.

Hey ​@tim ballering,

I thought you were able to see the screen to put Sandbox option to False. Did it not work after that?

Can you also check into Dialpad Settings → Integrations if you can find Zapier there and able to change sandbox to production?

If the issue still persists, you may want to directly contact the Dialpad support and the Zapier support here-https://zapier.com/app/get-help. Hope it helps!

Are you just seeing the sample test data zapier gives?

Thanks for confirming that ​@tim ballering. I checked on this end and couldn’t see any bug reports open for any similar authentication issues currently. I agree with Sparsh, definitely would be worth reaching out to Dialpad, as well as our Support team here to investigate further in case there’s a bug. 

Please do keep us updated on how you get on with them, want to make sure this gets sorted 🙂