Need Make.com Expert to Automate PDF Invoice Emailing from computer desktop or can be from Google Sheets & Google Drive

Hire a Pro Hire Help
1

I am looking for a Make.com expert to build a simple invoice emailing automation for my commercial janitorial business. This is NOT an invoice generation project.

We already create all invoices manually as PDF files.

****SYSTEMS: from computer desktop or Google Sheets or Google Drive or Gmail Workflow:

  1. Read client information from Google Sheets.
  2. Identify which clients should receive invoices during the mid-month or end-of-month billing cycle.
  3. Locate the corresponding PDF invoice stored in computer desktop or apple iCloud or Google Drive.
  4. Email the correct PDF invoice to the correct client with the email template and email Invoice file # and name on the subject line
  5. Update computer desktop or Google Sheets to indicate the invoice was sent successfully.
  6. Allow us to manually resend an individual invoice if needed.

We currently have approximately 80 recurring clients.

Please include:

  • Estimated fixed price
  • Estimated completion time
  • Your experience with similar Make.com automations
  • Whether you’ll provide documentation or a walkthrough after completion.
4 Likes
2

Hi Andrew,

The first thing I’d verify before quoting this is the file source. Make cannot read PDFs directly from a desktop folder or iCloud. They need to live in, or sync reliably to, Google Drive or another cloud source Make can access.

With 80 recurring clients, sending the email is the easy part. The real risk is a successful run attaching the wrong PDF or sending the same invoice twice. That comes down to whether the Sheet and each filename share a stable client or invoice ID.

Could you share one anonymized PDF filename and the relevant Sheet column names? Also, is the mid-month or end-of-month cycle already marked in the Sheet?

That would be enough to tell whether your current setup is safe to automate and give you an accurate fixed scope, price and timeline.

Zay

3

Hi Andrew, quick flag before anyone quotes this: Make.com can’t read files off a local desktop or iCloud, it needs a cloud source. So this only works if those PDFs live in (or sync to) Google Drive. Worth locking that down first since “desktop” isn’t buildable as-is.

Three things I need to quote accurately:

  1. A few real filenames from your current PDF invoices, is there a client ID/number in the name I can match against your Sheet, or are they named inconsistently?
  2. Is the mid-month/end-of-month trigger a fixed schedule, or a status column in the Sheet marking who’s due?
  3. For manual resend, do you need a button/interface per client, or is rerunning the scenario filtered to one client fine?

Built similar PDF-to-email flows at this client volume before, happy to share specifics on a call. Feel free to email me directly at [email protected] if you’d rather take this offline.

4

Hi Andrew,

I’d be happy to help with this.

From your description, this is less about invoice creation and more about building a reliable invoice delivery workflow.

My approach would be to:

• Read the billing schedule and client details from Google Sheets.

• Identify which invoices should be sent for the current billing cycle.

• Locate the matching PDF from your chosen storage location (Google Drive would be my recommendation for reliability, though we can discuss other options).

• Send each invoice using your email template with the invoice number and client name in the subject line.

• Log successful deliveries back to Google Sheets.

• Include a simple way to manually resend an individual invoice whenever needed.

• Add error handling and logging so failed sends can be identified easily.

Estimated completion:

1 to 2 days depending on where the PDF files are stored.

Estimated fixed price:

Approximately $120 to $180 after reviewing your current setup.

I’ve built similar Make.com workflows involving Google Sheets, Gmail, APIs, document handling, business process automation, and reliable workflow management.

I’ll also provide documentation together with a walkthrough so your team can confidently use and maintain the workflow.

I’ve sent you a DM with my portfolio, relevant automation examples, and contact details. I’d be happy to discuss your current setup and answer any questions.

Best,

Folafoluwa

5

Hi Andrew — I can take this as a fixed-scope paid pilot.

For CNY 699, I can deliver a bounded first version for a redacted 5-client sample: Google Sheets schedule → locate the matching PDF in Google Drive → Gmail send → log the result → manual resend path. This includes a test checklist, setup/usage notes, and one minor in-scope revision. With complete inputs, delivery is within 6 hours.

