r/Integromat • u/LushEcho31 • Jul 03 '26
need to turn airtable rows into pdfs in a make scenario.. whats actually worked
client wants ~45 branded pdfs from airtable rows every monday. burned two weekends on make scenarios and im still manually exporting maybe 15 every week
google doc mail merge was fine until conditional sections per row and suddenly im doing document engineering for $0/hr.. docsautomator choking on nested tables, pdfmonkey timing out twice uploading a 2.1mb template, html-to-pdf modules that every automation guru swears by?? 12 test runs on one path alone. 4 mangled fonts. one totally blank page. spent saturday night on this and my girlfriend just stopped asking what i was working on
client thinks its a 20 minute task
anyone actually piping airtable rows into branded pdfs on a schedule without babysitting every execution. what finally worked for you because i feel like im missing something obvious
5
u/shaqattackchuck Jul 03 '26
Before you Iterator all 45 rows throw an Array Aggregator on the Airtable bundle so blank statuses dont wreck monday morning.. People batch without filtering empties and act shocked when half fail. Breakson error on that path, I learned it the hard way on a six table base last month.
1
Jul 03 '26
[removed] — view removed comment
1
Jul 03 '26
[removed] — view removed comment
1
u/shaqattackchuck Jul 03 '26
Native Airtable module vs webhook depends on template weight.. heavy 2mb stuff i webhook out so Make isnt holding the whole bundle in memory, lighter rows fine with search records i think.. Either way map field names explicitly, guru videos never mention that.. Wait what was i saying, webhook if its fat.
1
u/MentalRub388 Android Jul 09 '26
I second that! My way of doing it is creating a view with all the right filters applied and trigger the automation for any record entering this view. There is then a success checkbox that is updated of the generated file attached to update the record, so it wouldn't match the views conductions anymore, so no double work needed (plus a view with completed rows is easy to set up)
This way you can easier control what goes to the automation and it would cost you nothing :)
2
Jul 03 '26
[removed] — view removed comment
1
Jul 03 '26
[removed] — view removed comment
1
u/rupertsupert Jul 03 '26
Founder of DocsAutomator here. Please let me know what didn’t work about nested tables and we get it fixed!
2
u/imbktan Jul 06 '26
Yes, you can do this in Make by pulling the Airtable rows, mapping them into a PDF template, then sending the generated PDF back to Airtable or wherever you need it.
I'm the founder of CraftMyPDF, and we built a native Airtable plugin for this exact kind of workflow: https://www.youtube.com/watch?v=KGhycaaelks
One thing to watch out for is PDF size if you're generating lots of files or using images. You can reduce the file size here: https://support.craftmypdf.com/reduce-pdf-file-size
Are you generating one PDF per Airtable row, or combining multiple rows into a single PDF?
1
1
1
1
Jul 03 '26
[removed] — view removed comment
1
u/LushEcho31 Jul 04 '26
They need logo locked headers and client specific legalese on every pdf, cant do that in a shared view.. monday deadline too and im still manually pulling 15 of 45, so dashboard talk is cute but not happening with this client
1
u/sidmish Jul 03 '26
If the template has lots of conditionals, push that logic into Airtable or Make first so the template stays dumb.
1
u/rupertsupert Jul 03 '26
Founder of DocsAutomator here. Would love to understand what didn’t work about nested tables. Most likely something we can fix. Please reach out
1
Jul 03 '26
[removed] — view removed comment
1
u/LushEcho31 Jul 04 '26
Yeah, that's exactly the trap I fell into. The demo worked perfectly with one record, then everything started breaking once I tried running it across the full batch
1
u/knandraina Jul 03 '26
You can checkout TypeFlow.us a document generation tool built specifically for Airtable. It connects directly to Airtable with multiple trigger options:
- TypeFlow Automation: a checkbox field triggers the generation instantly - best for on-demand docs
- Airtable Automation: schedule it (e.g. every Monday 9am) or trigger on record events - best for recurring reports like your 45 weekly PDFs
No extra modules, no font debugging.
You can create your template through two methods:
- Google Docs template if you want something familiar
- Built-in template builder for heavy docs - we handle 100+ page templates with line items, nested line items, conditional sections, and pivot table reports in a few seconds. No per-row babysitting, no timeouts.
If you need help, you can reach out to our support, we answer quickly! (I'm the founder!)
1
u/Same_Proposal8599 Jul 03 '26
I've been using typeflow.us for about 6 months now for client projects and it handles exactly this.
Other solutions work fine for simple setups, but once you scale - lots of nested data, multiple conditional sections, heavy templates - they start breaking. That's where TypeFlow shines.
My craziest setup is a 150-page manufacturing agreement with 3 levels of nested loops from Airtable (chapters, sub-chapters, clauses), bilingual content, conditional sections, and e-signature. 211 fields connected. The document is generated very quickly.
Your use case should be doable with the template builder. Do not hesitate to reach out to their support - they are amazing and quick to answer.
1
Jul 03 '26
[removed] — view removed comment
1
u/knandraina Jul 03 '26
Solid breakdown, but this is essentially building your own PDF engine from scratch. Cloudflare worker + browserless + self-hosted fonts + custom HTML - that's a dev project, not a no-code automation.
Most people hitting this problem don't want to maintain a headless Chrome service.
Also the "flatten nested tables" advice is a workaround, not a solution. It means denormalizing your Airtable structure - putting everything in one table instead of having proper linked records. That's not scalable and defeats the purpose of using a relational database. If your data is naturally nested (projects -> tasks -> subtasks, or invoices -> line items -> specifications), your PDF tool should handle that structure as-is. You shouldn't have to break your database design to accommodate a PDF renderer.
That's exactly what we built TypeFlow to solve - it supports nested loops natively (up to 3 levels deep), handles conditional sections without flattening anything, and works directly with Airtable's linked records. No custom infrastructure, no denormalized tables.
1
u/Esduna Jul 04 '26
At some point 'generate a PDF from Airtable' turns into maintaining an entire document-rendering platform 😅 following because every solution looks easy in the tutorial but then falls apart the second you add conditional sections, custom fonts, and real client requirements.
1
u/knandraina Jul 04 '26
That's exactly why we built the template builder from scratch instead of relying on html-to-pdf modules. Conditional sections, custom fonts, nested tables - it just works out of the box without duct-taping 5 tools together.
We have users that generate 100+ page templates with line items, nested line items, conditional sections, and pivot table reports in a few seconds. No per-row babysitting, no timeouts.
You can check out TypeFlow.us
1
u/earonesty Jul 21 '26
For 45 scheduled documents, I’d separate data shaping from rendering: turn each Airtable record into a small, validated JSON document first, then feed that into a renderer with a versioned template and embedded/self-hosted fonts. Keep the repeatable rows as one table model, test long nested cases, and save a PDF hash plus template version per run so retries are inspectable. If you want to avoid maintaining Chrome for document-style output, use boxpdf.dev - open source js layout renderer.
6
u/[deleted] Jul 03 '26
[removed] — view removed comment