Full Time
400-500 - could be more for right person
TBD
Jan 7, 2026
Overview
I’m looking for a No-Code Automation Builder to help design, build, and maintain automations across various tools and platforms.
This role is ideal for someone who already understands how software works, has some prior coding experience or technical background, and is now comfortable building powerful workflows using n8n and
You’ll be given clear objectives (sometimes high-level) and trusted to figure out the implementation independently, communicate progress, and deliver working automations.
Key Responsibilities
Building automations using n8n and
Connecting APIs, webhooks, CRMs, spreadsheets,
Translating business requirements into automated workflows
Debugging, improving, and optimising existing automations
Documenting workflows clearly so they’re easy to understand and maintain
Communicating progress, blockers, and completion clearly
What I’m Looking For
You’ll be a great fit if you:
Have hands-on experience with n8n and/or
Have prior coding experience (JavaScript, Python, or similar — even at a basic level)
Understand APIs, webhooks, data structures, and logic flows
Can follow instructions accurately while also thinking critically
Are comfortable being given a task and working independently to completion
Communicate clearly in good written and spoken English
Are organised, reliable, and proactive with updates
Working Style & Hours
Flexible working hours
No fixed schedule — I’ll give you a task, you work on it and deliver
You must be reachable for clarification and updates when needed
Strong communication matters more than being “always online”
Requirements
Reliable internet connection
A capable computer suitable for technical work
Ability to explain what you’ve built and why
Trial & Next Steps
Short paid trial task to assess real-world ability
Ongoing work available for the right person
What Success Looks Like
I can hand you a process and trust you to automate it properly
Automations are reliable, clean, and well-documented
Minimal back-and-forth needed once a task is understood
You think in systems, not just steps