This pilot excludes desktop/iCloud access and production credentials. If you need the full 80-client production rollout, I’ll quote that separately after the pilot validates filename matching and billing-cycle rules. Formal work starts only after scope confirmation and actual payment.

If the task is still open, please send a redacted Sheet/PDF naming sample and your deadline.

6

Hello @Andrew_Makar, I’m Taiwo, a Make.com expert running Pathfinder Automation Solutions, a team of Make specialists. I build exactly this kind of workflow regularly: Sheets records, Drive file matching, templated Gmail sends, and status write-back.

One honest note: Make can’t reliably pull files from a local desktop or iCloud, those aren’t cloud storage it connects to natively. Google Drive is the right home for the PDFs. If yours currently live on the desktop, syncing that folder to Drive solves it cleanly and everything else works exactly as you described.

Fixed price: $500
Completion time: 5-7 days
Documentation and walkthrough: Both, plus 14 days of support after delivery.

Let’s connect:
Website: https://www.pathfinderautomationsolutions.com
Upwork: https://www.upwork.com/freelancers/\~01446d60f782215efa
Book a call: Calendly

Taiwo

1 Like
7

Andrew, this is Misha, an n8n and AI automation developer. I’d build this as a Make.com scenario that reads your Google Sheet to identify mid-month or end-of-month billing clients, picks the correct PDF from a Google Drive folder by matching invoice file names, and emails the invoice with the proper subject line and template. The system would update the sheet to show each invoice was sent and include a manual resend button via a simple webhook for individual clients. I’ve done similar invoice routing and CRM automations for service businesses, so I know the need for reliable retry logic and clear status tracking. I’ll provide a recorded walkthrough and written documentation so your team can manage it easily. Fixed price is $400, completion within four days from access to your systems. Portfolio: https://mikedevai.netlify.app/ | Telegram: Telegram: Contact @hely_chatbots | WhatsApp: +375293761570

8

Hi Andrew, Before I say anything, here are a few automation systems I’ve built:

https://drive.google.com/file/d/1f7t9kA5yBW0Egc2TBkX7qinyRqOyNo9dbSbJIVZbpnpQEACLV/view?usp=sharing

Your workflow is exactly the kind of operational automation Make.com is built for, and I can help you make it reliable and easy to manage.

Here’s how I’d build it:

:white_check_mark: Read client details and billing schedules from Google Sheets.
:white_check_mark: Automatically identify which clients should receive invoices during the current billing cycle (mid-month or end-of-month).
:white_check_mark: Retrieve the correct PDF invoice from Google Drive (or another supported storage location depending on your setup).
:white_check_mark: Send a personalized Gmail email with the correct invoice attached, using the invoice number and client name in the subject line.
:white_check_mark: Update your Google Sheet with a timestamp and “Sent” status after successful delivery.
:white_check_mark: Build a manual resend workflow so you can resend any individual invoice without affecting the rest of the automation.

I’ll also include proper error handling, logging, and notifications so failed emails or missing invoices can be identified and resolved quickly.

Fixed Price: $450

Timeline: 5-7 days, including testing and final validation.

After delivery, I’ll provide complete documentation along with a walkthrough of the scenario so you know exactly how everything works and can make simple updates yourself in the future I’d be happy to discuss your current invoice storage structure (Google Drive, Desktop, or iCloud) and recommend the cleanest implementation.

Looking forward to working with you @Andrew_Makar

1 Like
9

Hi Andrew,

Before talking about price, there is one thing that determines the whole design:
where the PDFs live. If they are in Google Drive (or can be synced there), this
is a clean Make build. If they only exist on a desktop, I would add the simplest
possible sync layer rather than redesign the workflow — Make cannot reach a local
folder by itself. The fixed price below assumes Google Drive is the document
source. Assuming the filenames contain a stable client or invoice identifier,
I see no technical blockers.

