Make.com / n8n Automation Developer for AI
Any
50,000 PHP
40
Mar 22, 2026
We are a reputation management company
We already have our outbound cold
This is not a beginner automation job.
I am looking for someone who can take a detailed build spec and turn it into a clean, reliable, production-ready system with minimal hand-holding.
Project Structure
This role is structured in 3 phases:
Phase 1: Fixed-Price Build
You will build the initial system based on an existing detailed specification.
Fixed project payment: 50,000 PHP
Phase 2: Paid Maintenance / Optimization
After launch, I want the same person to continue maintaining, improving, debugging, and optimizing the system as needed.
This will be a separate paid arrangement after the build is complete.
Phase 3: Long-Term Role
If you are strong, fast, reliable, and easy to work with, this can turn into an ongoing role building and maintaining additional automations across the business.
I do not want a one-off freelancer if I find the right person. I want someone who can become the go-to technical builder for future systems.
What You’ll Be Building
You will build an automation system that does things like:
Pull interested prospect replies from Instantly.ai
Fetch the full
Send thread context + business/review data to Claude
Route responses based on logic:
auto-send
hold for VA review in Slack
escalate to founder
Send replies through Instantly while preserving thread and sender persona
Send SMS follow-up after
Update GoHighLevel pipeline, tags, and custom fields
Trigger stage-specific follow-ups when a prospect goes cold
Create Slack approval workflows with approve / edit / reject actions
Support a phased rollout from semi-automated to more fully automated
Be structured cleanly so future automations can be added without rebuilding everything
Platforms / Skills Needed
You should already be experienced with most or all of these:
APIs / webhooks / HTTP requests
Claude / Anthropic API
Instantly.ai
GoHighLevel
Slack integrations
Router logic / parsing / error handling
CRM workflow automation
SMS integrations
Who This Is For
You are a fit if:
You are a real automation builder, not just a general VA
You have built multi-step systems with APIs, logic branches, and approval flows
You can think through edge cases before they become problems
You can move fast and still build cleanly
You communicate clearly
You can work independently
You know how to debug without getting lost
Who This Is NOT For
This is not for you if:
You only know basic Zapier-level automation
You need constant step-by-step technical guidance
You have never worked directly with APIs / webhooks / JSON / routing logic
You cannot explain how your systems work
You are slow to execute and slow to communicate
You disappear when something gets difficult
Speed Matters
This project needs to move quickly.
I care about clean execution, but speed is also important. I am looking for someone who can build with urgency, communicate blockers early, and keep
I do not expect perfection on day 1. I do expect strong judgment, proactive communication, and steady progress.
If you are the type who drags projects out unnecessarily, this will not be a fit.
Timeline
I am looking for someone who can begin quickly and deliver the first working version fast.
A strong builder should be able to make meaningful progress immediately and get this built in a reasonable timeframe.
When you apply, tell me your realistic timeline to complete v1 properly.
Long-Term Opportunity
This is important:
If you perform well on this build, I want to keep working with you.
We have additional automation opportunities beyond this system. The right person can become the ongoing automation lead for the business through paid maintenance, upgrades, new workflows, and future builds.
To Apply
Do not send a generic application.
Start your application with:
READY TO BUILD
Then answer every question below carefully.
Applications that ignore instructions will not be considered.
Screening Questions
What is the most advanced automation system you have personally built? Explain the workflow clearly.
Which of these have you used directly:
Have you built approval-based workflows before where someone can approve, edit, or reject inside Slack or another interface? Explain.
How would you prevent duplicate webhook processing in a system like this?
If AI output fails parsing or returns bad structure, how would you handle that safely?
If you were building this project, what parts would you build first and why?
What part of this system is most likely to break if built poorly?
How would you structure this so future automations can be added without rebuilding the whole thing?
How fast could you realistically deliver a strong v1?
After launch, would you be open to a separate paid maintenance role plus future builds?
Send 2-3 examples, screenshots, Looms, or short explanations of similar work you have done.
What is your preferred setup for the build fee and then ongoing maintenance after launch?
Final Instruction
Write the word BLUEPRINT at the very end of your application.