GoHighLevel Automation + AI Specialist - Workflows and AI (PHP 35k)

Please login or register as jobseeker to apply for this job.

TYPE OF WORK

Full Time

SALARY

PHP 35,000/month

HOURS PER WEEK

40

DATE UPDATED

Sep 4, 2026

JOB OVERVIEW

ABOUT US

We are an Australian digital marketing agency. We build lead generation systems for construction, trade and home service businesses: solar, electrical, air conditioning, plumbing, bathrooms and builders. We run the ads, we build the pages, and we wire the whole thing into GoHighLevel so every lead is tracked from the ad click through to the booked job.

We are small, fast and AI first. You will work directly with the founder.

We have not named the company in this ad on purpose. If your application gets through the first screen, we tell you exactly who we are by email, before any interview.

THE ROLE, AND WHICH OF OUR TWO GOHIGHLEVEL ADS YOU SHOULD APPLY FOR

We are hiring two GoHighLevel specialists at the same time, and we are running two ads so the right person lands in the right seat.

This ad is the automation and AI seat. Workflows, pipelines, triggers, conditions, webhooks, phone, and the AI features inside GoHighLevel. You are the person who makes the system behave.

The other ad is the design seat. Websites, funnels and pages built inside GoHighLevel that do not look like GoHighLevel. That person makes the system look right.

The two of you will work side by side every day, in the same sub-accounts. So each of you needs a working knowledge of the other half. You will build a page sometimes. They will fix a workflow sometimes. But we are hiring each of you for your strong side, and we will screen you on your strong side.

If workflows, integrations and AI are what you are best at, this is your ad. If what you are best at is making pages look great, apply for the design ad instead, not this one. Please do not apply for both. Pick the seat that is actually you and we will read it properly.

WHAT YOU WILL DO

Automations and workflows. This is the seat.
- Build workflows from scratch: triggers, filters, conditions, wait steps, if and else branches, goal events, internal notifications, and the tidy-up steps most people forget
- Speed to lead, missed call text back, nurture sequences, appointment reminders, no-show recovery, review requests, database reactivation
- Design pipelines end to end. Stages that mean something, automation moving opportunities between them, opportunity value, rotting rules, and reporting a tradesman can read without a tutorial
- Inbound webhooks in, outbound webhooks out. Custom values, custom fields, mapping a JSON payload onto a contact record correctly the first time
- Native first. When a workflow genuinely has to leave the platform you use n8n, Make or Zapier, and you can say why GoHighLevel could not do it on its own
- Debugging. Open the execution logs, find the step that failed, work out whether it is the trigger, the filter, the data or the integration, and fix it

AI inside GoHighLevel. The other half of the seat.
- Conversation AI, voice AI, booking bots and the AI employee features. Writing the prompt, setting the guardrails, d ---------- when it hands off to a human, and testing it against real conversations before it ever talks to a real lead
- AI that qualifies a lead, books the appointment and moves the opportunity, with a human alerted the moment it goes off script
- The AI never quotes a price. You build that guardrail in and you prove it holds
- You use AI in your own work every day. We give you a Claude account. You use it to draft, debug and document faster, and you know when not to trust it

Build in GoHighLevel. The half you support.
- Funnels and pages inside the builder when the design seat is at capacity: opt-in, booking and thank you pages, forms and surveys
- Enough custom CSS to fix a page. Designing one is the other seat
- Reusable snapshots so a new sub-account is stood up fast rather than rebuilt from zero

Measurement
- Meta Pixel and Conversions API on funnels, verified in Events Manager, with event ID deduplication
- Google Tag Manager, GA4 key events, Google Ads conversion tags
- UTM, GCLID and fbclid captured into contact custom fields so a lead maps back to the exact ad
- Meta lead ads wired in with correct field mapping and instant speed to lead
- Test every form, trigger link, calendar and redirect before it goes live, and keep the screenshot that proves it fired

Phone, domains and deliverability
- LC Phone or Twilio numbers set up properly, including the registration a new number needs before it is allowed to send
- Call routing, IVR and missed call handling that actually rings the right person
- Sending domains done properly: SPF, DKIM, DMARC, domain authentication in LC Email or Mailgun, and you know why mail lands in spam when those are wrong
- You know the difference between a DNS change that is safe and one that takes a client's email offline, and you check before you change

Compliance
- Every outbound message carries a working opt out. Australian Spam Act. Not negotiable
- Document what you build so someone else can pick it up

THE MONEY, PLAINLY

PHP 35,000 per month to start. That is the number on the card and it is what this seat pays from day one.

Separately, and honestly: there is more available for someone genuinely exceptional who can prove it. If your number is above 35,000, do not skip this ad. Apply, name your number, and describe the builds that justify it. We would rather have that conversation than never see your application.

On day one you get a written standard describing exactly what good delivery looks like in this seat. At 60 days we review your delivery against that written standard. You will know before you start what you are being measured against.

THE ARRANGEMENT, IN PLAIN TERMS

