Tulen Agency
If You Can Build It in GoHighLevel, You May Just Be The Person We Have Been Waiting For. Automations Specialist — GoHighLevel, n8n, and everything you can reach with an API Tulen Agency · Remote · Paid trial project → full-time Let's start with where you probably are right now You're the technical one. Which means you're the person who built the workflow, and you're also the person nobody can replace, which sounds like leverage until you realize what it actually bought you: you can't take a vacation, you can't go deep on anything, and half your week is spent explaining to an account manager why the "simple change" they promised the client is going to break three downstream automations. Maybe you're at an agency where automation is treated as a chore instead of a product. Somebody sold a client on "we'll automate your follow-up," and now you're rebuilding the same missed-call-text-back snapshot for the ninth time this quarter. Or you're freelancing on Upwork, bidding against people who will do it for $12/hour and don't know what a webhook is, so the buyer can't tell the difference between you and them and neither can the algorithm. Or maybe the worst version: you're good enough to build something genuinely complex — real conditional logic, real API calls out to a system GHL was never designed to integrate with, real error handling — and there is not one person in your company who can look at it and understand what you did. So it never gets recognized, never gets budgeted for, and the next time someone asks "can we just use Zapier for this," you don't even argue anymore. If any of that landed, keep reading. If it didn't, this probably isn't your role, and you should stop here — we'd rather you self-select out now than three weeks into a trial. What Tulen actually is We run paid media and marketing automation for event venues, wedding venues, and hospitality brands across the US. We focus on high-ticket bookings where a single lead is worth thousands of dollars to the client. Here's why that matters to you: in our business, the automation layer is not a nice-to-have sitting off to the side of the "real" marketing work. It is the product. A venue's ad spend produces a lead. That lead has to land in GoHighLevel, get routed to the right pipeline based on event type, trigger the right nurture sequence, get in front of the venue's event coordinator inside the tool they already use — Tripleseat, Perfect Venue, HoneyBook, and then once they have a signed contract we need to send the data back to the exact campaign that generated it. Every one of those handoffs is a place where the money leaks out. Every one of them is a workflow, a webhook, or an API call. When that chain works, our clients see a 10x return on ad spend, and they stay with us for years. When one link in it silently breaks on a Tuesday, a venue loses a $40,000 wedding and doesn't find out for six weeks. That chain is the job. You own it. We're not hiring a ticket-closer. We're hiring the person who owns the machine that makes the rest of the agency work. What you'd actually be doing Build new automations for our venue clients. Every venue we onboard needs a system built for how that venue actually operates. Not a snapshot import and a prayer. You'll scope it, build it, test it, and own whether it works. Go into complex existing workflows and change them without breaking them. This is a real skill and most people don't have it. Reading somebody else's logic, finding the four places a change ripples out to, and making the edit cleanly — that's half the job on established accounts. Build from scratch, at real complexity. Multi-condition logic, conditional routing, custom fields and objects, webhooks going out, webhooks coming in, data getting reshaped in n8n or Make on the way between two systems that were never meant to talk to each other. Connect GoHighLevel to whatever else is in the stack. Venue management platforms, calendars, payment processors, reporting layers, spreadsheets, our own internal reporting. Some of these have clean, documented APIs. Some have an API that was documented once, in 2021, by someone who has since left the company. You'll figure it out either way. Be the technical answer. When a client asks "can the system do X?" — you're the one who says yes, no, or "not the way you're describing it, but here's what would actually solve the problem." That last answer is the one we value most. Keep the machine honest. Audits, error monitoring, catching the silent failures before a client does. The unglamorous part that separates people who build automations from people who run automation. Who this is for Multiple years building in GoHighLevel. Not "I've used it." Built in it. Deeply. You know where the platform's real edges are and how to work around them, because you've hit them. You're comfortable with APIs and webhooks as a default tool , not a last resort. You can read documentation for a platform you've never touched and have something working the same day. n8n, Make, or equivalent — you know when the right answer is to use GHL and when the right answer is to route it out to a proper automation platform. Fluent English and genuinely strong writing. This is a must-have, not a formality. You'll write to clients, write documentation, and explain technical constraints to non-technical venue owners without making them feel stupid. If you can't do that, the technical skill doesn't help us. You're a simplifier, not a complicator. Given two ways to solve something, you take the one that has fewer moving parts and fewer things that can break at 11pm on a Saturday. Nice to have: experience with venue/hospitality software (Tripleseat, Perfect Venue, HoneyBook), agency experience, tracking and attribution work (pixels, CAPI, server-side), light scripting, and any experience where you were the person clients talked to directly. How this works Step one is a paid trial project. Not a take-home puzzle designed to waste your weekend — an actual piece of work, scoped and paid, on a real problem. You'll see how we operate; we'll see how you build, and both of us will know within a couple of weeks whether this is right. If it is, it converts to an ongoing full-time role. We do it this way because senior hires are risky in both directions. You'd be leaving something known. We'd be handing over the nervous system of the agency. A trial is the cheapest way for both of us to find out the truth. On compensation: we're not posting a range. We pay well for people who are actually good, and what "well" means depends entirely on what you bring. If you're the person we're describing, you'll do fine here — tell us what you're worth and we'll have a real conversation about it. We would much rather stretch for the right person than save money on the wrong one. Logistics: remote. Overlap with US business hours for team collaboration and client calls. Occasional travel for client events and team meetups, on us. To apply Answer the questions below. There are a lot of them, and some of them will look like they have nothing to do with automations. That's deliberate. We're hiring someone who's bought into building something, not someone spraying applications at every listing with an AI autofill. If answering these carefully feels like too much work, we've both saved ourselves some time.We strongly recommend you film a loom to introduce yourself and send us answers to the following questions. If you want, you can answer all the following questions in that Loom. Walk us through the most complex automation you've ever built. What was the trigger, what were the branches, what systems did it touch, and what broke the first time you shipped it? Give us a specific example of a time you connected GoHighLevel to a platform it doesn't natively integrate with. How did you do it? A venue client wants this: when a wedding inquiry comes in, check whether their date is available in their booking system, route available-date leads into an immediate call-booking sequence, route unavailable-date leads into an alternate-dates offer, and push both into their event management platform with the right tags. How long would it take you to build that, start to finish, at an A+ level? Give us a number. Why that number? Walk us through what your process would actually look like. Tell us about a process you simplified that was unnecessarily complicated. What was broken, what did you change, what was the result? What's something about GoHighLevel that most people who use it get wrong? What important truth do very few people agree with you on? A client emails at 4 pm saying "the automation isn't working." That's the entire message. What are your first three moves? Are you currently employed or contracting somewhere? Where, and doing what? We read every application. If you're a fit, we'll set up a call — and be ready to share your screen and walk us through something you've actually built. — Tulen Agency Pay: From Php70,000.00 per month Work Location: Remote
Tulen Agency
