My printnode is getting an error, not sure if its on the GMAIL side, I have it check my email for a attachment and it supposed to print, looks as if does see it but fails every time
queued
Could not resolve host: ins.pdf, inspection2.pdf
4.28.6
147 ms
2 ms
November 29, 2024 07:46:07
error
download failed
Page 1 / 1
@yanni
It may help if you could show your configuration via screenshots.
Don’t forget to mask any sensitive data.
Should I need to fill this out ?
In the content block, it is looking for the URI for the PDF document and you’re sending it the list of filenames. So the error you get back is that it couldn’t find the host because there isn’t one.
If you look at the configuration below you will see that the you need to place the attachment into the box.
I hope this makes sense, Printnode is looking for a web address and you’ve send a string of names.
Hope this is useful
Hi @yanni,
We just wanted to see how everything is going with your Zap. Did Badger's recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
We're looking forward to your response.
I’m not sure , how to even get to that set up , below is my configuration options, and the PDF URI seems the only option I have, while your example shows attachment ?
@yanni
The content type might be wrong. I think you should use the dynamic data by clicking the three buttons.
Add the Attachments Mime type from the gmail step. Doing this would mean you’re choosing the attachment’s type,
You could also try writing ‘application/pdf’ in lower case and see if it helps. But this would mean you can only send pdf files.
Does that help?
Hi there @yanni
How did you get on with Badger’s suggestions here—did they help to get things resolved?
Keen to ensure you’re all set so please do let us know if you need any further help at all!
Yes got it fixed , was a different issue but working through this I figured it out
thank you
That’s fantastic to hear, @yanni! I’m so glad you were able to get it sorted. If you’re open to sharing, we’d love to hear more about what the solution was—this could be helpful for others who might run into similar issues.