The real challenge here is not sending emails — it is making the process reliable
enough that every client receives exactly the right invoice, exactly once.
Automation should remove manual work, not introduce new ways to send the wrong
invoice. This is exactly the kind of workflow I have spent the last 20 years
building — billing and ERP systems, now with Make/AI automation on top.

My approach: your Google Sheet stays the source of truth (client, billing cycle,
email, invoice file pattern). A scheduled scenario picks the clients due, locates
each PDF in Drive, sends a formatted email from your address, and updates the
tracking tab. Any exception — missing PDF, duplicate filename, bounced email —
is surfaced on an exception list immediately instead of disappearing silently.
The scenario is safe to re-run: if it runs twice, nobody gets invoiced twice.
A checkbox in the sheet re-sends any single invoice on demand.

Fixed price: USD 400
Delivery: 3-4 days
Includes: written documentation + 30 days of post-delivery fixes

I work async and in writing, so you get a clear record of how everything works.

Recent work:

  • AI quoting agent for a Swiss trades company (request parsing → catalog
    matching → PDF quote).
  • Field-reporting system with automated billing exports for a construction
    contractor (case: Claude Artifact ).

If you paste one example row from your sheet and one real PDF filename (redact
anything private), I will tell you whether I would automate it as-is or recommend
one small change first.

Alexander

10

Hi Andrew,

I can deliver this as a $499 fixed-scope Make build in 3 business days once a redacted sample is available.

I would use Google Drive as the PDF source because Make cannot reliably read a local Desktop or iCloud folder directly. The build would include:

  • Google Sheets filtering for the mid-month and end-of-month billing groups
  • Exact client or invoice ID matching to one PDF in Google Drive
  • A hard stop when zero or multiple PDFs match
  • Gmail delivery with the invoice number and client name in the subject
  • Sent timestamp, Gmail message ID, and error status written back to the Sheet
  • Duplicate-send protection
  • Manual resend through a controlled Resend flag in the Sheet

I would validate five redacted clients first, then enable the full group of about 80 only after the match and duplicate tests pass.

Relevant experience: TinyOps builds and validates workflow automations involving structured records, document matching, email delivery, reconciliation logs, and operator handoff. I have not deployed this exact setup for an 80-client janitorial company, so I will not present it as an identical reference.

The fixed price includes a written runbook, a recorded walkthrough, one revision, and seven days of defect support. Make and Google subscription costs are excluded.

To confirm the scope, send one anonymized invoice filename, the Sheet column headers, and whether the billing cycle is a Sheet value or a fixed calendar rule. No login credentials are needed to quote.

11

Hi Andrew — quick follow-up. Instead of adding more promises to the thread, I went ahead and built the core of this on mock data: 3 fake clients in a sheet, 3 PDF invoices in Drive, one tracking tab.

  • the invoice is found by invoice number, never “first file that matches”
  • missing PDF → the row is flagged in the tracking tab, nothing is skipped silently
  • sent / pending / missing_pdf visible at a glance, and the scenario is safe to re-run

Paste one redacted row from your sheet and one real PDF filename — I’ll run them through this build and reply with a screenshot of the result. The $400 fixed quote stands: 3-4 days, written docs + 30 days of post-delivery fixes.

12

Hi Andrew,

The thread has already settled the big design questions, so I’ll skip repeating them. Instead of describing what I would build, I built your whole spec this weekend and ran it live: both billing cycles, the sheet updates, the run summary email, and the manual re-send, tested with real sends against a fixture set of eight clients that includes a missing invoice, a duplicate filename, an inactive client, and one already sent this period. Every client ends the run with a visible status in the sheet, and the re-send clears its checkbox before it does anything, so a second poll can’t fire it twice.

One technical finding worth having no matter who you hire: the standard Drive “Get a file” module currently fails at the point where it actually downloads the file for attaching, because under the hood it calls a retired Google endpoint. Reading the filename works fine, so the failure only appears when a real email tries to carry the PDF. The newer “Download a file” module is the one that works. Anyone building this will hit that, and it took me a few hours to pin down.

