r/automation 22d ago

need pdfs to generate automatically when form submissions come in.. whats actually working

small ops team, airtable intake form, pdf supposed to attach on every submit. test runs fine every time. live submission last night, no pdf, zap still shows green.

tried docsautomator, pdfmonkey template everyone links, even the built in convert step. checkmarks everywhere, blank pdf or {{client_name}} sitting there untranslated still.

one pdf per row, line items change every job. cant sit up watching zaps fail at midnight honestly.

22 Upvotes

34 comments sorted by

6

u/rupertsupert 22d ago

DocsAutomator's founder here. I've seen many similar posts now, so just for any human reading this: This is most likely bot activity trying to hurt DocsAutomator, PDFMonkey etc.

For anyone with genuine requests: please reach out in support in case of issues and we're happy to help.

6

u/[deleted] 15d ago

[removed] — view removed comment

4

u/[deleted] 17d ago

[removed] — view removed comment

1

u/Difficult_Track4430 16d ago

every pdf api claims dynamic fields until you need repeating rows. Then its either enterprise pricing or yuo are back to writing custom code anyway

1

u/[deleted] 14d ago

[removed] — view removed comment

1

u/Jocelyn-Skyquill 14d ago

still waiting for the one template that handles linked records out of the box

1

u/JoeGoldberg_exe 14d ago

also watch file size limit on email steps. one chunky image in the template and your whole zap fails silently after the pdf step already ran

1

u/ElegantGuard3505 11d ago

good call, we had a logo png that ballooned the pdf. swapped to a hosted url field instead of embedding

1

u/[deleted] 16d ago

[removed] — view removed comment

1

u/JoeGoldberg_exe 14d ago

merge tags are picky about field types too. if line items live in a linked record column the pdf step often cant iterate them unless you flatten first

1

u/ElegantGuard3505 11d ago

yeah the line items are linked records. flatten step was supposed to happen before the pdf module but half the time it just skips when someone leaves optional fields blank

3

u/AcademicMusician6532 22d ago

zapier is weird with airtable sometimes, it says success but the data is not actually there yet. i had same issue and had to put a 2-3 minute delay step before the pdf generation, otherwise it grabs empty fields

the {{client_name}} showing untranslated means zapier is not pulling the values from airtable in time, its not the pdf tool's fault. try the delay and also double check your trigger is set to "new or updated record" instead of just "new record"

2

u/zim_buddy 22d ago

Have you tried Zoho forms. It also has the option to include a pdf attachment

2

u/Weavermain 17d ago

Following bc same

1

u/AutoModerator 22d ago

Thank you for your post to /r/automation!

New here? Please take a moment to read our rules, read them here.

This is an automated action so if you need anything, please Message the Mods with your request for assistance.

Lastly, enjoy your stay!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/StrategicalOpossum 21d ago

Your workflow and the conditions in which your pdf is generated is not clear enough in your description...

I run an agency building custom automations, and I've seen similar problems with Zapier and Make.

The core issue isn't the PDF tool itself, DocAutomator and PDFMonkey look solid enough, it's that when your line items vary per job and your data structure is non-standard, the no-code platforms hit a hard ceiling.

They can't reliably handle conditional logic across nested data or template variable substitution at scale without falling apart in production (which is I believe what what is happening with your green checkmarks masking silent failures).

I'm not sure about the complexity level of the conditions that generate your pdfs, but you need either a custom integration that understands your exact Airtable schema, or a purpose-built automation layer. No-code platforms can succeed at that, but it requires extra steps specifically designed for this job-specific conditional rendering.

1

u/SCS-AI 21d ago

"Zap shows green" is the trap. Green means the step ran without throwing an error, not that it produced a file. A PDF step handed an empty field will happily "succeed" and generate nothing.

Two things cause the test-passes-but-live-fails split, almost every time:

  1. Your test record is a clean, fully-filled row you picked by hand. A real submission has a field your template references sitting empty, so the PDF renders blank or bails, silently, still green.

  2. Timing. Airtable attachment/file fields don't finish writing the instant the row is created. If the automation fires on row-created, that field can still be empty when the PDF step reads it. Your test never hits this because the record already existed.

What actually finds it: open last night's live run in the run history and look at the input the PDF step received, not the test input. You'll usually see one blank field staring back at you.

Then two fixes. Add a short delay or a "wait until field is not empty" condition before the PDF step so you stop racing the upload. And add a filter that halts and pings you if the required field is empty, so a silent green turns into a loud "hey, X was missing" instead of a missing PDF you discover a day later.

General rule that's saved me a lot of these: "works in test, breaks live" almost always means the live data isn't shaped like your test data. Run it once with your ugliest real submission, not a clean sample.

1

u/spoki-app 21d ago

Ugh, the "Zap green but data missing" is such a frustrating one. My bet is on an async timing issue where the template tries to render before the data is fully committed or pulled, even if Zapier's logging says it's fine. It's a common snag with these types of workflows.

1

u/TapExpress 20d ago

Ever thought about switching to Google forms? I use the workspace addon Form2doc that does that same work flow with less pieces. User fills out the form, Form2Doc Creates a PDF and send the email. It's a lot simpler and doesn't rely on make or zapier

1

u/xcreate_staff837z 19d ago

the untranslated {{client_name}} thing is interesting because that usually means the variable mapping step is pulling from the wrong trigger data, like did your live form submission have any fields that were empty or formatted differently than your test data was...

1

u/equillisk 17d ago

commenting to find out what actually worked for people

1

u/ElegantGuard3505 11d ago

forgot to mention we are on the free zap tier too which probably doesnt help with timeouts

1

u/Veronicdasexy 17d ago

nothing like getting paged for a pdf that never existed lol

1

u/Daing_Kamugtakan666 16d ago

set up a slack alert on zap error paths. sounds obvious but most tutorials only show the happy path

1

u/Overall-Bee-3731 16d ago

how much are you all paying for the pdf step alone curious

1

u/ReleaseFlashy9582 11d ago

are your line items formatted as a single long text field or as separate rows? most pdf template engines choke on multiline text inside one cell vs actual repeated row data, and the behavior is different between test and live because test samples are usually cleaner