Please read this section properly. We would rather you d ---------- it is not for you today than discover something you did not expect in week three.

- This is an independent contractor engagement. It is not employment. You invoice us each pay period and we pay the invoice.
- You are responsible for your own tax and any local statutory contributions. We do not withhold tax. We do not pay SSS, PhilHealth or Pag-IBIG.
- There is no paid annual leave. There is no paid sick leave. There is no 13th month pay. We are telling you this in the ad rather than letting you find it out later.
- You are paid twice a month, in PHP, by Wise.
- Hours are 7:00am to 3:30pm Philippine time, Monday to Friday. 40 hours a week.
- Full time and exclusive for the engagement. Exclusive means what it says: while you are engaged with us you do not hold other retained clients and you do not work for another agency, evenings and weekends included. If you have existing commitments, tell us at application stage.
- 3 month probation.
- There is a PAID test task before any offer, and for this seat it is a real workflow build in a sandbox sub-account. We pay you for the time you spend on it, whether or not we make you an offer.
- Your equipment and your internet are yours: your own computer, a reliable connection at 25 Mbps or better, a backup connection, and a plan for power outages.
- Either side can end the engagement with two weeks written notice. That runs both ways.
- We provide and pay for a Claude account. You will use it every day.
- You will be inside client CRMs, ad accounts, phone systems and domain settings. Confidentiality is taken seriously, and you sign a contractor agreement and an NDA before you get access to anything.
- Real ownership of the automation side of the agency, not a ticket queue.

HOW THE INTERVIEW WORKS, SO THERE ARE NO SURPRISES

- If you get through the first screen we email you, tell you who we are, and offer you one interview time. One fixed slot, not a range.
- Reply and confirm that time in writing. If you do not confirm, we do not hold the slot.
- If something comes up, tell us before the slot and we will rebook you once. That happens and it is fine.
- If you do not turn up and you did not tell us, your application is closed. In our last round more than half the people we booked did not attend. It cost us an afternoon we could have spent on the people who did.
- The interview is a screen share. You open your own GoHighLevel account and walk us through the workflow, the pipeline and the AI agent you described in your application. Not slides. Not a portfolio PDF. The actual back end, live.
- So do not claim anything you cannot open. There is no penalty for a small amount of experience honestly described. There is a very large penalty for a claim that disappears when we ask to see it.

HOW TO APPLY

Line one of your application must read: TRIGGER followed by the number of GoHighLevel workflows you have personally built and turned on.

Example: TRIGGER 46

Applications that do not start this way are not read. That is the only trick in this ad and we have just told you what it is.

Then seven things. Numbers 3 to 6 are what actually d ---------- it.

1. YOUR CV. Attached or linked. A LinkedIn profile on its own is not a CV.

2. THE LIST.

Copy the list below and put ONE word next to every single line:

- DONE = I have personally built this on a real client account. Add the client type or industry.
- READ = I understand what it is and could learn it, but I have never shipped it.
- NEVER = I have never touched it, or I do not know what it is.

Read this next paragraph carefully because it is part of the test. We expect most applicants to have a lot of NEVERs on this list. Nine NEVERs with five honest DONEs beats eighteen DONEs every time, and an application with no NEVERs will be trusted less, not more. We open the DONEs on a screen share. There is no penalty for NEVER.

1. A workflow built from scratch with if and else branching and a goal event
2. A pipeline designed end to end, with automation moving opportunities between stages
3. Conversation AI or an AI booking bot configured in GHL and put live with real leads
4. Voice AI or an AI employee configured in GHL and put live on a real number
5. An AI agent given a rule it must never break, and tested to prove the rule holds
6. An inbound webhook used to create or update a GHL contact from an outside system
7. An outbound webhook from a GHL workflow into n8n, Make or Zapier
8. Custom values and custom fields used so one workflow serves many sub-accounts
9. Missed call text back, speed to lead and review request workflows built and live
10. A workflow debugged from the execution logs after it silently stopped firing
11. Calendars, recurring appointments and no-show recovery automation
12. A GHL snapshot built and deployed into a new sub-account
13. LC Phone or Twilio set up including the registration a new number needs before it can send
14. Call routing or an IVR set up in GHL that rang the right person
15. A Meta lead ad form connected to GHL with field mapping and instant speed to lead
16. Meta Pixel installed on a GHL funnel and verified in Events Manager
17. Meta Conversions API with event_id deduplication
18. UTM, GCLID and fbclid captured into contact custom fields
19. SPF, DKIM and DMARC set for LC Email or Mailgun on a client domain
20. A funnel page built in the GHL builder and made genuinely mobile responsive

3. ONE WORKFLOW YOU BUILT. Name it. Then tell us:
- what triggers it, exactly
- what the filters or conditions on that trigger are
- what each step does, in order
- what happens if the contact replies halfway through
- one thing about it you would build differently now

Write it as steps. Rough is fine. This is the answer we read first.

4. ONE PIPELINE YOU DESIGNED END TO END. The stage names in order, what moves a contact from one
stage to the next, whether each move is automatic or manual, and what the business owner actually got out of it. If you inherited the pipeline rather than designing it, say so.

