What is your goal?
If you have several users in Pandadoc and delete the user that was used to connect to Make using OAuth, your webhooks will stop working.
Actually it is only the module in the scenario that stops working, not the webhook itself.
- The webhooks on the Pandadoc side will still exist as they are not dependent on a useraccount.
- Pandadoc will keep sending data to the webhooks after the user got deleted
- Make will keep receiving the data on that webhook (will queue the records)
- Make will not process the webhook data as the webhook modules ARE dependent on the old Pandadoc useraccount
What is the problem & what have you tried?
Pandadoc has a lot of options when configuring webhooks. If you have complex filters on your webhook, or a lot of Pandadoc webhooks in general you will probably don’t want to setup all the webhooks again hoping you configured them the same as before.
However the webhook module in your scenario is connected to the old Pandadoc user account that does not exist anymore. This is a Make quirk in de Pandadoc Make app, not a Pandadoc issue. Webhooks in Pandadoc are not actually connected to a useraccount.
Save yourself a lot of work and don’t create a new Pandadoc connection with a new user. You will not be able to get the old webhooks running and you will lose the webhook queues.
SOLUTION:
- Login on Pandadoc using the new account that works
- Go to the Connections page in your Make account
- Reauthorize the existing Pandadoc connection and go through the steps
Not only the regular Pandadoc modules will start working, but also the Webhook modules with their original configuration. Even better, any old queued data can be processed if chosen to.
Error messages or input/output bundles
Connection couldn’t be verified
Failed to verify connection ‘PandaDoc connection’. Status Code Error: 400