Your four questions:

Price: $500 fixed, documentation and a walkthrough included. Time: 3 business days from a redacted sample of your sheet and a few real filenames. Experience: I build Make automations for small service businesses, most recently a five-scenario registration pipeline connecting a booking system, a CRM and Google Sheets. Documentation: yes, written for whoever runs it after me.

If you’d like proof before deciding anything, post or DM one redacted row and one real PDF filename, and I’ll run them through the finished build and send back the run log plus the email exactly as your client would receive it.

Christo

13

Andrew, before suggesting a fixed scope, I would need to confirm three implementation details:

  1. Can the invoice PDFs live in Google Drive, or be synced there reliably? Make will not safely use a random local Desktop/iCloud folder as the source of truth.

  2. Do your PDF filenames contain a stable client ID, invoice number, or billing-cycle marker that also exists in the Google Sheet?

  3. For manual resend, is a resend_flag column in Google Sheets acceptable, or do you need a separate button/interface?

If those three are clean, the Make scenario becomes much safer to scope: Sheets filtering, Drive file matching, Gmail sending, sent/error writeback, duplicate-send protection, and a manual resend path.

14

Andrew — I’d design this around preventing misdelivery rather than merely sending email. I propose a $395 fixed build delivered in two business days after receiving a redacted sample. Google Sheets remains the source of truth, PDFs sync to Google Drive, and every send requires one exact invoice-ID match. Zero or multiple matches stop in an exception queue. A successful send writes the timestamp and Gmail message ID back to the Sheet, while an explicit Resend flag handles one invoice without rerunning the full cycle.

I’ll test five redacted clients before enabling the roughly 80-client run, then provide a written runbook, recorded walkthrough, one in-scope revision, and seven days of defect support. My relevant capability is test-driven automation across structured records, document matching, email delivery, duplicate protection, and operator handoff; I do not have an identical janitorial-company case study and will not imply one.

To confirm scope, please share one anonymized filename, the Sheet column headers, and whether billing cycle is a Sheet value or a calendar rule. Terms are 50% to schedule and the balance after acceptance.

15

Hi Andrew,

There are already serious offers in this thread, so I’ll keep this short and just hand you something you can check without doing any work at all — no redacted rows to paste, no screenshots to wait for.

Nothing to install. Set the date to 31 July and press Run. Twelve clients on your two billing cycles, a deliberately messy Drive folder, the whole run in front of you.

The case worth thirty seconds is one I haven’t seen addressed yet in this thread. Matching on the invoice number instead of “first file that matches” is necessary, but it isn’t sufficient — because sometimes more than one file legitimately contains the number. The demo folder holds INV-2026-0417.pdf, INV-2026-0417 (1).pdf and INV-2026-0417-DRAFT.pdf. Mine treats the number as a whole token, so it rules out the DRAFT cleanly, and then refuses to choose between the original and the (1) duplicate — it holds that row back rather than picking one and hoping. Two other clients have no PDF at all; those are reported, not skipped quietly. The remaining five send.

Then press Run a second time and watch nothing happen. Every send is keyed on client + invoice number and written back before the next row is processed, so a re-run after a partial failure can’t put a second copy in front of eighty clients.

One correction on the brief, offered up front rather than after you’ve paid: files sitting on your desktop or in iCloud Drive cannot be reached by a cloud automation — there is no API for them. The PDFs have to live in Google Drive. That’s a one-time folder move, not extra build work, but it has to happen before anything runs.

USD 650 fixed, live within 7 working days of getting access to the sheet and folder. That covers both billing cycles, exact matching with hold-back on anything ambiguous, sent status written back to your sheet, single-client resend, a dry-run mode so you can watch a run before it sends, written handover so you’re not dependent on me, and 30 days of fixes after delivery.