5. AN AI AGENT OR CONVERSATION AI YOU CONFIGURED. What it did, roughly what you put in the prompt,
what it got wrong when you first turned it on, how you fixed that, and when it hands over to a human. Tell us one thing you stopped it from ever saying, and how you made sure it never did. If you have never configured one, write NEVER and say so plainly. An honest never is fine here. An invented one is not, because we will ask you to open it.

6. TWO SCENARIOS. Answer both in your own words.

6a. A workflow that has been running fine for months silently stops firing. Nobody changed anything. Nobody got an alert. Walk us through exactly what you check, in what order, and name the three most likely causes.

6b. A client has a custom form on their own website. It is not a GHL form and it never will be. You need every submission to create or update a contact in GHL and start a workflow. The native form submitted trigger will never see it. How do you do it? Be specific about the mechanism.

7. THROUGHPUT, YOUR NUMBER AND YOUR EMAIL.
- How many client sub-accounts are you actively responsible for right now?
- Pick one real build you finished: the date you got the brief, the date it went live, and the number of working days you personally spent on it. If it took three weeks, write three weeks. We are calibrating how you work, not only how fast you are.
- The monthly PHP figure you are working for right now, and the figure you would need to commit to us full time and exclusively. If those are two different numbers, say so.
- An email address we can reach you on. This platform's messaging has gone down on us before.

HOW TO WRITE THIS

Write it yourself.

We are going to be straight with you about why we care. In our last round, the single most impressive written application we received named exact tools and exact failure modes. It read like someone who had done the work for years. In the live interview, that same person could not name one tracking tool, said he did not know how to do automations, and had no example he could open. The application had almost certainly been written by an AI. We did not shortlist him and we both lost an afternoon.

Plain English with a typo in it beats a polished paragraph that says nothing. Use AI to fix your spelling if you like. If it writes your answers, it will show up in the first three minutes of the interview, because we ask you to open the thing you just described.

VIEW OTHER JOB POSTS FROM:
SHARE THIS POST
facebook linkedin
  BENCHMARKS  
Loading Time: Base Classes  0.0019
Controller Execution Time ( Jobseekers / Job )  0.0221
Total Execution Time  0.0253
  GET DATA  
No GET data exists
  MEMORY USAGE  
1,563,376 bytes
  POST DATA  
No POST data exists
  URI STRING  
jobseekers/job/GoHighLevel-Automation-AI-Specialist-Workflows-and-AI-PHP-35k-1723787
  CLASS/METHOD  
jobseekers/job
  DATABASE:  onlinejobs (Jobseekers:$db)   QUERIES: 13 (0.0103 seconds)  (Hide)
0.0006   SELECT *
                                
FROM exrates
                                WHERE rate_name 
'USD-PHP' 
0.0024   SELECT *
FROM `employer_jobs`
WHERE `job_id` = 1723787
 LIMIT 1 
0.0006   SELECT *
FROM `employers`
WHERE `employer_id` = 961474
 LIMIT 1 
0.0006   SELECT COUNT(*) AS `numrows`
FROM `t_thread` `t`
LEFT JOIN `t_thread_misc` `miscON `t`.`id` = `misc`.`thread_id`
WHERE `t`.`job_id` = 1723787
AND `misc`.`idIS NULL 
0.0007   SELECT e.business_namee.logoe.websitee.rebill_datee.date_added member_datehitsDATEDIFF('2026-09-08',ej.date_added) duration_daysDATEDIFF('2026-09-08',e.rebill_date) duration_rebillej.*, e.deactivate FROM employers eemployer_jobs ej WHERE e.employer_id ej.employer_id AND
                                   ((
e.user_level >= '500' AND ej.date_added <= e.rebill_date)
                                   OR 
e.employer_id '' OR (ej.date_approved <> '2000-01-01' and DATEDIFF('2026-09-08',ej.date_added) <= 14 ))
                                   AND 
e.deactivate != AND ej.deleted AND job_id '1723787' 
0.0014   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1723787 
0.0011   UPDATE employer_jobs SET hit_counts '***Sep-04-2026=371***Sep-05-2026=205***Sep-07-2026=1***Sep-08-2026=2' WHERE job_id'1723787'  
0.0008   UPDATE employer_jobs SET monthly_hits '***Sep-2026=579' WHERE job_id'1723787'  
0.0005   SELECT date_sent FROM jobseeker_sent_emails WHERE jobseeker_id '' AND job_id '1723787' AND status LIKE 'sent%' ORDER BY id DESC  
0.0004   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1723787 
0.0005   SELECT COUNT(*) AS `numrows`
FROM `employer_jobs`
WHERE `employer_id` = '961474'
AND `date_added` >= '2022-06-08' 
0.0004   select from teasers 
0.0003   SELECT FROM skill_categories WHERE skill_cat_id='' 
  HTTP HEADERS  (Show)
  SESSION DATA  (Show)
  CONFIG VARIABLES  (Show)