PDF generation API: Automate Google Sheets to PDF Reports

TL;DR

This guide walks you through automating PDF report generation from Google Sheets using Make.com (a no-code automation platform) and APITemplate.io (a PDF generation API). Here’s what you need to know:

• What you’ll build: An automation that watches your Google Sheet, pulls new data, generates a professionally formatted PDF, and saves it to Google Drive (or emails it directly).
• Time required: About 30-45 minutes for initial setup.
• Cost: Free tiers available for all three tools. You can generate up to 50 PDFs/month on APITemplate.io’s free plan.
• Technical skill needed: None. This is a completely no-code solution.
• Best for: Sales reports, client summaries, invoices, project updates, inventory reports, and any recurring document you currently create manually from spreadsheet data.

Key takeaway: If you spend more than 10 minutes each week copying data from a spreadsheet into a report template, this automation will pay for itself immediately.

1. Why Use a PDF Generation API for Google Sheets?

Most businesses run on spreadsheets. Sales numbers, project timelines, inventory counts, expense logs-it all lives in Google Sheets. However, the problem starts when you need to share that data with someone who doesn’t want to stare at rows and columns.

Clients want polished reports. Executives want dashboards. Partners want summaries. Consequently, what do you do? You copy data from the spreadsheet, paste it into a Word doc or Google Doc, format it to look decent, export it as a PDF, and send it off. Then you do it again next week. And the week after that.

This manual process creates three problems:

First, it wastes time. A report that should take 2 minutes to generate ends up taking 60 minutes because of all the copying, formatting, and exporting. Multiply that by the number of reports you create each month, and you’re looking at hours of lost productivity.

Second, it introduces errors. Every time you manually copy data, there’s a chance you’ll grab the wrong cell, miss a row, or paste outdated numbers. I’ve seen companies send reports with last month’s figures more times than I can count.

Third, it doesn’t scale. One weekly report is manageable. However, ten weekly reports for ten different clients? That becomes a part-time job.

Fortunately, automation solves all three problems. When your spreadsheet updates, your PDF generates itself. As a result, the data is always current, the formatting is always consistent, and you don’t lift a finger.

What does “automated PDF generation” actually mean?

Automated PDF generation is the process of creating PDF documents programmatically based on data from another source-in this case, Google Sheets. Instead of manually formatting documents, you set up a system that:

1. Checks your spreadsheet at scheduled intervals for new data
2. Pulls that data when found
3. Inserts it into a pre-designed template
4. Renders a PDF file
5. Delivers it wherever you need it (email, cloud storage, Slack, etc.)

The entire process happens without human intervention. In other words, you set it up once, and it runs indefinitely.

2. Best Reports for PDF Generation API Automation

Not every document benefits from automation. However, if you’re creating the same type of document repeatedly with different data, automation is a game-changer.

Ideal report types for PDF generation API automation:

• Sales Reports: Weekly performance summaries, revenue breakdowns, team leaderboards
• Client Reports: Project progress updates, budget tracking, milestone summaries
• Financial Documents: Expense reports, invoices, budget variance reports
• Operations: Inventory alerts, fulfillment reports, receiving logs
• HR Documents: Attendance summaries, certification reports, performance reviews

What Makes a Report Good for PDF Generation API Automation?

Ask yourself: Do you create this report repeatedly? Does the format stay the same with only data changing? If yes, automation makes sense.

3. The Stack: Google Sheets, Make.com, and PDF Generation API

Google Sheets: Your Data Source

Google Sheets provides real-time collaboration, API access, and trigger capabilities for automated workflows.

Make.com: The Automation Engine

Make.com is a no-code automation platform with visual workflow builder, 1,500+ app integrations, conditional logic, and a free tier (1,000 ops/month).

APITemplate.io: The PDF Generation API Service

APITemplate.io is a cloud-based PDF generation API that converts HTML templates into PDF documents. Key features:

• HTML/CSS templates with Jinja2 syntax ({{ variable }})
• Direct Make.com integration
• Fast rendering (1-3 seconds)
• Free tier: 50 PDFs/month