René Larsen
Avaga Holding AS · Fredrikstad, Norway
Org.nr 829 544 482 · [email protected]

16

Hi Andrew! I reviewed your invoice emailing workflow for your janitorial business.

I can build this in Make around Google Sheets, Google Drive, and Gmail, but first I’d verify filename matching so the wrong PDF is never sent.

I suggest a small paid first milestone: test 5 redacted clients, confirm Sheet columns and Drive naming rules, send one sample email, and log sent/error status.

Estimated first version: 1-2 days after sample data and access.

Could you share one anonymized Sheet row and one invoice filename, and confirm whether the PDFs can live in Google Drive?

17

Andrew, I can build the Google Workspace route (Sheets + Drive + Gmail) for USD 450 fixed, delivered in four business days once the scope, payer, payment, inputs, and safe access are confirmed.

The scenario will process mid-month and end-of-month rows sequentially, require a unique invoice key and exactly one matching PDF, validate the recipient and file, send the attachment, then write the sent status, timestamp, and Gmail message ID only after confirmed success. It will prevent duplicate sends and support a manual resend flag. Missing or duplicate PDFs, invalid recipients, Gmail failures, and uncertain send outcomes will stop safely without marking the invoice sent or automatically resending it.

Included: synthetic positive and negative tests, a buyer-observed three-invoice acceptance run, an exportable blueprint, field map, test evidence, written walkthrough, and one correction round. I would use only buyer-owned, least-privilege Google connections. Desktop/iCloud and invoice generation are outside this milestone.

My closest experience is API and workflow automation with failure-safe state changes and test-led delivery, rather than this exact janitorial workflow, so I will prove it in the scenario before any bulk run. After written acceptance, I will send a matching Stripe checkout; work starts when paid.

Romeo / romeoapps.com

18

Hi @Andrew_Makar ! If this is still relevant I would love to help you with your invoicing automations

We are a small team of make.com experts and have developed plenty of complex integrations. This project should not be a challenge to us.

If you are interested we would love to help you, you can schedule a call in here: Automation Discovery Call | Felipe Saucedo | Cal.com discovery or check our website www.aspirity.com

19

Hi Andrew,

I can build this as a fixed-scope Make.com workflow using Google Sheets, Google Drive, and Gmail.

The main priority would be safe invoice matching, not just email delivery. Each Sheet row would contain a stable client or invoice ID, and the scenario would only send when exactly one matching PDF is found. Missing or duplicate files would be stopped and logged instead of being sent incorrectly.

The workflow would include:

  • mid-month and end-of-month billing filters;
  • exact PDF matching in Google Drive;
  • Gmail delivery using your subject and email template;
  • sent timestamp and status written back to Google Sheets;
  • duplicate-send protection;
  • a controlled manual resend flag for individual invoices;
  • error logging, documentation, and a recorded walkthrough.

My fixed-price estimate is $395, with delivery in 3 business days after receiving a redacted sample Sheet row and several example invoice filenames.

I would first validate the process with five sample clients before enabling the full group of approximately 80 clients.

One technical requirement: the invoice PDFs need to live in or sync to Google Drive, since Make cannot reliably access a local desktop or iCloud folder directly.

Best regards,
Vlad

20

Hi Andrew — assuming the PDFs are in Google Drive (or can sync there reliably), I can deliver a fixed-scope reliability pilot for a redacted five-client sample in 3 business days. The pilot uses Google Sheets as the billing source of truth, matches each client or invoice ID to exactly one Drive PDF, stops safely when zero or multiple files match, records exceptions, prevents duplicate sends, and tests a controlled resend flag. It includes a short runbook and walkthrough. This is delivery automation, not invoice generation. It excludes Desktop or iCloud access, production Gmail credentials, real customer data, live invoice emails and the 80-client rollout until matching and duplicate checks pass. Fixed pilot price: USD 400. To confirm the exact setup, please share one redacted filename, the relevant Sheet column headers, and whether the billing cycle is driven by a Sheet value or calendar rule.