Make.com Automation Builder

Job Brief: ---------- Automation Builder
Automated Reporting Pipeline - Meta Ads + Go High Level


Project type
One-off build (with potential ongoing retainer)

Engagement type
Gig

Platform
---------- (Integromat)

Data sources
Meta Ads API + Go High Level API

Output
Google Sheets - daily raw data + rolling dashboard

Number of clients
8 (separate Business Managers and GHL accounts)

Timeline
To be agreed - phased delivery expected


Project Overview
I run an acquisition-focused consultancy managing Meta ad campaigns for 8 clients. Currently I spend approximately 2 hours every Monday manually pulling data fro ---------- ta Ads Manager and Go High Level, then consolidating it into a weekly snapshot spreadsheet.

I need a ---------- automation specialist to build a pipeline that pulls this data automatically on a daily basis and populates a structured Google Sheet. The sheet will have two layers: a raw daily data tab and a rolling dashboard tab showing 3-day, 7-day, and 30-day snapshots.

This is not a complex build in terms of logic, but it requires genuine hands-on experience with the Meta Marketing API and Go High Level API specifically - not just general Make experience.


Scope of Work
Phase 1 - Single Client Build
Build the full pipeline for one client first. This is a deliberate checkpoint before scaling to all 8 accounts. Phase 2 only proceeds once Phase 1 is working correctly and I have signed off on it.

Data Sources
Meta Marketing API
Daily spend per ad account
Impressions
Reach
Frequency
Link clicks
CTR (link click-through rate)
CPC (cost per link click)
CPM
Click > Landing page views%
Results (purchases / conversions) - NOTE: the conversion event name varies per client account and must be configurable per client, not hardcoded
Cost per result

Go High Level API
Page views (sales page)
Leads / opt-ins
Sales volumes by product tier: Core Offer, Bump, OTO1, OTO2 (naming is generic - actual product names vary per client but map to these tiers)

Google Sheet Architecture
Tab 1 - Raw Daily Data
One row per day per client
All API-pulled fields listed above as columns
A 'Notes / Change Log' column (manually filled by me - to track creative changes, headline tests, offer changes etc.)
Data overwrites the last 3 days on each run to account for Meta's attribution window (conversions are backdated up to 48 hours)

Tab 2 - Rolling Dashboard
Aggregated views: rolling 3-day, 7-day, and 30-day windows, auto-calculated from today's date
Calculated metrics derived from raw data: CPA, AOV, ROAS, EPC, Sales Page CVR%, Bump CVR%, OTO1 CVR%, OTO2 CVR?shboard tab uses sheet formulas only - no additional API calls
One dashboard tab per client, or a consolidated multi-client view - to be discussed

All calculated metrics (CPA, ROAS, CVR% etc.) are formula-driven in the sheet. The automation only needs to supply the raw numbers. Do not build calculated metrics into the Make scenario.


Trigger and Schedule
Daily trigger - runs once per day, preferably between midnight and 6am AEST
Pulls previous day's data plus refreshes last 3 days to handle Meta attribution window
Must handle failures gracefully - if one client's API call fails, the scenario should continue for remaining clients and log the error

Multi-Account Handling
This is the most technically important requirement. All 8 clients are on separate Meta Business Managers and separate Go High Level accounts. The builder must have a clear approach to handling this before starting work.

No single token covers all clients - each account requires its own API connection or token
The approach to managing multiple BM tokens (refresh, expiry, re-auth) must be documented and handed over
GHL accounts are also separate instances - same requirement applies
Each client should have their own independent Make scenario so failures are isolated per account.
I will provide access credentials once approach is agreed

What I Am Not Looking For
Someone who will 'figure it out' on my budget - you should have done this before
A Zapier builder who has dabbled in Make - Make-specific experience required
Someone who has only connected a single Meta ad account - multi-BM experience specifically
A build that works once and breaks when a token expires with no documentation on how to fix it

Required Experience
---------- - demonstrated, not claimed. Show me a live example or describe a comparable build in your application
Meta Marketing API - specifically experience with multi-account / multi-BM setups and token management
Go High Level API - experience pulling funnel/CRM data
Google Sheets integration via Make
Experience handling API authentication, token refresh, and error handling in Make scenarios

Bonus (not required for Phase 1)
Google Sheets dashboard / formula build experience - if you can handle both the pipeline and the dashboard logic that is a bonus but not a requirement

Deliverables
The following must be delivered and signed off before payment for each phase:

Working Make scenario(s) pulling daily data fro ---------- ta and GHL into Google Sheets
Sheet populated with at least 2 weeks of historical data for the Phase 1 client on handover
Written documentation covering: how the scenario works, how to add a new client, how to handle token expiry and re-authentication for both Meta and GHL, and what to do when a scenario errors
A 30-minute walkthrough call on handover (Zoom/Loom) explaining what was built and how to maintain it

How to Apply
Do not send a generic application. I will not respond to copy-paste cover letters.

In your application please answer the following specifically:

Have you connected multiple separate Meta Business Managers in a single Make scenario? If yes, describe how you handled token management across accounts.
Have you built a Make scenario that pulls data from Go High Level? If yes, what data were you pulling and what was the use case?
Describe how you would handle the Meta attribution window (conversions backdated 24-48 hours) in a daily data pull scenario.
What happens in your scenarios when one API call fails mid-run? Walk me through your error handling approach.
Provide either a link to a comparable live scenario (can be anonymised) or a brief description of the most similar project you have built.

These five questions are a screening filter. If you cannot answer questions 1 and 3 specifically, this project is not the right fit.


Budget and Scope Note
This is scoped as a one-off build with a phased approach - Phase 1 is one client, Phase 2 is the remaining 7. I have additional automation projects beyond this one and am looking for someone I can work with on an ongoing basis if Phase 1 goes well.

Please quote for Phase 1 (single client pipeline + documentation) and Phase 2 (scaling to 8 clients) separately in your application.