How These Tools Connect

Specifically, here’s the data flow in plain terms:

1. Google Sheets triggers the workflow when data changes
2. Make.com pulls data and sends it to the PDF generation API
3. APITemplate.io renders the PDF and returns a download URL
4. HTTP module downloads the PDF file
5. Google Drive (or Gmail) stores/delivers the PDF

The beauty of this setup is that each tool does one thing well. Google Sheets manages data. Make.com handles automation logic. APITemplate.io renders PDFs. You don’t need to compromise on any part of the workflow.

4. How PDF Generation API Automation Works

Let me walk through a concrete example so you can visualize the entire process.

PDF Generation API Scenario: Weekly Sales Performance Report

Imagine you’re a sales manager. Every Friday, you need to send each salesperson a PDF summarizing their weekly performance. The data lives in a Google Sheet that looks like this:

report_date	salesperson_name	region	deals_closed	target_deals	revenue	target_revenue	status	email
2025-03-07	Sarah Sharma	Northeast	12	10	48500	40000	Exceeded	sarah@company.com
2025-03-07	Marcus Tiwari	Southwest	8	10	36200	40000	Below	marcus@company.com
2025-03-07	Aditya Trivedi	Midwest	10	10	41000	40000	On Target	adityatrivedi08082001@gmail.com

The automation flow:

1. Trigger: Make.com detects new rows in your Google Sheet
2. Extract: Pulls data from the row (name, region, revenue, etc.)
3. Generate: Sends data to PDF generation API with your template ID
4. Render: APITemplate.io creates the PDF in 1-2 seconds
5. Deliver: HTTP module downloads PDF, saves to Google Drive or emails it

Total time: ~10-15 seconds for multiple reports vs. 60+ minutes manually.

Available Triggers

Trigger Type	Best For
Watch Rows	Real-time processing (order confirmations, form submissions)
Schedule	Regular reports (weekly summaries, monthly statements)

5. Prerequisites for PDF Generation API Setup

Before you start building, first make sure you have the following:

Account Checklist

Service	What You Need	Free Tier?
Google Account	For Google Sheets and Drive access	Yes
Make.com	For automation workflows	Yes (1,000 ops/month)
APITemplate.io	For PDF generation	Yes (50 PDFs/month)

Prepare Your Google Sheet

Create a Google Sheet with clear column headers (e.g., salesperson_name, region, revenue, email). These headers map directly to your PDF template variables.

Your Google Sheet showing sample data.

Get Your API Keys

1. APITemplate.io: Go to apitemplate.io -> API Integration -> Copy your API key

Copy your API key from the API Integration page. Keep this secure-it authenticates all your PDF requests.

2. Make.com: Create account at make.com and verify email

The Make.com dashboard is where you’ll build your automation. Click ‘Create a new scenario’ to get started.

6. Creating Your PDF Generation API Template

The PDF generation API uses HTML/CSS templates with Jinja2 syntax for dynamic content.

Step 6.1: Create a New Template

1. Log in to APITemplate.io -> Manage Templates -> New PDF template
2. Name it (e.g., “Weekly Sales Report”) -> Click Create

Go to the manage templates tab and click on “New PDF Template”

Step 6.2: Design the Template with HTML and CSS

Click the HTML/Template tab and paste your HTML code. Here’s a simplified example:

<!DOCTYPE html>
<html>
<head>
  <meta charset="UTF-8">
  <title>Sales Report - {{ salesperson_name }}</title>
  <style>
    /* Reset and base styles */
    * {
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    }

    body {
      font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
      line-height: 1.6;
      color: #2d3748;
      padding: 40px;
      background: #ffffff;
    }

    /* Header section */
    .report-header {
      text-align: center;
      padding-bottom: 25px;
      border-bottom: 3px solid #3182ce;
      margin-bottom: 30px;
    }

    .report-header h1 {
      font-size: 26px;
      color: #1a365d;
      margin-bottom: 8px;
      font-weight: 600;
    }

    .report-header .subtitle {
      font-size: 14px;
      color: #718096;
    }

    /* Info cards row */
    .info-cards {
      display: flex;
      justify-content: space-between;
      gap: 20px;
      margin-bottom: 30px;
    }

    .info-card {
      flex: 1;
      background: #f7fafc;
      border-radius: 8px;
      padding: 20px;
      text-align: center;
      border: 1px solid #e2e8f0;
    }

    .info-card .label {
      font-size: 11px;
      text-transform: uppercase;
      letter-spacing: 0.5px;
      color: #718096;
      margin-bottom: 5px;
    }

    .info-card .value {
      font-size: 18px;
      font-weight: 600;
      color: #2d3748;
    }

    /* Section titles */
    .section-title {
      font-size: 16px;
      font-weight: 600;
      color: #1a365d;
      margin: 30px 0 15px 0;
      padding-bottom: 8px;
      border-bottom: 2px solid #e2e8f0;
    }

    /* Data table */
    .data-table {
      width: 100%;
      border-collapse: collapse;
      margin-bottom: 25px;
      font-size: 14px;
    }

    .data-table th {
      background: #2b6cb0;
      color: #ffffff;
      padding: 12px 15px;
      text-align: left;
      font-weight: 500;
      font-size: 12px;
      text-transform: uppercase;
      letter-spacing: 0.5px;
    }

    .data-table td {
      padding: 12px 15px;
      border-bottom: 1px solid #e2e8f0;
    }

    .data-table tr:nth-child(even) {
      background: #f7fafc;
    }

    .data-table tr:hover {
      background: #edf2f7;
    }

    /* Status badges */
    .status-badge {
      display: inline-block;
      padding: 4px 12px;
      border-radius: 20px;
      font-size: 11px;
      font-weight: 600;
      text-transform: uppercase;
    }

    .status-exceeded {
      background: #c6f6d5;
      color: #22543d;
    }

    .status-on-target {
      background: #bee3f8;
      color: #2a4365;
    }

    .status-below {
      background: #fed7d7;
      color: #742a2a;
    }

    /* Summary box */
    .summary-box {
      background: linear-gradient(135deg, #2b6cb0 0%, #4299e1 100%);
      color: #ffffff;
      padding: 25px;
      border-radius: 10px;
      margin-top: 30px;
    }

    .summary-box h3 {
      font-size: 14px;
      font-weight: 500;
      margin-bottom: 20px;
      opacity: 0.9;
    }

    .summary-stats {
      display: flex;
      justify-content: space-around;
      text-align: center;
    }

    .summary-stat .number {
      font-size: 28px;
      font-weight: 700;
    }

    .summary-stat .label {
      font-size: 11px;
      opacity: 0.85;
      margin-top: 5px;
    }

    /* Footer */
    .footer {
      margin-top: 40px;
      padding-top: 20px;
      border-top: 1px solid #e2e8f0;
      text-align: center;
      font-size: 11px;
      color: #a0aec0;
    }
  </style>
</head>
<body>
  <!-- Report Header -->
  <div class="report-header">
    <h1>Weekly Sales Performance Report</h1>
    <p class="subtitle">{{ region }} Region • Week Ending {{ report_date }}</p>
  </div>

  <!-- Quick Info Cards -->
  <div class="info-cards">
    <div class="info-card">
      <div class="label">Salesperson</div>
      <div class="value">{{ salesperson_name }}</div>
    </div>
    <div class="info-card">
      <div class="label">Region</div>
      <div class="value">{{ region }}</div>
    </div>
    <div class="info-card">
      <div class="label">Report Period</div>
      <div class="value">{{ report_date }}</div>
    </div>
  </div>

  <!-- Performance Summary Section -->
  <h2 class="section-title">Performance Summary</h2>

  <table class="data-table">
    <thead>
      <tr>
        <th>Metric</th>
        <th>Actual</th>
        <th>Target</th>
        <th>Variance</th>
        <th>Status</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td><strong>Deals Closed</strong></td>
        <td>{{ deals_closed }}</td>
        <td>{{ target_deals }}</td>
        <td>
          {% if deals_closed|int >= target_deals|int %}
            <span style="color: #22543d;">+{{ deals_closed|int - target_deals|int }}</span>
          {% else %}
            <span style="color: #742a2a;">{{ deals_closed|int - target_deals|int }}</span>
          {% endif %}
        </td>
        <td>
          {% if status == 'Exceeded' %}
            <span class="status-badge status-exceeded">Exceeded</span>
          {% elif status == 'On Target' %}
            <span class="status-badge status-on-target">On Target</span>
          {% else %}
            <span class="status-badge status-below">Below Target</span>
          {% endif %}
        </td>
      </tr>
      <tr>
        <td><strong>Revenue Generated</strong></td>
        <td>${{ "{:,}".format(revenue|int) }}</td>
        <td>${{ "{:,}".format(target_revenue|int) }}</td>
        <td>
          {% if revenue|int >= target_revenue|int %}
            <span style="color: #22543d;">+${{ "{:,}".format(revenue|int - target_revenue|int) }}</span>
          {% else %}
            <span style="color: #742a2a;">-${{ "{:,}".format(target_revenue|int - revenue|int) }}</span>
          {% endif %}
        </td>
        <td>
          {% if revenue|int >= target_revenue|int %}
            <span class="status-badge status-exceeded">Exceeded</span>
          {% else %}
            <span class="status-badge status-below">Below Target</span>
          {% endif %}
        </td>
      </tr>
    </tbody>
  </table>

  <!-- Achievement Summary -->
  <div class="summary-box">
    <h3>Period Achievement Summary</h3>
    <div class="summary-stats">
      <div class="summary-stat">
        <div class="number">{{ deals_closed }}</div>
        <div class="label">Deals Closed</div>
      </div>
      <div class="summary-stat">
        <div class="number">${{ "{:,}".format(revenue|int) }}</div>
        <div class="label">Total Revenue</div>
      </div>
      <div class="summary-stat">
        <div class="number">{{ ((revenue|int / target_revenue|int) * 100) | round }}%</div>
        <div class="label">Target Achievement</div>
      </div>
    </div>
  </div>

  <!-- Footer -->
  <div class="footer">
    Generated automatically on {{ generation_date }} - Powered by APITemplate.io
  </div>
</body>
</html>

Step 6.3: Jinja2 Template Syntax

Syntax	Purpose
{{ variable }}	Insert a value
{{ "{:,}".format(value|int) }}	Format numbers with commas
{% if condition %}	Conditional logic

Step 6.4: Preview and Test the Template

1. Click Data tab -> Enter test JSON -> Click Preview

The preview shows exactly how your PDF will look. Check that all variables populate correctly before moving on.

2. Click Save -> Note your Template ID from the Settings tab

Copy your template ID from the URL or Settings tab. You’ll paste this into Make.com in the next section.

7. Building the PDF Generation API Automation

Now that your template is ready, it’s time to connect everything in Make.com. This section walks you through building the complete PDF generation API workflow.

Step 7.1: Create a New Scenario

Log in to Make.com → Click Create a new scenario

The scenario canvas is where you’ll build your automation. Click on the circle+ to create a module.

Step 7.2: Add the Google Sheets Trigger

1. Click the empty circle -> Search “Google Sheets” -> Select Watch Rows
2. Connect your Google account and configure:

Search for ‘Google Sheets’ and select it to add the trigger module.

4. Click Add next to Connection to link your Google account
5. Follow the OAuth prompts to authorize Make.com

Once connected, configure the trigger as follows:

Field	Value
Connection	Your Google account
Search Method	Search by path
Drive	My Drive
Spreadsheet ID	Select your spreadsheet from the dropdown
Sheet Name	Select the specific sheet tab (e.g., Sheet1)
Table contains headers	Yes
Row with headers	A1:Z1
Limit	10 (or however many rows to process per run)

6. Click Save to save the module

Step 7.3: Add the PDF Generation API Module

1. Click + -> Search “APITemplate” -> Select Create a PDF

Click the plus icon to add another module, then search for APITemplate.io.

2. Enter your API key and select Dynamic data (JSON Payload)
3. Select your template from the Template ID dropdown
4. Map your data in the Dynamic Data field:

Map each template variable to the corresponding Google Sheets column. The numbers (like 1.revenue) refer to the module number.

7. Click Save to save the module

Step 7.4: Add HTTP Module to Download the PDF

The APITemplate.io module returns a download URL, not the actual file. Therefore, we need an HTTP module to fetch the PDF before saving it to Google Drive.

1. Click the + after the APITemplate.io module
2. Search for HTTP and select HTTP – Download a File
3. Configure it:

Field	Value
Authentication type	No authentication
URL	Click Download URL from APITemplate.io in the left panel

4. Click Save

Configure the HTTP module with Auth type, URL, etc.

Step 7.5: Save PDF Generation API Output to Google Drive

1. Click + -> Search Google Drive -> Select Upload a File
2. Connect your Google account

⚠️ Gmail Users: If you see “restricted scopes” error, you need a custom OAuth client. Go to Google Cloud Console -> Create project -> Enable Google Drive API -> Create OAuth credentials -> Add redirect URIs for Make.com -> Use Client ID/Secret in Make.com’s advanced settings.

Completing the Google Drive Module Setup

After completing the OAuth setup, continue with the Google Drive module configuration.

First, create a folder in Google Drive:

1. Open Google Drive
2. Click New -> New folder
3. Name it something like “Weekly Reports Output”.
4. Click Create

This folder will store all your generated PDF reports.

Then, configure the Google Drive module:

5. Connect using your custom OAuth client (follow Step E above if needed)
6. Next, configure the upload:

Field	Value
Connection	Your Google Restricted connection
Enter a Folder ID	Select from the list
New Drive Location	My Drive
New Folder Location	Select the folder you created (e.g., “Weekly Reports Output”)
File	Select Map option
File Name	Click salesperson_name (B) from Google Sheets, then type _report.pdf
Data	Click Data from the HTTP module in the left panel

Configure the Google drive module.

Finally, build the File Name dynamically:

1. First, click inside the File Name field
2. From the left panel, click salesperson_name (B) under Google Sheets
3. Type _report.pdf after it

As a result, this creates filenames like Aditya Trivedi_report.pdf for each salesperson.

4. Click Save to complete the module

Step 7.6: Test Your PDF Generation API Scenario

Before activating, first test with real data:

1. Add a new row to your Google Sheet with sample data
2. Click Run once in Make.com (bottom left of the canvas)
3. Watch the scenario execute

Green checkmarks indicate each module completed successfully. Click any module to inspect the data that flowed through it.

4. Check your Google Drive folder-the PDF should be there

Your automated PDF now appears in Google Drive. Open it to verify the data populated correctly.

Step 7.7: Activate Your PDF Generation API Workflow

Click Scheduling -> Toggle ON -> Set interval (e.g., every 15 minutes)

Choose how often Make.com checks for new rows in your spreadsheet.

Click Save (disk icon), your automation is now live.

8. Auto-Sending PDFs via Email

Most reports need to reach someone’s inbox, not just sit in a folder. Therefore, let’s add email delivery.

Step 8.1: Add an Email Module

First, after the Google Drive upload (or instead of it, if you don’t need Drive storage):

1. Add a Gmail -> Send an Email module (or use Email for non-Gmail)
2. Connect your Gmail account
3. Configure the email:

Field	Value
Connection	Your Gmail connection
To (Recipient email address 1)	Click email (I) from Google Sheets
Subject	Click salesperson_name (B) then type 's Weekly Sales Report
Body type	Raw HTML
Content	See Step 8.2 below

4. Configure the attachment:

Field	Value
Attachments	Click Add attachment
File	Select Map option
File name	Click File name from HTTP module
Data	Click Data from HTTP module

5. Click Save

Step 8.2: Write a Professional Email Body for PDF Generation API Reports

Next, in the Content field, type HTML and insert variables by clicking labels from the left panel:

1. Click inside the Content field
2. Type your HTML, and when you need a variable, click it from the Google Sheets section in the left panel

Example email body:

Type this, clicking the highlighted variables from the left panel:

<p>Hi [click salesperson_name (B)],</p>

<p>Please find attached your weekly sales performance report for the week ending [click report_date (A)].</p>

<p><strong>Quick Summary:</strong></p>
<ul>
  <li>Deals Closed: [click deals_closed (D)]</li>
  <li>Revenue Generated: $[click revenue (F)]</li>
  <li>Status: [click status (H)]</li>
</ul>

<p>The full detailed report is attached as a PDF.</p>

<p>Best regards,<br>
Sales Operations<br>
<em>This is an automated message</em></p>

How to insert variables:

• Type the static text normally (e.g., <p>Hi)
• Click the variable from the left panel (e.g., salesperson_name (B))
• Continue typing the rest (e.g., ,</p>)

The variables will appear as colored chips in the Content field.

Now run the automation again and check the recipient email inbox.

Recipient email inbox received the mail showing proper details including pdf report.

9. Troubleshooting PDF Generation API Issues

Even well-designed automations can hit snags. Therefore, below is how to diagnose and fix the most common problems.

Problem	Cause	Solution
Connection lost	OAuth tokens expired	Go to Connections -> Reauthorize
Template not found	Wrong template ID	Copy fresh ID from APITemplate.io
Missing data in PDF	Variable name mismatch	Ensure exact case-sensitive match
No PDFs created	No new data or filter blocking	Check execution history, verify new rows exist
Duplicate PDFs	No deduplication	Add “Processed” column, filter for empty

10. Alternatives: Zapier, n8n, Direct PDF Generation API

Platform	Best For	Pricing
Make.com	Visual automations with logic	Free + $9/mo
Zapier	Simple linear workflows	Free + $19.99/mo
n8n	Self-hosted, privacy-focused	Free (self-hosted)
Direct API	Developers, custom apps	API costs only

APITemplate.io integrates natively with all these platforms. For a detailed Make.com guide, see How to Generate PDFs in Make.com with APITemplate.io.

11. Scaling Your PDF Generation API Workflow

Expand your automation:

• More templates: Sales reports, invoices, project updates, different brands
• More triggers: Form submissions, CRM updates, e-commerce orders
• Error handling: Add Slack/email alerts for failures
• Batch processing: For high volume, use scheduled runs instead of instant triggers

12. Summary

In conclusion, automating PDF reports from Google Sheets eliminates the tedious, error-prone work of manual document creation. With Make.com orchestrating the workflow and the PDF generation API handling document creation, you can turn any spreadsheet data into professional documents-automatically.

What we covered:

1. Why automation saves time and reduces errors
2. Which report types benefit most from this approach
3. How Google Sheets, Make.com, HTTP, APITemplate.io, and Google Drive work together
4. Step-by-step template creation in APITemplate.io
5. Building the complete automation in Make.com
6. Advanced feature: Email delivery
7. Troubleshooting common issues
8. Alternative tools for different needs

Your next action: Create your first template in APITemplate.io using the code provided in Section 6, then connect it to Make.com following Section 7. Most people have their first automated PDF generating within an hour.

Additional Resources

• APITemplate.io API Reference – Full API reference and template guides
• APITemplate.io FAQs – Common questions and integrations
• Make.com Help Center – Tutorials and module documentation
• Jinja2 Template Designer Documentation – Advanced templating syntax

Further reading:

• Top PDF Generation APIs for 2025
• How Low/No-Code Solutions Are Transforming Document Generation

Ready to Automate Your PDF Reports?

Stop wasting hours on manual report creation. Start generating professional PDFs from your Google Sheets data in minutes.

Sign Up for APITemplate.io – Free – Create up to 50 PDFs per month at no cost.

This guide was created to help businesses automate their document workflows. If you have questions or want to share what you’ve built, reach out to the APITemplate.io team.