How to generate one PDF document per Google Sheets row and attach all PDFs to one email?

:bullseye: What is your goal?

I am building a Make scenario for a local delivery service.

Every night, the scenario should find all paid delivery orders scheduled for the next day in Google Sheets Orders_Log.

For each order, I need to generate one separate PDF delivery document.

If there are 5 delivery orders, the final internal email should contain 5 separate PDF attachments.

Relevant data comes from Google Sheets:

order_number
delivery_date
delivery_window
delivery_town
accommodation_name
full_delivery_address
customer_whatsapp
delivery_notes
customer_email
customer_phone
total_price
products / order items if available

Important operational rule:

The DDT / delivery document must use WineHoliday Delivery Details as source of truth, not Shopify shipping address.

The goods departure information should be:

Enoteca Assetati
Via Cavour 83/A
14100 Asti (AT), Italy
Time: 09:30

Goal flow:

Scheduler
→ Google Sheets Search Rows
→ filter delivery_date = tomorrow and financial_status = paid
→ for each row generate one PDF
→ collect all PDFs
→ send one internal email with all PDFs attached

Questions:

What is the best Make structure for generating one PDF per Google Sheets row?
Should I use Google Docs template → Create document from template → Export as PDF?
How do I generate multiple PDFs and attach them all to a single email?
Do I need an Array aggregator for attachments?
What is the correct way to avoid sending one email per order?
Is there a recommended module sequence for this?

Expected result:

One email sent internally every night.

Subject:
WineHoliday DDT + Route Briefing — DD/MM/YYYY

Attachments:
DDT_Order_1076.pdf
DDT_Order_1077.pdf
DDT_Order_1078.pdf

The email body should also include a summary of all orders and a Google Maps route link.

:thinking: What is the problem & what have you tried?

I have not built the PDF part yet.

I already have a working scenario that reads paid delivery orders from Google Sheets Orders_Log and sends an internal email / WhatsApp briefing.

Now I need to add the PDF generation part.

The main question is the correct architecture in Make.

I want to avoid sending one email per order.

I need one final internal email with:

  • one PDF attachment per delivery order
  • all PDFs attached together
  • a summary of all orders in the email body
  • a Google Maps route link in the same email

I am not sure whether the correct structure should be:

Option A:
Google Sheets Search Rows
→ Iterator
→ Google Docs Create document from template
→ Export as PDF
→ Array aggregator for attachments
→ Send one email with all PDFs attached

or Option B:
Google Sheets Search Rows
→ Iterator
→ Create PDF
→ Store files temporarily
→ Aggregate files
→ Send one final email

Questions:

  1. What is the recommended module sequence in Make?
  2. Should I use Google Docs template or another PDF generation module?
  3. How do I attach multiple generated PDFs to one single email?
  4. What should the Array aggregator aggregate: files, binary data, file names, or attachments?
  5. How do I avoid the Email module sending one email per Google Sheets row?
  6. Should the email module be placed after the Array aggregator only?
  7. Is there a better way to generate one PDF per row and attach all of them to one email?

I need the architecture before building it.

:clipboard: Error messages or input/output bundles

No error yet. I am trying to design the correct Make architecture before building the PDF generation.

Option A is the right shape, with one simplification: Google Sheets → Search Rows already outputs one bundle per row, so you don’t need the Iterator. You can go straight from Search Rows into the document module.

Sequence:

Scheduler → Google Sheets Search Rows (filter: delivery_date = tomorrow, financial_status = paid) → Google Docs Create a document from template → Google Drive Download a file → Array aggregator → Email Send.

A few answers to your specific questions:

The Array aggregator’s source module must be the Download a file step, not Search Rows. That’s what makes it collect the PDFs.
Aggregate the whole file bundle, then map Array[] into the email’s Attachments field. Don’t try to build the array manually.
The email only sends once because it sits after the aggregator — anything before it runs per bundle.
Google Docs templates are fine for a DDT since the layout is fixed. If your orders have a variable number of line items, Docs gets painful fast — that’s the usual reason people move to a dedicated PDF module.

For the route link, build it in a separate branch off the aggregator so it doesn’t multiply per order.

Absolutely not mate. The source module should 100% be the search rows module and not the download a file module.

You always aggregate a module the produces extra bundles.

You want one PDF per row and one email at the end. The email module has to sit after the aggregator, or it fires once per order.

Concrete change: Search Rows, Iterator, create the PDF inside the iteration, then an Array Aggregator on the file binaries only. Map the email module to that one array. If you aggregate the Google Doc IDs instead of the PDF files, the email goes out with nothing attached.

Be careful with email attachment size limits, especially if you might have more than 5 PDFs per email. I would recommend at least compressing them into a ZIP before sending, using Makes Archive module.

I stand with @Stoyan_Vatov on this