Question: I am reading through the pandadoc documentation and it says you need an enterprise account to use webhook features with Make. I would assume the watch documents task in make is a webhook. Is this actually true? I couldnt find in the video what version you might be on.
Hey Hunter! Great question. I know exactly what you're referring to. I believe they don't really enforce this rule.... It has always worked with zapier for example.. and yes there was a time when it didn't work with make. But now I believe it works and you don't have to be on an enterprise account.
@@sonorusconsulting cool. Thanks for the reply. Been researching and watching videos on how to create something similar you have shown here and pandadoc looked like a good fit but that disclaimer on the pricing threw me off.
I’m in the same boat. I ended up emailing Pandadoc when I should have just looked here in the comments. @@sonorusconsulting, are you using the mid-tier plan “Business” plan?
Thanks for the detailed video on this automation setup. I haven't used the temporary URL buffer file step before, but is there an issue not adding that additional step before uploading the file into Airtable?
Hey Andre! That's a good question - the answer simple. It has to do with the way that PandaDoc works in combination with how Airtable works. When you request to download a 'document' from PandaDoc, they don't hand it to you on a silver plater. Instead they supply you with the 'binary' data for the file. In simple terms, you get the 0s and 1s of file instead of URL 'to the file' .. Now this is half the story... Every time we want to upload a file to Airtable we need to provide a URL to file. Providing 'binary data' won't work. Hence, that's why we need to use a service such as 1saas to effectively upload the file (binary data) and generate a URL for Airtable to use. Hope this helps. Many thanks Alex @ Sonorus
@@sonorusconsulting - Thanks Alex. I also had another question about this integration. Do you need a specific Pandadoc plan to use this approach? As I was looking at the Pandadoc app's integration settings and it seemed the webhooks integration required the Enterprise plan. But I seem to be able to connect via Make onto their Business plan. So not sure if your approach would also work on the Essentials plan.
On the Watch Documents scenario (step 3) in MAKE I have been unable to resolve the 1SaaS/0CodeKit module error "[400] Bad request. Please check your parameters. More details: Error while uploading file: File already exists" therefore it will not move pass this error and update the airtable once signature has been received, any suggestions?
Thank you for this informative video. I have a question. In my Make account there is no "Watch Documents" feature in the PandaDoc modules list. What could be the reason?
Hello, very good ! I try script from step 1, and it is not working with this : let call = await fetch ("${webhook}?recordID=${urlParams}"); TypeError: Invalid URL: ${webhook}?recordID=${urlParams}
@@matthooczko8217 is this what you mean?: { "subject": "This is my subject", "message": "Hello! This document was sent from the PandaDoc API.", "silent": false, "forwarding_settings": { "forwarding_allowed": true, "forwarding_with_reassigning_allowed": true } }
Question: I am reading through the pandadoc documentation and it says you need an enterprise account to use webhook features with Make. I would assume the watch documents task in make is a webhook. Is this actually true? I couldnt find in the video what version you might be on.
Hey Hunter! Great question. I know exactly what you're referring to. I believe they don't really enforce this rule.... It has always worked with zapier for example.. and yes there was a time when it didn't work with make. But now I believe it works and you don't have to be on an enterprise account.
@@sonorusconsulting cool. Thanks for the reply. Been researching and watching videos on how to create something similar you have shown here and pandadoc looked like a good fit but that disclaimer on the pricing threw me off.
I’m in the same boat. I ended up emailing Pandadoc when I should have just looked here in the comments. @@sonorusconsulting, are you using the mid-tier plan “Business” plan?
Thanks for the detailed video on this automation setup. I haven't used the temporary URL buffer file step before, but is there an issue not adding that additional step before uploading the file into Airtable?
Hey Andre!
That's a good question - the answer simple. It has to do with the way that PandaDoc works in combination with how Airtable works.
When you request to download a 'document' from PandaDoc, they don't hand it to you on a silver plater. Instead they supply you with the 'binary' data for the file. In simple terms, you get the 0s and 1s of file instead of URL 'to the file' ..
Now this is half the story...
Every time we want to upload a file to Airtable we need to provide a URL to file. Providing 'binary data' won't work.
Hence, that's why we need to use a service such as 1saas to effectively upload the file (binary data) and generate a URL for Airtable to use.
Hope this helps.
Many thanks
Alex @ Sonorus
@@sonorusconsulting - Thanks Alex.
I also had another question about this integration. Do you need a specific Pandadoc plan to use this approach? As I was looking at the Pandadoc app's integration settings and it seemed the webhooks integration required the Enterprise plan. But I seem to be able to connect via Make onto their Business plan. So not sure if your approach would also work on the Essentials plan.
On the Watch Documents scenario (step 3) in MAKE I have been unable to resolve the 1SaaS/0CodeKit module error "[400] Bad request. Please check your parameters. More details: Error while uploading file: File already exists" therefore it will not move pass this error and update the airtable once signature has been received, any suggestions?
Hey Dan 👋 I'll take a quick look and ping you a loom here
Thank you for this informative video. I have a question. In my Make account there is no "Watch Documents" feature in the PandaDoc modules list. What could be the reason?
@mehmetulga - that's a bit wierd. Are you 💯 sure that's the case?
@@sonorusconsulting i found it now. thank you.
Hello, very good ! I try script from step 1, and it is not working with this :
let call = await fetch ("${webhook}?recordID=${urlParams}");
TypeError: Invalid URL: ${webhook}?recordID=${urlParams}
Hey! Try using 'Record_Id' instead of 'recordID'.. should work..
@@sonorusconsulting Thanks, the error was I used ' and not `
@@grobinconsulting aahhh ok ..... makes sense..
I'm not sure what i'm doing wrong but i can't get the Body to work correct in step 2 Any chance you can copy and paste that in the comments?
[400] JSON parse error - Extra data: line 12 column 1 (char 227)
{
"message": "Hello! This document was sent from the PandaDoc API.",
"subject": "Please check this test API document from PandaDoc"
}
@@matthooczko8217 is this what you mean?:
{
"subject": "This is my subject",
"message": "Hello! This document was sent from the PandaDoc API.",
"silent": false,
"forwarding_settings": {
"forwarding_allowed": true,
"forwarding_with_reassigning_allowed": true
}
}
Yes it is. Thank you!
@@matthooczko8217 no problem! :)